2010. február 24. 13:35 napon Anton Aylward írta:

Istvan Gabor said the following on 02/24/2010 05:00 AM:

[snip]

...

It is a desktop with a CRT monitor connected by a VGA cabel, not DVI. But as I recall my installation, it might be related to the thing I chose 'server installation' at very first time without any graphical interface, and added X and graphical stuff after that.

Could be. openSuse is on my laptop so I don't have that problem. My server is headless so I never see that issue anyway; just the results of the logs.

...

When the system boots both the graphical and text boot screens are shown on this monitor without any problem, the boot messages are scrolling through the screen. If I login in the first terminal window according to 'w' command it is tty1.

Istvan, can't you take a hint? Both Patrick and I have gone on about greping relevant files. (to say nothing of reading man pages!)

Well, I did take Patrick's hint (# grep -e -C /etc/init.d/boot.d/*), that's how I found about /etc/init.d/boot.rootfsck and /etc/init.d/boot.localfs files.

You showed the line from /etc/init.d/boot.rootfsck:

if test "$REDIRECT" = "/dev/tty1" ; then

Doesn't it occur to you to find out HOW the variable REDIRECT was set in the first place? Go grep. Go look for the commands that set it. Go think what CONTEXT was running when it was set, cos it certainly wasn't the xterm, the GUI wasn't running, and you can arbitrarily hot-key and login at any terminal window, and YOU WEREN'T LOGGED IN at boot time.

Absolutely I would like (and wanted) to know how REDIRECT is set but interpreting bash scripts is way beyond my knowledge. I can understand only very basic things, like "if test "$REDIRECT" = "/dev/tty1" ; then" but not things like &&, -z, and certainly not something like this: test -z "$CONSOLE" && CONSOLE=/dev/console REDIRECT="$(showconsole 2>/dev/null)" export CONSOLE REDIRECT

Go read the manual page on the shell and consider how you would add trace and debug to 'boot.roofsck' and how, since you're not logged in, you would monitor and control it.

This is something I can not do either.

You're not approaching this in a methodological and logical manner no matter what hints Patrick and I give you. You are making us do all the work for you.

Well, that's not the case. I followed your advice every time, that's how I found tune2fs which I did not know before, I read e2fsck as you suggested. I followed Patrick's advice as well, see above. But I can not do things that are beyond my computer knowledge. If could I would not have asked the question here but would have solved it myself. I followed your hint as well, and I got: /etc/init.d # grep REDIRECT * but the result was too overwhelming for me. Anyway, thanks for your help, I appreciate it. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

2010. február 24. 16:15 napon Ken Schneider - openSUSE írta:

On 02/24/2010 09:59 AM, Istvan Gabor pecked at the keyboard and wrote:

[snip]

test -z "$CONSOLE" && CONSOLE-/dev/console

means to test if the variable CONSOLE is empty and if it is set it to /dev/console. If the variable is not empty go to the next line.

The next line sets the variable REDIRECT to the value of the result of the command showconsole. (I'm pretty sure but not 100%.)

The last line exports the value of the tow variables globally.

Ken, thanks for explaining. I wish I had more time to learn all this stuff. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Charles Obler said the following on 02/24/2010 05:35 PM:

...

Ken, thanks for explaining. I wish I had more time to learn all this stuff.

Istvan

Here's a terrific bash tutorial.

http://www.tldp.org/LDP/abs/html/

It's one of my favorite tutorials. Bash is a surprisingly powerful language, and it's fun to code in.

That's a great tutorial, Charles! I love that introduction: <quote> A working knowledge of shell scripting is essential to anyone wishing to become reasonably proficient at system administration, even if they do not anticipate ever having to actually write a script. Consider that as a Linux machine boots up, it executes the shell scripts in /etc/rc.d to restore the system configuration and set up services. A detailed understanding of these startup scripts is important for analyzing the behavior of a system, and possibly modifying it. The craft of scripting is not hard to master, since the scripts can be built in bite-sized sections and there is only a fairly small set of shell-specific operators and options [1] to learn. The syntax is simple and straightforward, similar to that of invoking and chaining together utilities at the command line, and there are only a few "rules" governing their use. Most short scripts work right the first time, and debugging even the longer ones is straightforward. </quote> Istvan, you say you don't have time to learn? Well I think you don't have time NOT to. Its not as if you have to learn it ALL at once, like some languages I could mention. (One of my hates of Mandriva was that so much of the admin stuff was done in Perl and geared for Gnome.) -- Every civilization that has ever existed has ultimately collapsed. -- Henry Kissinger -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org