You are not logged in.
Lately I've been getting a warning at boot about some config file not being in .conf format mentioning it may not be compatible with future releases. (Sorry for not being very exact, I can't seem to find it in my system logs anywhere, hence my posting!)
I'd like to know which of the dozen log files is the one displaying things you see at boot?
What is the best/easiest way to search the log?
Are there any programs to search your system logs?
I tried finding some programs, but have had no luck. I also tried opening the logs in leafpad and searching that way, but haven't found anything resembling the message from booting up. I have searched the "everything" log for "warning" case insensitive, and didn't find anything about the config file anywhere.
Last edited by oni5115 (2009-07-14 12:57:37)
Offline
I've wondered about the same thing lots of times, I've found one partial solution but it's very very imperfect..
http://wiki.archlinux.org/index.php/Pos … ot_Process
It's not how to read boot log files but to pause before displaying the login prompt..
Last edited by fgrano (2009-07-14 11:50:36)
Offline
This error is caused by the new module-init-tools package,you can read about it here: http://www.archlinux.org/news/450/
Offline
Thanks, both are good to know. Should be fixed now.
Offline
I get etc/modprobe.d/framebuffer_blacklist.conf error during boot. Looking in /etc/modprobe.d shows framebuffer_blacklist.conf and framebuffer_blacklist.pacsave both files with same info. $ cat modprobe.conf shows /etc/modprobe.d/modprobe.conf.
Offline
Are you sure you don't get the error about the pacsave file?
Offline
Yes I got error messages about ...blacklist.conf and ...blacklist.pacsave in triplet. Removing the /etc/modprobe.d/framebuffer_blacklist.pacsave file stopped the error messages. Hope it doesn't "come to bite me in the ass" later:).
Offline
This issue had been discussed already. I delayed to answer as newcomers are sluggish in searching the forum.
http://www.archlinux.org/news/450/ discuss about the changes and what the end user is to take action. lestoil, rename all the files in the /etc/modprobe.d with the extension .conf. deleting a file is not a solution.
Last edited by kgas (2009-07-18 12:16:48)
Offline