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'm about to set up my first print-file server with slack10.1 and before i kick off, i made a quick selection already of the packages i think i might need.
Before i will start digging in the smb.conf manuals i would like to ask anyone who has a spare moment play the game "find the bloat" and to have a quick look at my tagfiles and to comment if there are packages that are not needed at all or maybe some missing.
I already installed this and it basically boots without any errors but just to be sure i would appreciate some second opinions from the experts and my fellow newbie's.
The purpose of the server is to provide file and print services to about a dozen windows clients, use the floppy and dvd devices, and make some backups of the shares now and then. It would also be nice to be able to log in for maintenance from a remote location.
cdparanoia and cdrdao are for audio cds, i don't think you'll use that.
sysvinit is just for compability with sysv init scripts, it's no needed.
You could also avoid mdadm and raidtools if you're not using them.
I don't think you'll need autofs too, since you're not going to plug stuff too often
The rest seems fine, because you want to have some tools when you login.
I already have a firewall router, so would an additional firewall on the server be usfull or would it only get in the way without any additional value?
Waitaminit... are you in pain? Are you running out of disk space? If the answer is "no" then this not-so-exceptionally-long list of packages hardly matters, and I would be reluctant to start "removing accessories from a moving vehicle." Many of the inter-relationships among Linux packages are rather subtle. Look at the rather long list of entries that LinuxFromScratch lists (bullet-points 5 and 6...) for what is a bare-minimum Linux system! You might inadvertantly cut off your nose in spite of your face .. been there, done that.
First of all thanks to all for having a peek and give some good advice,
will try to start setting up my new server config from here.
Quote:
sysvinit is just for compability with sysv init scripts, it's no needed.
however, don't know why, but when i leave out this one, i get a a kernel panic when booting, simply adding this one to the tagfiles again simply resolves the problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.