Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello all, resident Linux newb here. Just installed Slackware 11 and got it going (I guess), I have a lot of questions that may seem extremely trivial but for some reason have escaped all logical thought:
Apparently Slackware decided to forget to install ifconfig? It's not in /sbin
Code:
# /sbin/ifconfig
-bash: /sbin/ifconfig: No such file or directory
I'm not even sure I can get on the internet. No commands I am familiar with work (apt-get, wget) How am I supposed to get all of the necessary drivers and stuff that these 'basic' Linux guides point to?
X11 won't startup because of an error 104
Code:
...
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/name:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
...
Fatal server error:
no screens found
fatal IO error 104 (Connection reset by peer) on X server ":0.0"
My Slackware installation also seemed to skip over the entire network setup portion, is this normal? Sorry for the newb questions but I'm really quite lost.
Last edited by DarkShade9; 12-31-2006 at 07:06 AM.
Sounds like you don't have a package called tcptools or iptools or someting. I once forgot to install that(actually, it wasn't a mistake) and got similar errors. Install the package(some slacker might be here to say the exact name) and run netconfig(I think that is the name). You should be up running after that.
Cheers.
Don't go making a minimal install if you don't know what the various packages do. At least do one install in newbie mode and read everything. The packages tcpip and dhcpcd should be enough to get you online, unless you need any additional drivers etc.
If you can't find a file you know you should have, go to http://packages.slackware.it/ and search for the file there using "file name". Be sure to select the right slack version as well. Install the package you find that contains the file you need.
edit:
For the X error, try setting up X over again using xorgsetup and xorgconfig, in that order. Be sure to copy over whatever new xorg.conf file that gets generated. If that still won't work, you might be lacking some drivers in your kernel.
Quote:
Originally Posted by DarkShade9
My Slackware installation also seemed to skip over the entire network setup portion, is this normal? Sorry for the newb questions but I'm really quite lost.
I've had that happen a few times, I think it might be the same thing, that you didn't install tcpip (or any /n packages for that matter).
Don't go making a minimal install if you don't know what the various packages do. At least do one install in newbie mode and read everything. The packages tcpip and dhcpcd should be enough to get you online, unless you need any additional drivers etc.
If you can't find a file you know you should have, go to http://packages.slackware.it/ and search for the file there using "file name". Be sure to select the right slack version as well. Install the package you find that contains the file you need.
edit:
For the X error, try setting up X over again using xorgsetup and xorgconfig, in that order. Be sure to copy over whatever new xorg.conf file that gets generated. If that still won't work, you might be lacking some drivers in your kernel.
I've had that happen a few times, I think it might be the same thing, that you didn't install tcpip (or any /n packages for that matter).
I did a full install, everything was [x] except for KDEi. After fooling around with it a bit, I managed to manually installpkg * all necessary tools (ifconfig, wget) but I still can't get Xfree86 to work. I never got it to work on my OS X box either. Is the xf86 installer on the slackware discs current or should I download the newest version? The farthest I ever got with it was when I did a startx with a new .conf and the display turned grey and I had a big black X in the middle of the screen, and it was mouse controlled, but nothing else came up.
Thanks for all the help so far. I figure if I can get Slackware running, I can get a lot of other distros going.
what version of slack are you running currently pretty much everything is using x.org stuff. Try using the xorg commands xorg setup ( what debian does during the installer) and xorgconfig to get it really working. I have no x with out running those. If you need to install packages that you think its missed you can re-run install scripts using pkgtool
i had similar problems with X, running xorgsetup or xorgconfig did not work for my box. I had to manually make changes to these file to get them working.
i suppose first i should make sure you have run either xorgsetup or xorgconfig (as root) and then tried startx as a user?
Okay, finally, I got things working. Thank you all for your help so far. Only a few more hurdles to get over and then I'll be very happy.
How do I get the computer to autoboot into Linux? I have no other OS on the drives. Do I just comment out the booting into Windows part in /etc/lilo.conf?
Can I get it to automatically login as a user? I'm looking to make this a headless server so I can vnc into it from another computer.
Why does it always forget my ifconfig configuration? If I logout, it loses all of that info, and I have to put it back in. I made a shell script to do it but it really shouldn't forget my settings.
Basically, I just want it to do this:
I turn computer on
It autoboots into Linux
It autologs into a user
It remembers my network settings (or I can just have it run the network script at startup)
It launches vncserver
Done.
I kind of know how to do this in OS X but login items I was never good at.
to autoboot Linux, you'll want to comment out the Windows info in /etc/lilo.conf and change the timeout from 1200 (I think that's the default) to something like 50 (five second should be enough time if you need to enter something else at the lilo prompt, the countdown stops when you start typing.) then you absolutely need to run '/sbin/lilo' as root to make the changes take effect.
I think the easiest way to autologin to your Desktop Environment (I'll assume KDE) it to change your /etc/inittab line that says:
Code:
# Default runlevel. (Do not set to 0 or 6)
id:3:initdefault:
so that it says
Code:
# Default runlevel. (Do not set to 0 or 6)
id:4:initdefault:
That will enable a graphical login rather than the default Text mode login. Then you can use KDM to automatically log you in (it's in the KDE preferences somewhere...)
If for some reason you need to login to runlevel 3 (X stops working or you just want to spend some quality time with the CLI) you can type "Linux 3" at the lilo screen (replace "Linux" with whatever name lilo is associating with your slackware install) and you will go to Runlevel 3 instaed of 4
I don't know how to make it remember your network settings... maybe add a script to /etc/rc.d/rc.local to load them at boot for you?[Hrm... I just saw the part of your post where you said you don't want to use a script.... sorry I can't be of more help] That could be done for vncserver as well I believe.
Last edited by truthfatal; 01-03-2007 at 10:10 PM.
Change the timeout settings in lilo.conf, or comment out the windows portion and the 'prompt' line. But run 'lilo' as root right after you edit lilo.conf.
As for:
Quote:
Originally Posted by DarkShade9
It autologs into a user
Use the KDE Login manager. You can tell it not to require a pass/autologin.
Quote:
Originally Posted by DarkShade9
It remembers my network settings (or I can just have it run the network script at startup)
Just edit /etc/rc.d/rc.inet1.conf with whatever you need: ip address, gateways, dhcp, whatever. No need to run a script.
Great, thank you all for your help. Everything is nicely setup now. Linux auto-loads, I can make it headless now as I ssh from my OS X machine to login, and then VNC controls the desktop, exactly what I wanted.
I know this all sounds elementary and trivial but it's a nice place to be from where I was last week.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.