SWarET to Current Crash issue (never been really Answered)
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.
So because I know for sure I'm using Slackware, I can save myself 31mb? Do I just use that 3.4mb tgz with the same instructions as if it were the 34mb one? Thanks for the help!
-Galen
EDIT: Whoa, so I just read that Slackpack install. It sounds like it doesn't need to install source? Do I miss out from not completely customizing my new kernel (like high ram support...I have 1024mb of ram). And I would do that after a fresh install...w/ 2.4.26. Sounds easy...am I wrong though?
Distribution: Slackware current, FreeBSD 4.10, 5.4, 6.2, Debian, RedHat, CentOS, Sun Cobalt OS
Posts: 66
Rep:
High ram support is for systems with 2GB, 4GB and up so i suppose you don't need to compile that feature but another hint i would give you even though it might be too late already is that if you go by the book if you have 1GB and over of RAM it is strongly recommended that you use ECC registered memory.
You would only need to recompile your kernel for high amounts of ram if you had say something above like 8 gigs.
You don't necessarily miss out on features by not compiling from source. You just miss out on the learning experience. As well I just prefer to compile my own kernel because then I choose everything that gets compiled as a module. I just like it more. Plus it's kinda nice.
You should install the kernel source code. If you don't recompile for highmem support, only ~800 megs of memory are recognized. There is some debate as to what is the best method for dealing with 1G of ram. Some leave the highmem out, only recognizing ~800 megs. Others enable highmem, allowing full recognition of the 1G, but with possible extra overhead that may make the extra ram a moot point. The other solution is to apply the Con Kolivas patch, which moves the ram barrier up to allow 1G without adding highmem support.
I thought compiling would be cool and a good experience...untill I realized it needs about 14hrs of your life or more. 4hrs to get set up...then 10 to fix everything you did wrong. I don't know...I did it once, so i had the learning experience of realizing: I'd much rather discover what stuff does as I use it...not try and guess what I MIGHT use and then forget I even have it and learn how to add it later anyway. But hey, that's me! So I'm reinstalling right now on the comp downstairs. I spent about 2.5hrs at the rec center and finished my readings...pretty cool stuff. His Kernel upgrade is just like SHILOs though, so I'm going to try that other one on the site Ninja Cow gave me (just upgrading generic,etc). Also, it seems like unless I'm using ext3 and SCSI or RAID, I really don't need initrd (I'm using ext2 since I have that nifty browser for Windows now and all my stuff is IDE). Thanks so much for all the help guys! 'till next time! (Feel free to IM me if you're bored: Number1Slackah on either Yahoo or AIM).
The Reborn Slackware'r,
-Galen
EDIT: Also, the insyte guy uses slackpkg w/o a problem. Anyone else use this as opposed to the super-duper swaret and slapt-get (sp?)
Gracias Shilo, I'm googlin' that Con patch right now. Awesome site, but did you use Slackware 10 ISO? I didn't have the same luck you did, so I'm going insyte's way (which is basically your way + some new stuff).
-Galen
Well I guess you know your into linux wayyyy too much when you can configure a kernel without even thinking about it!
Plus with my AMD 64 3200+ and 1gig of ram, it compiles in about 5 minutes. I was just configuring a kernel for my usb bootable distro I'm making and my friend couldn't believe I even knew what to check or how fast I was doing it. You really don't even notice after awhile because you've done thousands(or more) configurations and compiles.
Well, if you know your all of your system specs then it's fairly trivial. I built mine so I know every option needed. Not to mention I spent literally a month making sure that the motherboard I got was completely linux compatible. I sure wasn't going to spend $1500 on a new comp to find out usb, sound, or SATA doesn't work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.