[ Sorry for cross-posting, but I included -arch@ for technical
discussion, -current@ for reaching the wider audience and -fs@ for the
relevance of the matter.]
During the last years a lot of effort by several developers happened
in order to reduce Giant influence over the entire kernel.
The VFS la
Hi,
On Friday 26 August 2011 07:56:04 Pegasus Mc Cleaft wrote:
>
> I have recently installed this into a new machine and had chance to
did you solve your problem?
I have had a similar problem yesterday after upgrading my ports via packages. I
could not even switch to the consoles anymore
Steve Wills wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 08/26/11 22:16, Steve Wills wrote:
> > On 08/26/11 21:41, Steve Wills wrote:
> >> Hi,
> >
> >> I'm trying to use 9.0-CURRENT as an NFS server for a VMWare ESXi
> >> 4.1.0.
> >> When I attempt the mount, it logs this messag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/27/11 09:00, Rick Macklem wrote:
>> This line indicates that mountd over tcp is registered for v3,
>> so I suspect the error message is misleading??
Forgot to reply to this part, and I should have been more clear earlier.
When I used the default
On Sat, Aug 27, 2011 at 02:00:50PM +0200, Attilio Rao wrote:
> [ Sorry for cross-posting, but I included -arch@ for technical
> discussion, -current@ for reaching the wider audience and -fs@ for the
> relevance of the matter.]
>
> During the last years a lot of effort by several developers happene
On 8/25/11, Dimitry Andric wrote:
> On 2011-08-25 17:12, Beach Geek wrote:
>> make buildworld failed trying to upgrade from r223619 to r225128.
>> (Note: Updating other boxes from r224774 to r225119 went flawless)
>>
>> On failing laptop (Toshibs Sat C655D)
>
>> /usr/include/c++/4.2/bits/stri
On Aug 26, 2011, at 2:07 PM, Andriy Gapon wrote:
>
> It seems that after the introduction of the mountroot scripting language a
> user
> now has exactly one chance to try to specify a correct root device at the
> mountroot prompt. I am not sure that that is convenient/enough.
This is no diffe
Hi,
after upgrading vom FBSD8.2 to todays current, I have the problem that my
two Areca controllers don't find any disks. In dmesg there are a lot of
messages like:
arcmsr0: scsi id 2 lun 0 cmd=0x12 srb='0xff83e298f000' ccb command time
out!
The whole dmesg can be found here:
http://ugrohnwal
This website should be brushed up or taken offline!
It seems full of vintage stuff from glory days.
http://www.freebsd.org/marketing/os-comparison.html
O.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-c
On Sat, Aug 27, 2011 at 12:13 PM, Hartmann, O.
wrote:
> This website should be brushed up or taken offline!
> It seems full of vintage stuff from glory days.
>
> http://www.freebsd.org/marketing/os-comparison.html
Agreed. Things have changed quite a bit in the last decade.
-Garrett
__
Steve Wills wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 08/27/11 09:00, Rick Macklem wrote:
> >> This line indicates that mountd over tcp is registered for v3,
> >> so I suspect the error message is misleading??
>
> Forgot to reply to this part, and I should have been more cle
Steve Wills wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 08/26/11 22:16, Steve Wills wrote:
> > On 08/26/11 21:41, Steve Wills wrote:
> >> Hi,
> >
> >> I'm trying to use 9.0-CURRENT as an NFS server for a VMWare ESXi
> >> 4.1.0.
> >> When I attempt the mount, it logs this messag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/27/11 20:55, Rick Macklem wrote:
>> I don't know why the nfsd wouldn't be able to bind(2) to port #2049 a
>> second time for UDP, but someone on the net side might know? (Just in
>> case it is a problem that has already been fixed, I'd try a newe
On Saturday 27 August 2011 13:11:43 Erich Dollansky wrote:
> Hi,
>
> On Friday 26 August 2011 07:56:04 Pegasus Mc Cleaft wrote:
> > I have recently installed this into a new machine and had chance to
>
> did you solve your problem?
>
> I have had a similar problem yesterday after upgrading m
14 matches
Mail list logo
