A question for people who have used both Slackware and Arch.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
figured Slackware sounded like it had a little of both.
Yes - exactly - Slackware does. It's BSD style init system is well documented and all tools are already there for building applications (no "development" versions of packages). The community also adds a lot to the value of the distribution and the amount of documentation. Then there's the SlackBuild methodolgy for building things. I would definitely recommend trying Slackware - you'll learn a lot about Linux.
that's where I got my idea for multidistro.com
1 cd, many distro's
now i usb, many distro's too
that way I don't burn 5 cd's of 100+mb each, just 1 with all on board
here's my current ext3 usb 4gb now
Code:
title Super Grub Disk\nEasily restore the grub bootloader.
root (hd0,0)
kernel /boot/syslinux/memdisk
initrd /boot/sgd/sgd.gz
title Grub bootloader - USB-Menu
root (hd0,0)
configfile /boot/grub/usb/grub-menu.lst
title Grub4DOS USB-Menu
root (hd0,0)
configfile /boot/grub/usb/usb-menu.lst
title PLOP Bootmanager USB
root (hd0,0)
kernel /boot/plpbt
title Sidux-2009-02 USB-Menu
root (hd0,0)
configfile /boot/grub/sidux-menu.lst
title PartedMagic - USB-Menu
root (hd0,0)
configfile /boot/grub/usb/pmagic-menu.lst
title ClamAV Anti-Virus LiveUSB
root (hd0,0)
configfile /boot/grub/usb/clamusb-menu.lst
title TinyCore_2.1 with JWM USB-Menu
root (hd0,0)
configfile /boot/grub/usb/tc-menu.lst
title RescuePuppy49 USB-Menu
root (hd0,0)
configfile /boot/grub/usb/pupusb-menu.lst
title NetbootCD 3.1.1 USB Net-install a Major Distro
root (hd0,0)
kernel /boot/kexec.bzI quiet base norestore nolocal
initrd /boot/nbinit3.gz
so, with that dude I can do almost anything
including net-installing any major distro via netbootcd-3.1.1
made by same guy who made the multicd.sh
( http://netbootcd.tuxfamily.org/ )
I don't get the part about "only 2 CDs to spare" Blank CDs are dirt cheap---less than US$.50 each.
Are you in an area where such things are hard to get?
For some reason I overlooked this post for a second ...
I sort of don't want to use a stack of CDs on one distribution ... I knew it was real customizeable and good for learning and tinkering with. I really felt like having something I could start off simple and build up, and thought Slackware was more of this type of distribution.
Also, I'll have to look for those next time, these are a dollar a piece.
I sort of don't want to use a stack of CDs on one distribution ...
Actually, if you don't mind putting a little manual effort in (and if you're going to like Slackware then that is pretty much a given), you only need to download the 1st cd, then ftp and install the rest of the packages manually from the command line.
The way the Slackware installer works is incredibly flexible, which is one of the things I like about Slackware.
Yes, I also recommend using the tag-file option, thus you will be able to repeat the install proces, if necessary,
and just install the pkg's you want "automagically"
I've only read up a little on Slackware, but I only have 2 CDs to spare ... The only reason I haven't downloaded it. The only package management I've had experience with is using apt-get/synaptics, rpm using Fedora and OpenSUSE/YaST, and portage (which I like a lot.) I really like Gentoo, but I haven't used a distribution like Slackware or Arch yet ... I've been thinking about something do-it-yourself besides Gentoo. I'm surprised, since I registered here, how many people are in the Slackware forum. I've read it's a very good distribution and widely used, but I didn't expect it to be nearly as popular as it is in these forums. Also surprised by how few are in the Arch forum. I under-over-estimated.
The 'Slackware' forum is the unofficial moderated forum. I prefer this forum format over a open type forum. You tend to have people who respond professionally. Don't misunderstand me we all have been spanked at least one time.
The above links and others available from 'Slackware-Links'. More than just SlackwareŽ links!
BTW, Welcome to Slackware.
Last edited by onebuck; 07-16-2009 at 08:54 PM.
Reason: grammar & spelling
I agree to some of the stuff that's already been posted in this thread: Arch and Gentoo are rolling releases, so they tend to break often. Moreover, Gentoo compiles everything from source, which can be a pain. (They are great learning experiences, nonetheless - even more so than Slackware.) Someone said Arch is similar to Debian - maybe you could elaborate. What Debian has in common with Slackware is stability, which is not a priority in Arch. On the other hand, Debian can be used as a stable release or as a rolling release (by modifying /etc/apt/sources.list). Debian is too big of a project to be compared with anything - in my opinion, it is THE Linux Distro: it supports more processor architectures than any other, has a great package manager, great software control, a great team of developers etc. And yet I'm using Slackware right now. But that's just me. Slack is a very specific answer to very specific needs. Debian can cover a much greater area. (It's probably the only non-profit Linux project that has been taken seriously by big companies - they don't have a choice! IMHO, it's way better than SUSE or RedHat, but those have the advantage of offering some commercial support - which is pretty much all they have to offer :P) So anyway, going back to Arch and Slack. You find a neat comparison on their own WikiPage:
Someone said Arch is similar to Debian - maybe you could elaborate. What Debian has in common with Slackware is stability, which is not a priority in Arch. On the other hand, Debian can be used as a stable release or as a rolling release (by modifying /etc/apt/sources.list).
Arch is very similar to the Unstable branch of Debian if you do a net install, leaving out the policies and concerns about being "free".
I wasn't talking about the Stable branch.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.