-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> > > JM>map02# strace -p 730
> > > JM>strace: open("/proc/...", ...): No such file or directory
> > > JM>trouble opening proc file
> >
> > > You must mount procfs.
> > >
> > > # fstab;
> > > proc /proc procfs rw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> JM>map02# strace -p 730
> JM>strace: open("/proc/...", ...): No such file or directory
> JM>trouble opening proc file
> You must mount procfs.
>
> # fstab;
> proc /proc procfs rw 0 0
The bi-weekly sta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> There was, at one point, talk of adding some sort of
> "geom.dont_blame_phk_when_you_shoot_your_ankle_off" sysctl to permit
> this type of access when the user was absolutely sure they knew exactly
> what kind of dangerous and potentially corrupting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> You have hit one of the main issues still to be resolved in GEOM. (I
> don't know that phk thinks it's a problem to be resolved or a feature to
> be documented.)
>
> In any case, since GEOM was added you can no longer slice or label an
> active devi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> > I'm also seeing a similar problem - I have a cluster of high-volume
> > mailservers delivering mail over nfs to maildirs on a netapp. The cluster
> > was all 4-stable, but I decided to mix a couple of 5.1 boxes in to see how
> > they would do.
[.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> In this configuration I see a lot of "nfs server ...: is not responding"
> and "nfs server ...: is alive again" when I copy large files (e.g. a CD
> image). All of them happen in the same second. I haven't looked at the
> state or priority of the cp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> ATAng has just been committed. You need to make world after this update
> as atacontrol etc needs to pick up the changes.
Just want to report initial success with this - my smp machine previously
would not recognize my offboard pci-based ide device
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> > Grap the latest from ftp.deepcore.dk/pub/ATAng and apply the diff files
> > to your src tree, remove the contents of sys/dev/ata and extract the
> > ATAng-*tgz file there, then do the usual drill to get a new kernel...
Tried to grab this last nig