SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I just installed and configured alienbob's latest current iso on an old r51 thinkpad and everything works ootb using the huge.s kernel, the second choice as my centrino cpu doesn't support PAE, that's ok, I only have 512MB RAM anyway. Runs really well with xfce, but I think I'll compile lxde. I also installed wicd (extras) for a painless wireless experience.
Thanks to Pat, alienbob and the crew.
Please explain a little better? You used Alien_Bob's;
The ISO below are <2GB + 'ISO images are automatically re-generated within a day if there is an update to the ChangeLog.txt' + These ISOs are created using Alien_Bob's script 'mirror-slackware-current.sh' + Source is not provided on the ISO images below Slackware-current DVD ISO image <- 'x86' for 32bit Slackware64-current DVD ISO image <- 'x86_64' for 64bit
The above links and others can be found at 'Slackware-Links'. More than just SlackwareŽ links!
That's the link I used. Sorry for not being clear. The install was pristine, as in I have never had slackware on the r51 Thinkpad.
I have since found a bug with the xfce terminal. I mounted the DVD to install KDE to see how it would go on a slowish machine. While in xfce, I opened "terminal", changed directory to " /media/Slackware-current DVD/slackware/kde" and invoked a small loop to install all *.txz packages in the directory. As a matter of course I did "su root".
for i in *.txz;do installpkg $i;done
This returned "syntax error near unexpected token `do'"
I switched to xterm and the command worked as expected.
I did try "pkgtool" but ran into a snag where I think the space in the directory path has baulked things. (Erm, yes I burnt the DVD in Windows, if it makes a difference).
The dialog showed up as expected but when I tried to select "Install packages from current directory" pkgtool exited with: /sbin/pkgtool: line 404: [: /media/Slackware-current: binary operator expected
/sbin/pkgtool: line 490: [: /media/Slackware-current: binary operator expected
... You can see the path is cut short. This was in "Terminal" (xfce) and "xterm".
Can you point me to the appropriate place to report this? I took a look but I have limited time ATM.
BTW, KDE did work ok but was sluggish to start and a sometimes lagged. XFCE is much better suited to this machine, which I did suspect before hand.
I look away for a while and 'www.slackware.com Website Down?' causing panic, misinformation along with some well intentioned blog entries set a flame ablaze. 'Caitlyn Martin' does another sensationalist journalistic one sided hatchet job from misinformation about Slackware from Eric's blog (not Alien_Bob but V. T. Eric Layton or vtel57 at LQ) on DW. Even with trusted members and maintainer(Alien_Bob) stating that the information presented was not clear or correct, Ms. 'Caitlyn Martin' did not make retractions or corrections fully.
Sadly 'Caitlyn Martin' did no retraction nor correction for the damage she has done. She has attempted some damage control here but none at DW, even when she has referenced the LQ Thread: 'www.slackware.com Website Down?' with comments on DW. She is very defensive at this point in time and still do her wiggling routine. Personally when I see here name on any written document, I will automatically become a little skeptic therefore guarded. One other point; Slackware is still the oldest current stable Gnu/Linux. I really think that some people tend to resent that fact.
For those that are worried about the status of Slackware then be sure to check the ChangeLog.txt. You can find the ChageLog.txt on your favorite mirror. Over the years slackware.com has been down only to recover. You can still access store.slackware.com for donations or Slackware Gear purchases.
Please remember that the problems are in the way facts or information have been presented/interpreted by members and 'Caitlyn Martin'. Caitlyn did not follow good journalistic practices therefore stepped into a big pile and her feet are still dirty. No proper cleanup!
I've been away for awhile, playing around with Arch, but I decided that it's time to install Slackware on my laptop. I've set up Slackware enough to know what I need to do but I had a question about it anyway. One of the first things I do is switch to a generic kernel as when I was learning about Slackware I read about doing that. However, I almost never see anyone mention that, even when talking to new people. Do you all just huge the huge kernel? I figured the generic kernel would be a bit snappier as it has less modules to load but I've never really tested it.
One of the first things I do is switch to a generic kernel as when I was learning about Slackware I read about doing that. However, I almost never see anyone mention that, even when talking to new people. Do you all just huge the huge kernel? I figured the generic kernel would be a bit snappier as it has less modules to load but I've never really tested it.
I think most people do that (Except those who build there own kernels. ). The 13.37 release announcement even tells you about the generic kernel and what is needed to use it:
There are two kinds of kernels in Slackware. First there are the huge kernels, which contain support for just about every driver in the Linux kernel. These are primarily intended to be used for installation, but there's no real reason that you couldn't continue to run them after you have installed. The other type of kernel is the generic kernel, in which nearly every driver is built as a module. To use a generic kernel you'll need to build an initrd to load your filesystem module and possibly your drive controller or other drivers needed at boot time, configure LILO to load the initrd at boot, and reinstall LILO. See the docs in /boot after installing for more information.
People probably don't talk too much about it because README.initrd is pretty thorough.
For members who are subscribed to the this thread! Now is the time to post your questions for a Interview with Patrick Volkerding thread. Time to clear up some open questions about Slackware since there have been loads of FUD and speculation lately.