by Robert Stockma » Mon, 02 May 1994 04:08:38
With slackware 1.1.1 and 1.2.0 the file /usr/adm/kernel
is missing. With editing /etc/syslog.conf one can
make a entry for this file. But after startup this
file is 0 bytes in size. The boot messages which show
up before init and syslogd are invoked aren't logged
in the file /usr/adm/kernel.
How can one enable this?
by a.. » Tue, 10 May 1994 04:41:14
My old setup was based on SLS 1.01 and SLS 1.03, with 0.99.13 being the
latest kernel on the system, and all the boot messages showed up in
/var/adm/messages and /var/adm/syslog.
Since I blew away my /usr partition and installed Slackware from scratch
they don't show up at all!
Any hints as to why this has changed would be appreciated!
(Is it the setup, or possibly the kernel version..?)
Andrew.
+--------------------------------------------------------------------------
| Andrew *, Dept. of Computer Science, | Run, run, as fast as you can |
| University of York, York, YO1 5DD, England | you can't catch me, I'm the |
+--------------------------------------------------------------------------
1. Red Hat 6.0 && init messages && new kernel
I have been using Linux since around 2.0.30 and Red Hat 4.2. I
currently have a Red Hat 5.2 box with a 2.2.10 kernel, and a new Red Hat
6.0 box with a 2.2.10 kernel as well. I got 6.0 from CheapBytes
(unoffical, no docs).
My problem: booting the 2.2.5-15 kernel from Red Hat, I get the usual
page or so of kernel messages, and the output from the init scripts
(with the nice green OK's along the right side...nice touch ;-).
Booting the 2.2.10 kernel I compiled, I get "Loading Linux...OK, booting
the kernel." and _nothing_ more until the login prompt. I used to be
quite comfortable compiling my own kernel...<sigh>. It seems like I
remember a kernel config option about verbose hardware detection
messages or something very similar, but I didn't find it in the 2.2.10
config options. But should a different kernel affect the output from
the 'init' scripts?!
If anyone has any ideas or needs more details, please say something.
This is really frustrating, and somewhat humiliating. Thanks.
Eric
3. syslogd failed to log message to /var/adm/messages
5. Netboot & init:: Boot process hangs at init
6. Will a close on an XOFFed tty block forever?
7. Linux won't boot past "INIT version 2.62 boot" message at bootup
8. slurp
9. init 2.76 hangs on boot -- not running /sbin/init.d/boot
10. Avoid message logging (syslogd)
11. SERIOUS PROBLEM: syslogd: cannot register to log console messages
12. Logging boot messages(and crash messages)
13. Syslogd to log messages from other host?