I am working with opensuse 11.3 and I have dual system (with win7).Most of the day 90% I am working in other than win7/of course openSuSE.In fact I have installed as virtual machines :Mac Os,PCBSD,Debian and win XP ,all 4 in opensSuSE.Why?Because I want to test them and I want to know how they work and what are the difference between them/if I can see.Sometime I open a virtual machine /operate with it and also I did a USB stick live bootable with kubuntu 10.4.
This is the situation and my laptop has 4Gb RAM ,350 Gb hard drive and 2 processors Intel with 2 GB each.
All are fine but to maintain/manage all these is I MUST KNOW if something it’s wrong.
And is my personal laptop that I am using at my workplace,I preferred this to work more time in Linux/my colleagues are using windows family/vista,xp,7,it doesn’t matter.
Of course I looked in var/log for read it.
But I want to know for sure wich is the logfile that stores information when my PC starts/boots.In older versions of SuSE I knew but for opensuse 11.3 really I don’t know.Maybe this can be created by a command ,or it’s stored in other path ,I would like to know exactly.
This is my request for the friends that read this text.
Please ,give me some help,I think it should not be so difficult ,for manny ,but I am sick to dig all the time without be sure,and I know the solution is here in this forum.
I believe this logfile has extremly importance for the health of the hardware/software of the PC.
So what I need is a path or “how to do”.
I am looking for it.
Thank you to all.
Merry Christmas!
Happy New Year!
Pushy, in addition the very fine responses you have received, may I suggest a script file that allows you to examine many of those log files that you seek. Here is a url to its location:
The script is called slave and message #11 shows the most recent version. Copy and paste into a text editor, save as the file slave in your /home/username/bin folder (insert your name in place of user name). Use the terminal command chmod +x ~/bin/slave to make it executable. Open up another terminal session and type the command slave. These instructions appear again with the script file text.
One could also put this script in /usr/local/bin/, which (according to the Filesystem Hierarchy Standard) is the proper place for such things (for executables which are not managed by the package manager). If doing so, it can be used systemwide.
Thank you to all,I put the question because I compared the information from the screen when the PC starts and the text from var/log/boot.msg,boot.omsg ,boot.log etc but I don’t see the same text as in the black screen after start for example in boot.msg .for this reason I asked (I told you before that I read the text files about booting from var/log),that 's way I mentioned I want to be 100% sure about the right file.
I am going to use your knowledge put above by you dear suse friends.
On 2010-12-24 11:06, Pushy wrote:
>
> Thank you to all,I put the question because I compared the information
> from the screen when the PC starts and the text from
> var/log/boot.msg,boot.omsg ,boot.log etc but I don’t see the same text
> as in the black screen after start for example in boot.msg
What exactly do you expect to find that you do not see?
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
ne could also put this script in /usr/local/bin/, which (according to the Filesystem Hierarchy Standard) is the proper place for such things (for executables which are not managed by the package manager). If doing so, it can be used systemwide.
Good morning to you gropiuskalle on this fine Christmas eve. /usr/local/bin/ is in everyone’s path and would work fine for scripts to be shared with all users. But, you must be root to save or edit any files placed there. My thinking is that they should go into each users own bin folder, where they can edit and save the files without root permissions. Only when a PC is being used by more than one person would you need to consider using this folder, but again it is the right place to share the same script between multiple users.
And thanks for your comments and you have a very Merry Christmas!
As often, there are many approaches and various ways to deal with an issue. I prefer the “official” ways and sticking to certain standards (and I personally do not see a problem moving a script to another path as root, as long as it is clear that the source of it can be trusted - I’m sure you agree that this should always be carefully checked), but that’s definitely not the only way that will work. For a single user, your way will work perfectly well too. It’s just that I don’t like yet another folder in my /home is all.