Re: /etc/init.d/boot message?
[edited out discussion about how this could be implimented ...]
But I'm sure I used to get all the messages in /var/log/kern.log before
I upgraded to hamm (see messages with subject "/etc/init.d/boot
message")
e.g.
Jun 14 13:06:25 Bert kernel: klogd 1.3-3, log source = /proc/kmsg
started.
Jun 14 13:06:25 Bert kernel: Loaded 5635 symbols from
/boot/System.map-2.0.33.
Jun 14 13:06:25 Bert kernel: Symbols match kernel version 2.0.33.
Jun 14 13:06:25 Bert kernel: Loaded 43 symbols from 5 modules.
Jun 14 13:06:25 Bert kernel: Console: 8 point font, 400 scans
Jun 14 13:06:25 Bert kernel: Console: colour VGA+ 80x50, 1 virtual
console (max 63)
Jun 14 13:06:25 Bert kernel: pcibios_init : BIOS32 Service Directory
structure at 0x000f7530
Now, I only get stuff after INIT runlevel 2, after a message about
syslogd restarting e.g.
Jun 20 19:23:54 Bert syslogd 1.3-3#26: restart.
Admittedly, lots of stuff changed during the upgrade including a new
kernel, and how everything is started at boot time. I also use
a custom kernel (2.0.33), but I can't see any appropriate settings
there.
I also checked /etc/sysinit, /etc/inittab and the differences between
the
new /etc/rcS files and the old boot file saved by the upgrade as
/etc/init.d/boot.OLD, but I can't see anything significantly different
in how things boot up.
syslogd is running, but aparantly only after runlevel 2. The entries
in /etc/rc?.d and a backup from before the upgrade don't seem to have
any difference in when syslogd is started.
I still think that something in the upgade changed this, but I don't
know
what.
Note that Ole J. Tetlie wrote:
> Strange. I still get these messages in /var/log/kern.log.
>
> Jun 19 07:06:55 apollo kernel: Loaded 5380 symbols from /System.map.
> Jun 19 07:06:55 apollo kernel: Symbols match kernel version 2.1.88.
> Jun 19 07:06:55 apollo kernel: Loaded 48 symbols from 3 modules.
> Jun 19 07:06:55 apollo kernel: Linux version 2.1.88 (olet@apollo) (gcc version 2.7.2.3) #4 Sat Mar 28 16:42:18 CET 1998
[snip ...]
> | Any other ideas?
>
> Not much. I'm using the absolutely latest debian (upgraded today),
> how about you?
...
Mee Tooo ;)
Shiraz.
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: