[SOLVED] how to get back source file as well as check whether x-win is xfce?

bsmile · 11-12-2017, 03:57 PM

I tried to reduce space so I skipped getting the source file in time of installation, which turns out to be a big mistake. Now how can I possibly get the source file back to its intended location within the installed slackware instead of reinstalling it in the virtualbox? (I have reinstalled slackware with source files included, so this should not be an issue any more.)

Also the GUI looks very much like KDE although I specifically chose xfce as default, how can I double check that the current desktop is xfce instead of KDE? If KDE, how can I change to xfce for the next reboot?

I don't like to wait at the beginning of linux reboot, where can I change the booting setting to boot immediately?

bsmile · 11-12-2017, 04:12 PM

just checked by setting /etc/inittab option 4 to 3 and reboot the system, then issue startxfce4 at command line to manually initialize xfce, and it turns out that indeed the system automatically goes to kde at booting time although I set the default to be xfce. I also checked with xwmconfig and indeed the default is xfce4, so how can I possibly do with this situation? Thanks,

Alien Bob · 11-12-2017, 04:34 PM

Runlevel 3 (console login) uses xwmconfig where you selected XFCE as the default. But in runlevel 4, when the display manager starts (which will be KDM if you did a full install) you make the choice of your desktop in the KDM dropdown menu before you login. That choice you make will remain the default afterwards, but you are correct that the initial OS default will be KDE.

bsmile · 11-12-2017, 04:40 PM

I tried to make xfce as my default desktop by consulting https://superuser.com/questions/6859...t-system-start to manually revise it to be xfce, which works, but this is really not what I want as it seems I cannot change my default to KDE if needed. Also, it seems the very initial x is still KDE by that way, although after log in it changes to xfce. Is this what Alien mentioned "the initial OS default will be KDE"? Thanks

bsmile · 11-12-2017, 04:46 PM

Quote:

Originally Posted by Alien Bob

Runlevel 3 (console login) uses xwmconfig where you selected XFCE as the default. But in runlevel 4, when the display manager starts (which will be KDM if you did a full install) you make the choice of your desktop in the KDM dropdown menu before you login. That choice you make will remain the default afterwards, but you are correct that the initial OS default will be KDE.

Thanks for your input. I don't understand two things,

If runlevel 3, then it will stop at command line and I have to manually input startxfce4 to enter xfce.
If runlevel 4, I don't quite remember I had seen any dropdown menu during system booting.

Did I do anything wrong?

(It seems I cannot delete my post after it is posted, is this the case in LQ?)

Alien Bob · 11-12-2017, 05:11 PM

Quote:

Originally Posted by bsmile

Thanks for your input. I don't understand two things,
If runlevel 3, then it will stop at command line and I have to manually input startxfce4 to enter xfce.

No. You run "xwmconfig" to select your default desktop, and then you run "startx" to start X with that default desktop. You should not have a reason to run startxfce4 directly.

Quote:

If runlevel 4, I don't quite remember I had seen any dropdown menu during system booting.
Did I do anything wrong?

Look again. If there's no session selection to be found then perhaps you are not starting KDM but XDM - in which case you did not perform a full install.

Quote:

(It seems I cannot delete my post after it is posted, is this the case in LQ?)

Deleting posts after you posted them is sneaky. What you can do is alter the text of your post after posting it. But I would suggest you only do that to add information, not to remove information.

Gerard Lally · 11-12-2017, 05:12 PM

Quote:

Originally Posted by bsmile

I don't like to wait at the beginning of linux reboot, where can I change the booting setting to boot immediately?

Change /etc/lilo.conf and run lilo afterwards:

Code:

# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 30     # 3 seconds

Alien Bob · 11-12-2017, 05:13 PM

Quote:

Originally Posted by bsmile

I tried to reduce space so I skipped getting the source file in time of installation, which turns out to be a big mistake. Now how can I possibly get the source file back to its intended location within the installed slackware instead of reinstalling it in the virtualbox? (I have reinstalled slackware with source files included, so this should not be an issue any more.)

This part of your OP does not make sense. Slackware runs just fine without adding all its source code. The only useful package which contains actual source code is the "kernel-source" package and you only need that one if you want to build a tweaked kernel of your own, or in case you want to compile a 3rd-party kernel module.

bsmile · 11-12-2017, 05:37 PM

Quote:

Originally Posted by Alien Bob

This part of your OP does not make sense. Slackware runs just fine without adding all its source code. The only useful package which contains actual source code is the "kernel-source" package and you only need that one if you want to build a tweaked kernel of your own, or in case you want to compile a 3rd-party kernel module.

I think I had skipped the kernel-source package when installing the slackware, which caused the issue. Now I reinstalled the system with the source files included, install guest addition is not an issue any more.

magicm · 11-12-2017, 05:56 PM

Quote:

I don't like to wait at the beginning of linux reboot, where can I change the booting setting to boot immediately?

Although, @Gerard Lally response will reduce the pause to 3 seconds, if you really want to boot immediately, there's a section in /etc/lilo.conf (when generated by 'liloconfig')

Code:

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
# prompt

Uncomment the prompt line (remove the leading #), and then run lilo

Change /etc/lilo.conf and run lilo afterwards:

Of course this assumes you only have one OS to manage

bsmile · 11-12-2017, 07:20 PM

Quote:

Originally Posted by magicm

Although, @Gerard Lally response will reduce the pause to 3 seconds, if you really want to boot immediately, there's a section in /etc/lilo.conf (when generated by 'liloconfig')

Code:

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
# prompt

Uncomment the prompt line (remove the leading #), and then run lilo

Change /etc/lilo.conf and run lilo afterwards:

Of course this assumes you only have one OS to manage

Thanks for your help, this issue is finally resolved. Another similar issue is a username/password needs to be input before the booting can proceed. Is there way to let OS choose the default username to log in without asking for password? (like what is done with ubuntu: https://askubuntu.com/questions/1752...rdin-text-mode) Thanks,

Gordie · 11-12-2017, 08:38 PM

Quote:

Originally Posted by bsmile

Thanks for your help, this issue is finally resolved. Another similar issue is a username/password needs to be input before the booting can proceed. Is there way to let OS choose the default username to log in without asking for password? (like what is done with ubuntu: https://askubuntu.com/questions/1752...rdin-text-mode) Thanks,

You really should mark this thread as solved and start a new thread for your new question.

AFAIK it will only work for KDE