Slackware

[Hunted]

Alright, I was able to create my username with no problems

[LSA]

Originally posted by Hunted@4 March 2004 - 17:51
Alright, I was able to create my username with no problems

Can you startx?

[Hunted]

Originally posted by LSA+4 March 2004 - 19:54--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (LSA @ 4 March 2004 - 19:54)</td></tr><tr><td id='QUOTE'> <!--QuoteBegin-Hunted@4 March 2004 - 17:51
Alright, I was able to create my username with no problems

Can you startx? [/b][/quote]
Nope, same problem still

[LSA]

Are there any error messages?

Did you install it right?

[Hunted]

Nope, as was installing it, I had no problems

[LSA]

What runlevel are you in?

/sbin/runlevel

http://www.bilbos-stekkie.com/slack_init/e...ex.php?action=5

Slackware init&#39;s and runlevels

[Hunted]

N 3

[LSA]

# These are the default runlevels in Slackware:
#&nbsp; 0 = halt
#&nbsp; 1 = single user mode
#&nbsp; 2 = unused (but configured the same as runlevel 3)
#&nbsp; 3 = multiuser mode (default Slackware runlevel)
#&nbsp; 4 = X11 with KDM/GDM/XDM (session managers)
#&nbsp; 5 = unused (but configured the same as runlevel 3)
#&nbsp; 6 = reboot

Go to 4

Originally posted by IBM tut

telinit command: Changing runlevels on a running system

The telinit command is the way to change runlevels. When you execute telinit S as root (or whatever runlevel you&#39;d like to change to), it changes runlevels, shuts down the prior runlevel, and then starts up the next one.

In a way, you are rebooting parts of the system. However, the ability to shutdown and restart services is one of Linux&#39;s most endearing qualities. Need to change the IP address for your machine? No problem, make a few changes and restart your networking services. As long as everything is configured correctly you&#39;re back up and running so quickly it&#39;s hard to tell anything has changed. Try doing that on other operating systems where you have to reboot just because you&#39;ve changed wallpaper on your desktop

The only time it&#39;s really necessary to reboot or completely shut down a Linux box is if you&#39;re adding or changing hardware, assuming you&#39;re working with a device that isn&#39;t hot-swappable, or if you&#39;ve had a break in and need to take the machine offline to repair the damage. Unlike other operating systems, I&#39;ve never seen rebooting solve a problem on a production system that couldn&#39;t be solved without rebooting. I have managed to hang non-production machines by playing around with commands like hdparm, but I expected it to happen.

Let&#39;s say you need to perform some system maintenance that requires having the system in single-user mode. For instance, tuning your hard drive with hdparm. The first step is to su to root.

Then we&#39;ll execute the telinit command to bring the system into single-user mode:


telinit S -t 60

The "-t" argument is optional; it tells telinit to wait 60 seconds before actually performing the switch to single-user mode. However, as soon as the command is executed, anyone who is logged into the machine will get a warning on their console that the system is going to switch runlevels or go down in 60 seconds.

When the 60 seconds are up, init shuts down the processes that aren&#39;t used in the single-user mode and brings the system back up in single-user only mode. You&#39;ll then be prompted for the root password to perform system maintenance.

The process the system uses to get into single user mode is a bit different. The default for single user mode calls for init to invoke the sulogin command on the console and requiring a root login to work in single user mode.

After the system enters single user mode you should see a message like this:


&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Give root password for system maintenance
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (or type Control-D for normal startup):

Once you&#39;ve performed your maintenance you can bring the system back up by executing this command:


telinit 3

This tells the system to re-enter a multi-user runlevel. You could substitute "2" or "4" for "3" in this command. On Slackware systems runlevel 4 will put you in multi-user mode with one of the X display managers, so you will log directly into X.

If you have a UPS hooked up to your system that has a serial cable, it&#39;s possible to have the UPS send your system a signal in the event that power goes out. This is very useful if you have a production-class system with a large filesystem. I&#39;ve seen what happens when a 100GB RAID ext2 filesystem is not cleanly unmounted (fsck takes about four hours to complete). On the other hand, a properly configured UPS can alert the system of the power outage and send telinit/init the SIGPWR signal, which will cause init to bring the system into single-user mode or shut the system down altogether, depending on how it&#39;s configured.

[Hunted]

-_- I typed in telinit 4, it was working, then the same thing happend when I ran startx

[Hunted]

I might try another distro. What do you suggest, besides Mandrake (I want to use, but I can&#39;t use it), FreeBSD (also want to use, but cannot install KDE), Redhat (don&#39;t care for it), LindowsOS (SUCKS)