virtualization modules (kvm-intel in my case) isnt loading automaticly
kernel doesnt manage kvm modules ?

OK, false alarm. I did a fresh install with this package today and all the symlinks are there.

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

Samba 3.6.8 released, release notes: http://samba.org/samba/history/samba-3.6.8.html

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.

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.

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

Ah, OK. Thanks for that. I was wondering why...

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.

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).

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.

Attached Thumbnails

     

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.

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"?

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.