Slackware This Forum is for the discussion of Slackware Linux.
|
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
|
09-16-2012, 06:25 PM
|
#196
|
LQ Newbie
Registered: Aug 2012
Posts: 23
Rep: 
|
virtualization modules (kvm-intel in my case) isnt loading automaticly
kernel doesnt manage kvm modules ?
Last edited by abstradelic; 09-20-2012 at 07:57 AM.
|
|
|
09-17-2012, 12:46 AM
|
#197
|
Member
Registered: Jun 2004
Distribution: Slackware
Posts: 241
Rep:
|
Quote:
Originally Posted by elyk
Hmm, maybe this already got fixed in ca-certificates-20120623-noarch-2. I'll have to try it.
|
OK, false alarm. I did a fresh install with this package today and all the symlinks are there.
|
|
|
09-17-2012, 01:10 PM
|
#198
|
LQ Newbie
Registered: Jan 2012
Location: Hong Kong
Distribution: Slackware
Posts: 18
Rep: 
|
sorry i think i should have made the following thread in this post, because the visible bell should be included in linux console by default
http://www.linuxquestions.org/questi...le-4175427273/
in the etc-14.0-* package,
add the following line on etc/termcap under the "#Slackware 3.1 liunx...." session
:vb=\E7\E[?5h\E[?5l\E8:\
so we can have visible bell on linux console.
btw, i know nothing about termcap, i just know it works, one should review it before making the change
|
|
|
09-18-2012, 01:34 AM
|
#199
|
Member
Registered: Jan 2008
Posts: 426
|
|
|
|
09-18-2012, 04:04 AM
|
#200
|
Member
Registered: Feb 2008
Distribution: Slackware
Posts: 595
Rep: 
|
Just a note, though I've mailed Pat about it..
A quick "grep -R '13\.37' /mirror/slackware/slackware-current/" reveals a number of documents that still need an update pre-release, such as README.TXT, README_LVM.TXT, README_PXE.TXT & README_CRYPT.TXT.
|
|
|
09-18-2012, 05:33 AM
|
#201
|
Senior Member
Registered: Nov 2002
Location: Birmingham UK
Distribution: Various
Posts: 1,736
Rep: 
|
Installed it on an Asus X54C laptop. Everything works. Wifi worked "out of the box". I close the lid and it goes to sleep. I open it and it springs back into life. Last time I tried that with Linux on a laptop (some 7 years ago I'll grant you), the result was a dreadful mess.
Network manager is still not started on first boot.
Other than that, all good.
Looking forward to the final release.
|
|
|
09-18-2012, 07:20 AM
|
#202
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559
|
Quote:
Originally Posted by salparadise
Network manager is still not started on first boot.
|
You have to run "chmod +x /etc/rc.d/rc.networkmanager" yourself first. The script is installed non-executable by default so that it won't mess up systems which use the traditional Slackware network configuration via rc.inet1.conf.
Eric
|
|
|
09-18-2012, 07:45 AM
|
#203
|
Senior Member
Registered: Nov 2002
Location: Birmingham UK
Distribution: Various
Posts: 1,736
Rep: 
|
Ah, OK. Thanks for that. I was wondering why...
|
|
|
09-18-2012, 11:38 AM
|
#204
|
Slackware Maintainer
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 3,177
|
Quote:
Originally Posted by Alien Bob
You have to run "chmod +x /etc/rc.d/rc.networkmanager" yourself first. The script is installed non-executable by default so that it won't mess up systems which use the traditional Slackware network configuration via rc.inet1.conf.
Eric
|
If NetworkManager was chosen in the installer's network setup, it should chmod +x /etc/rc.d/rc.networkmanager for you. Is that not working?
|
|
|
09-18-2012, 12:28 PM
|
#205
|
Senior Member
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,559
|
Quote:
Originally Posted by volkerdi
If NetworkManager was chosen in the installer's network setup, it should chmod +x /etc/rc.d/rc.networkmanager for you. Is that not working?
|
Pretty certain it did work like that for me (the installer did the job for me when I selected Network Manager) on my last Slackware current install.
Last edited by ruario; 09-18-2012 at 12:29 PM.
Reason: s/sure/certain/
|
|
|
09-18-2012, 12:50 PM
|
#206
|
Senior Member
Registered: Nov 2002
Location: Birmingham UK
Distribution: Various
Posts: 1,736
Rep: 
|
I installed everything except emacs, xfce and games. I've installed each RC for SLW14 and each time network manager is not started. I must admit I was thinking "this can't be right", until I read Alien Bob's reply. It still seems a little unusual (though not a problem to sort out).
|
|
|
09-18-2012, 01:42 PM
|
#207
|
Senior Member
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,559
|
Quote:
Originally Posted by salparadise
I've installed each RC for SLW14 and each time network manager is not started.
|
Are you sure you actually selected it to manage your networks during installation. It is the very bottom option and is not highlighted by default. It is easy to miss if you usually pick static or dhcp, since it is a new option and old habits die hard.
I just did a very quick test install using a Slackware64 current DVD I created just after RC4 was released. I specifically set Network Manager to manage my networking setup during installation and afterwards it was enabled without me having to manually "chmod +x" it. See attached screenshots.
EDIT: For the eagle eyed, the hostnames in the first and last screenshots don't match because I chrooted into my newly installed Slackware after setup had finished, rather than rebooting.
Last edited by ruario; 09-18-2012 at 01:52 PM.
Reason: Added quote; added clarification comment about hostnames in screenshots
|
|
|
09-18-2012, 01:45 PM
|
#208
|
Senior Member
Registered: Nov 2002
Location: Birmingham UK
Distribution: Various
Posts: 1,736
Rep: 
|
Ahh. Right.
Sorted.
I'm so used to rattling through the Slackware installer that I had missed that. If the default is "DHCP" I would not have changed that setting.
Now I know.
Many thanks.
|
|
|
09-18-2012, 01:47 PM
|
#209
|
Member
Registered: Aug 2011
Posts: 295
Rep: 
|
Quote:
I installed everything except emacs, xfce and games.
|
WTF???
I can understand someone who does not install emacs or xfce, but why the hell would someone install no games? What do you do when you have to compile something and have nothing else to do? Opening a terminal, tipping "trek" and blowing Klingons with photonic torpedoes at the shell is one of the few things you can do to prevent the waiting from making you insane!!
Hahaha, just kidding. But there are good games in that old BSD collection.
Now back to serious business. Has someone who had a problem with "eject -T" (discussed here) had their problems solved with the update issued on "Tue Sep 4 21:54:46 UTC 2012"?
Last edited by BlackRider; 09-18-2012 at 01:49 PM.
|
|
|
09-18-2012, 01:58 PM
|
#210
|
Senior Member
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,559
|
Quote:
Originally Posted by salparadise
Ahh. Right.
Sorted.
I'm so used to rattling through the Slackware installer that I had missed that. If the default is "DHCP" I would not have changed that setting.
Now I know.
Many thanks.
|
Yes, DHCP is indeed the default. No problem, I was fairly sure this was the reason. Once you have done that install a few times it is so easy to motor through it at breakneck pace. 
|
|
|
All times are GMT -5. The time now is 06:32 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|