>
>
> On Mon, 28 Jun 2010, Daniel Braniss wrote:
>
> >>
> >>
> >> On Mon, 28 Jun 2010, al...@ulgsm.ru wrote:
> >>
> >>>
> >>>
> >>> kernel built with:
> >>> options BOOTP # Use BOOTP to obtain IP address/hostname
> >>> options BOOTP_NFSROOT # NFS mount root file system using BO
On Tue, 29 Jun 2010, Dan Nelson wrote:
> In the last episode (Jun 29), Rick C. Petty said:
> > On Tue, Jun 29, 2010 at 10:20:57AM -0500, Adam Vande More wrote:
> > > On Tue, Jun 29, 2010 at 9:58 AM, Rick Macklem
> > > wrote:
> > >
> > > > I suppose if the FreeBSD world feels that "root" an
On Tuesday 29 June 2010 12:46 pm, Mario Sergio Fujikawa Ferreira
wrote:
> Quoting Jung-uk Kim :
> > On Monday 28 June 2010 02:01 pm, Jung-uk Kim wrote:
> >> Please drop the attached patch in ports/devel/boost-libs/files,
> >> rebuild all dependencies, and try your deluge ports again[1].
> >
> > Pl
Quoting Jung-uk Kim :
> On Monday 28 June 2010 02:01 pm, Jung-uk Kim wrote:
>> Please drop the attached patch in ports/devel/boost-libs/files,
>> rebuild all dependencies, and try your deluge ports again[1].
>
> Please ignore the previous patch and try this one. Sorry, there was a
> typo. :-(
i've got a panic with zfs only machine so i decided to build a witness kernel
and just after the first reboot:
http://img190.imageshack.us/img190/3314/panicflowtable2.jpg
the second boot: no prob
uname -a
FreeBSD cg196.security-mail.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE
#8: Tue Jun 29 14:30:1
In the last episode (Jun 29), Rick C. Petty said:
> On Tue, Jun 29, 2010 at 10:20:57AM -0500, Adam Vande More wrote:
> > On Tue, Jun 29, 2010 at 9:58 AM, Rick Macklem wrote:
> >
> > > I suppose if the FreeBSD world feels that "root" and "toor" must both
> > > exist in the password database, then
On Mon, 28 Jun 2010, Rick C. Petty wrote:
It would be interesting to see if the performance problem exists for
NFSv3 mounts against the experimental (nfsv4) server.
Hmm, I couldn't reproduce the problem. Once I unmounted the nfsv4 client
and tried v3, the jittering stopped. Then I unmoun
On Tue, 29 Jun 2010, Rick C. Petty wrote:
To be fair, I'm not sure this is even a problem. Rick M. only suggested it
as a possibility. I would think that getpwuid() would return the first
match which has always been root. At least that's what it does when
scanning the passwd file; I'm not
On Tue, Jun 29, 2010 at 10:20:57AM -0500, Adam Vande More wrote:
> On Tue, Jun 29, 2010 at 9:58 AM, Rick Macklem wrote:
>
> > I suppose if the FreeBSD world feels that "root" and "toor" must both
> > exist in the password database, then "nfsuserd" could be hacked to handle
> > the case of transla
On Tue, 29 Jun 2010, al...@ulgsm.ru wrote:
Yes. without BOOTPxxx options boot is fine.
Btw, if you feel like helping out with testing it, I have patches for
this case that modify pxeboot to use NFSv3 instead of NFSv2. The more
testing they get the better. They're at:
http://people.freebsd.o
On Tue, Jun 29, 2010 at 9:58 AM, Rick Macklem wrote:
> I suppose if the FreeBSD world feels that "root" and "toor" must both
> exist in the password database, then "nfsuserd" could be hacked to handle
> the case of translating uid 0 to "root" without calling getpwuid(). It
> seems ugly, but if de
On Mon, 28 Jun 2010, Daniel Braniss wrote:
On Mon, 28 Jun 2010, al...@ulgsm.ru wrote:
kernel built with:
options BOOTP # Use BOOTP to obtain IP address/hostname
options BOOTP_NFSROOT # NFS mount root file system using BOOTP info
options BOOTP_NFSV3
Try building a
On Tue, 29 Jun 2010, al...@ulgsm.ru wrote:
I think using NFS_ROOT but not the BOOTPxxx options will work around this
or you could test the following patch and see if it helps. (Testing the
patch would be appreciated, since I don't have any way to test across
multiple subnets and it would be n
On Tue, 29 Jun 2010, Ian Smith wrote:
Not wanting to hijack this (interesting) thread, but ..
I have to concur with Rick P - that's rather a odd requirement when each
FreeBSD install since at least 2.2 has come with root and toor (in that
order) in /etc/passwd. I don't use toor, but often e
On 29 June 2010 13:25, pluknet wrote:
> Hi.
>
> I noticed that ps on all supported releases (w/ ULE)
> shows the value of cpu keyword always as 0 (zero).
Please, ignore my stupidity. Thought that's a CPU number.
--
wbr,
pluknet
___
freebsd-stable@free
Hi.
I noticed that ps on all supported releases (w/ ULE)
shows the value of cpu keyword always as 0 (zero).
COMMAND CPU
kernel/swapper 0
kernel/firmware taskq 0
kernel/thread taskq 0
kernel/kqueue taskq 0
kernel/acpi_task_0 0
kernel/acpi_task_1 0
kernel/
16 matches
Mail list logo
