[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: newbie question -- Using Bootlog, Startup Messages, Console

Wulfy wrote:
> man bootlogd  it's part of the sysvinit package...  :)
> wulfy@Yewdales-lodge:~$ dpkg -S bootlogd
> sysvinit: /sbin/bootlogd
> initscripts: /etc/init.d/bootlogd
> initscripts: /etc/init.d/stop-bootlogd
> initscripts: /etc/default/bootlogd
> sysvinit: /usr/share/man/man8/bootlogd.8.gz
> wulfy@Yewdales-lodge:~$ apt-cache policy sysvinit
> sysvinit:
>   Installed: 2.86.ds1-1
>   Candidate: 2.86.ds1-1
>   Version table:
>  *** 2.86.ds1-1 0
>         500 cdrom://[Debian GNU/Linux 3.1 r1 _Sarge_ - Official i386 
> Binary-1 (20051220)] sarge/main Packages
>         500 http://ftp.uk.debian.org stable/main Packages
>         100 /var/lib/dpkg/status
> hope this helps 

It certainly helps me ;-)

To follow-up on my attempt to get bootlogd working;
When trying to use KDE's Konsole and 'sudo' to enable bootlog -- here's the

~$ cd /var/log

:/var/log$ less boot
boot: Permission denied

$ sudo less boot
which then shows me no log has been created yet -- so I try;

$ sudo /sbin/bootlogd -lps
bootlogd: cannot find console device 136:2 in /dev

So now I'm searching for "136:2" and have no idea why it's looking for that,
and the /dev dir is HUGE ;-0

So I drop to a VT/VC (ctrl-alt-f2) and login as root;
then rerun above command '/sbin/bootlogd -lps'

and it *seems* to have taken affect -- but i guess i won't know for sure until
I reboot...well here goes ;-)


Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 

Reply to: