Someone should close kern/11222

2000-01-04 Thread Ted Faber
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I noticed that the behavior that prompted me to submit kern/11222 (spurious fscks on when an mfs file system was in use at boot time) disappeared under 3.3-RELEASE, and today I finally had time to check the CVS logs to see what happened. It looks

Re: Someone should close kern/11222

2000-01-04 Thread Matthew Dillon
:I noticed that the behavior that prompted me to submit kern/11222 :(spurious fscks on when an mfs file system was in use at boot time) :disappeared under 3.3-RELEASE, and today I finally had time to check :the CVS logs to see what happened. It looks to me like Andrew :Gallatin's patch

Re: kern/11222

1999-07-06 Thread Matthew Dillon
[EMAIL PROTECTED] :-BEGIN PGP SIGNED MESSAGE- : :Hi, folks. I was hoping that someone would take a look at kern/11222, :which has been open since I submitted it in April. The problem it :addresses is that MFS buffers that are dirty when the reboot syscall :is made

Re: kern/11222

1999-07-06 Thread Ted Faber
-BEGIN PGP SIGNED MESSAGE- Matthew Dillon wrote: Hi Ted. I did look at it and it seems ok, though I didn't run it by the gurus. Thanks. I know you're busy, and I just figured it was buried under other more pressing concerns. Sorry the commit problems are still lingering,

kern/11222

1999-07-06 Thread Ted Faber
-BEGIN PGP SIGNED MESSAGE- Hi, folks. I was hoping that someone would take a look at kern/11222, which has been open since I submitted it in April. The problem it addresses is that MFS buffers that are dirty when the reboot syscall is made are never cleaned because the reboot call

Re: kern/11222

1999-07-06 Thread Matthew Dillon
dil...@backplane.com :-BEGIN PGP SIGNED MESSAGE- : :Hi, folks. I was hoping that someone would take a look at kern/11222, :which has been open since I submitted it in April. The problem it :addresses is that MFS buffers that are dirty when the reboot syscall :is made

Re: kern/11222

1999-07-06 Thread Ted Faber
-BEGIN PGP SIGNED MESSAGE- Matthew Dillon wrote: Hi Ted. I did look at it and it seems ok, though I didn't run it by the gurus. Thanks. I know you're busy, and I just figured it was buried under other more pressing concerns. Sorry the commit problems are still lingering,