Post something that you do not like about slackware
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 would have said I don't like having to configure my wireless through inet1.conf (Wicd doesn't work well with my laptop), but now that NetworkManager is on SlackBuilds.org I don't really have any complaints.
Please be a little more specific: you speak about a ton of problems but do not give a single example, so one can see your sentence as only spreading FUD. BTW, how heavy is a ton of problems
...
You know very well too why -generic is not the default at time of install. Among other reasons most file systems are not built in it so you would go for a kernel panic in most cases.
I'm not spreading FUD, Pat V is, because that's what he said in the changes and hints:
Quote:
The huge kernels are primarily intended as "installer" and "emergency"
kernels in case you forget to make an initrd. For most systems, you
should use the generic SMP kernel if it will run, even if your system is
not SMP-capable.
Distribution: x86_64 Slack 13.37 current : +others
Posts: 459
Rep:
Quote:
It's one of the first tasks I do when setting up my account. I've been following other threads with cdrom issues as the symptoms appear similar to mine. In the meantime, I'm trying to figure out if I'm starting to get a failing motherboard or hard drive. However, the other linux distribution installed totally without a hitch (it almost broke my heart just how painless it was compared to what I've done in slack).
I discovered a couple of weeks ago that the Hitachi 250GB drive I bought from Maplins for £60 was the source of many unexplainable problems,the drive shows no errors with any of the tests I have run on it but I have disconnected it for the second time and alls well...even my XP was freezing for moments at a time,I am pretty sure that it was this drive that screwed up my partition table at the time I was writing to the other drive so much so that I could,nt recover any of the logical ones,the primary partitions on both drives survived...
Lucky for me that I don,t keep anything of any value on my box...to me its like a Rubix cube,I could do the cube in around thirty seconds... it pulls apart and you just reassemble it correctly... in fairness to Slackware it does rather well considering the constant change in developing programs utilities,Pat dos,nt write these changes but he and the others have to continually accommodate them,considering the constant flux of change Slackware is doing rather well... LOL
You know very well too why -generic is not the default at time of install. Among other reasons most file systems are not built in it so you would go for a kernel panic in most cases.
Yes, but why can't -generic have *one* default filesystem built into it? If you don't want to mess with an initrd, you could just use the default filesystem and -generic would work fine. Everyone's probably got their own preference on what the "Slackware default" filesystem should be, but something bland like ext3 would suffice. If that's not your personal preference, then you'll have to use an initrd.
Yes, but why can't -generic have *one* default filesystem built into it? If you don't want to mess with an initrd, you could just use the default filesystem and -generic would work fine. Everyone's probably got their own preference on what the "Slackware default" filesystem should be, but something bland like ext3 would suffice. If that's not your personal preference, then you'll have to use an initrd.
It seems more "slack" to just build your own kernel to fit your needs if you don't want an initrd. It's not a big deal to build in a file system. I like the fact that slackware keeps things general and let's me make my own decisions. JMO of course.
Sure, there's always that option. We're encouraged not to run custom kernels anymore though - at least if we want to report bugs. And it's even more effort than setting up the initrd. Seems like just adding one filesystem to -generic would add a major convenience, and it would also remove a stumbling point for new users. The only disadvantage I can see is a non-removable driver for people not using that fs. I don't see that causing a noticeable or even measurable performance hit though. It's not like the -generic kernel is all that small anymore anyway. It's now over 2.5MB - the days of it fitting on a floppy are long past. I'd say that if anyone is really bothered by a single default filesystem driver, they can be the ones to recompile to get rid of it. JMO, also.
I understand why -generic is built that way, and mkinitrd isn't that much of a hassle. It's just one more step to set up a new installation that I think could be avoided with a very minor kernel config tweak.
Yes, but why can't -generic have *one* default filesystem built into it?
I have another idea.
Slackware's installer knows what the filesystem of the boot drive is (it uses that information to set up that fstab). Therefore, it can build an initrd with just that filesystem and then set you up with the generic kernel.
When you consider that the initrd might need to support things other than filesystems, though, it gets more complicated.
Slackware's installer knows what the filesystem of the boot drive is (it uses that information to set up that fstab). Therefore, it can build an initrd with just that filesystem and then set you up with the generic kernel.
Doesn't that pose a problem for people who need special RAID drives for instance?
Yes, but why can't -generic have *one* default filesystem built into it? If you don't want to mess with an initrd, you could just use the default filesystem and -generic would work fine. Everyone's probably got their own preference on what the "Slackware default" filesystem should be, but something bland like ext3 would suffice. If that's not your personal preference, then you'll have to use an initrd.
So you would have a -generic-xfs, a -generic-ext2, a -generic-reiserfs, etc., right?
But I often use an ext2 /boot and the rest as xfs - it was bad enough when I had to load support for xfs from a floppy.
After all it's not forbidden to chroot /new_slackware_root, make an initrd, edit lilo.conf to add a -generic entry and run lilo before rebooting after having completed Slackware's installation.
@H_TeXMeX_H:
- still waiting for a few examples of the _ton_of_problems_ you mentioned about using -huge
- I was prepared to hear that not everybody likes me, don't worry and be happy
Last edited by Didier Spaier; 06-15-2010 at 04:13 AM.
After all it's not forbidden to chroot /new_slackware_root, make an initrd, edit lilo.conf to add a -generic entry and run lilo before rebooting after having completed Slackware's installation.
@H_TeXMeX_H:
- still waiting for a few examples of the _ton_of_problems_ you mentioned about using -huge
- I was prepared to hear that not everybody likes me, don't worry and be happy
Alright, at your request I have removed "tons of" from that post. I hope you're happy now. If you're not, I don't care, because I am right, that's why it is recommended that you use the generic kernel. If you're too lazy to search, and want me to do it for you, that's your problem.
Last edited by H_TeXMeX_H; 06-15-2010 at 04:10 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.