In message [EMAIL PROTECTED], Bruce Ev
ans writes:
Probably that you shouldn't have downgraded savecore by updating it
:-). savecore now uses devname() but devname() is too unreliable to
use for anything except informational output.
It always were:
boot
log in
mv
My boot message of today said:
Oct 11 10:18:10 waterblue savecore: /dev/#C:116:0x20001: No such file or directory
And swap entry in /etc/fstab is:
/dev/ad0s1b noneswapsw 0 0
This is non-DEVFS environment. Am I missing some point of updating?
--
Mine has been saying something similar for a week or so now. I just
figured it was me and ignored it. Manually running savecore gives no error
and works fine.
On Wed, 11 Oct 2000, Jun Kuriyama wrote:
My boot message of today said:
Oct 11 10:18:10 waterblue savecore: /dev/#C:116:0x20001: No
On Tue, Oct 10, 2000 at 07:39:40PM -0700, Steve Kargl wrote:
Jun Kuriyama wrote:
My boot message of today said:
Oct 11 10:18:10 waterblue savecore: /dev/#C:116:0x20001:\
No such file or directory
This is occurring on my machine also. It makes it fairly
hard to get a crash.
I got
On Wed, 11 Oct 2000, Jun Kuriyama wrote:
My boot message of today said:
Oct 11 10:18:10 waterblue savecore: /dev/#C:116:0x20001: No such file or directory
And swap entry in /etc/fstab is:
/dev/ad0s1b noneswapsw 0 0
This is non-DEVFS
