SlackwareThis 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.
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.
I started playing with the 2.6.32 kernel a short while back to hopefully get the driver for my Dell laptop's video working. Still working on that and it is another post.
The use of the new kernel mods to allow the use of 'make localmodconfig' will aid those that want a easier method of kernel builds for their Slackware install.
There are too many improvements to list here so I suggest that you look at 'Linux 2 6 32';
Quote:
Linux 2.6.32 has been released on December 3rd 2009.
Summary: This version adds virtualization memory de-duplicacion, a rewrite of the writeback code which provides noticeable performance speedups, many important Btrfs improvements and speedups, ATI R600/R700 3D and KMS support and other graphic improvements, a CFQ low latency mode, tracing improvements including a "perf timechart" tool that tries to be a better bootchart, soft limits in the memory controller, support for the S+Core architecture, support for Intel Moorestown and its new firmware interface, run time power management support, and many other improvements and new drivers.
1 members found this post helpful.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Mon Jan 4 21:43:02 UTC 2010
New kernels... and this deserves a mention/warning: the last bits of the
"old" IDE/ATA system have been removed now. Everything should be using
the libata based drivers now, so if you have any drives that are currently
running as /dev/hda, /dev/hdb, etc., when you reboot with these kernels all
drives will be renamed as /dev/sda, /dev/sdb, etc. If you had any /dev/sd*
already, they might get renamed. Adjustments may be required in
/etc/lilo.conf, /etc/fstab, the initrd, and elsewhere. Good luck!
Be sure to read the HOWTO 'libata_switchover' by rworkman if you plan on using the updated kernel from '-current'.
Major Changes:
- Connection information is available by right clicking the tray icon
- Can set the hostname per network for all DHCP clients
- urwid 0.9.9 is now supported
- Added wicd-cli, a command line interface for use in scripts
- Global scripts are now passed parameters specifying the network
Minor Changes:
- Support for only displaying notifications using -o to wicd-client
- Reconnecting now works when measuring signal strength in dBm
- ESSIDs made of numbers now work properly
- All valid wpa_supplicant drivers are now displayed
- Wired network is now displayed while scanning wireless networks
- Added wicd-gtk, a command to always and only run the GTK UI
- Marked ioctl backend not supported
- Use dhcpcd-bin on Debian instead of dhcpcd script
with the phrase "subscribe [name of list]" in the body of the email. The list choices are described below (use one the names below for the name of the list).
slackware-announce <- name of list
The slackware-announce mailing list is for announcements of new versions, major updates and other general information. It is a low traffic, moderated list.
slackware-security <- name of list
The slackware-security mailing list is for announcements relating to security issues. Any exploits or other vulnerabilities pertaining to Slackware will get posted to this list.
You will need to run a *development* snapshot of Slackware (meaning,
slackware-current of around 01-feb-2010 or newer). These packages do
*not* work on Slackware 13.0.
KDE 4.4 has different requirements from KDE 4.3 or 4.2. You will have to upgrade
several non-KDE Slackware packages as well as add some new packages.
Slackware 32-bit:
* All of the dependencies that you need are in the "x86/deps" directory.
* All KDE packages can be found in "x86/kde".
Slackware 64-bit:
* All of the dependencies that you need are in the "x86_64/deps" directory.
* All KDE packages can be found in "x86_64/kde".
Slackware 32-bit as well as 64-bit:
* KDE localizations (language packs) are available in "x86_64/kdei". You only
need one package (for your own language)
Below are the three steps you take to upgrade to KDE 4.4.0. It will bring
you KDE4 even if you did not have it installed before.
I assume your current directory is where you found this README.
From within this directory, you run the following commands as root.
If you never installed one of the Betas or Release Candidates of KDE 4.4 , then
you can safely remove one package: virtuosoconverter is only needed if you
were using nepomuk desktop search before the final release of KDE 4.4.0
# removepkg virtuosoconverter
If you ran Betas or RC's of KDE 4.4 prior to upgrading to 4.4, then you will
notice that your nepomuk database will be converted from virtuoso v5 to v6,
the very first time you login to your 4.4 desktop.
This process will temporarily double the size of your nepomuk database (by
default, this size is 50 MB).
You can also decide to skip this conversion by deleting the database before
starting KDE (and then you can remove the virtuosoconverter package):
$ rm -r ~/.kde/share/apps/nepomuk/repository/*
===============================================================================
Eric Hameleers - alien at slackware dot com - 09-feb-2010
Yesterday i downloaded Slackware and i thought tomorrow i go install it.Made a usb boot image and today after work i first installed Ubuntu along with Xp over Mandriva on my internal hard drive.I did that because i had a nice Ubuntu install on an externel hard drive wich i could not acces anymore after the Mandriva install.Now everything was ok to get start with Slackware.
Then i tried to start the installation with no succes.Changed the bootsettings to usb and i got a disk error.It works when i unplug my external drive but that was the place i wanted Slackwares install.Tried several usb port combinations but with no succes.
Then after reading this sticky i got a new idea :-)
I leave my computer for what it is now.Its running very well with the Ubuntu on my external drive and im not in a hurry to install Slackware.My new goal is to use Slackware as my major distribution and get in on my internal drive installed.
To be honest i am at a point now i can setup Ubuntu and configure it the way i want it to be in just a few hours.On this i think its better to start with the beginning and go on from there.Not skip the boring parts anymore but just go for every part i have to learn.Thats why this sticky is so perfect with all the links.
How do you get to be an certified slacktech is there any official affiliate or training program.
i live in sweden and am going to the computer fair in kista this week are any of you guys gonna be there.
How do you get to be an certified slacktech is there any official affiliate or training program.
i live in sweden and am going to the computer fair in kista this week are any of you guys gonna be there.
I'm not aware of a certification program for 'Slackware'. Loads of documentation that could be used to help oneself in learning GNU/Linux therefore Slackware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
