Re: savecore cannot find device?
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 /dev/something /dev/other # devname(3) gives wrong output -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: savecore cannot find device?
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 environment. Am I missing some point of updating? 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. There are several failure modes. When devname() can't find the device name by looking up dev.db or using sysctl kern.devname, it invents a name of the above form. Apparently, the device name "ad0s1b" is not understood by the kernel when savecore is run (early in /etc/rc). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: savecore cannot find device?
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 this too. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: savecore cannot find device?
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. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: savecore cannot find device?
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 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? > > > -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
savecore cannot find device?
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? -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. <[EMAIL PROTECTED]> // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
