Along these lines I would love to see an option to install a bare minimum system. Now for this to really work the installation process needs a way to track all dependencies when installing packages on top of this base.

Not bad, testing it ..... loving it xD


Congratz and thxz for sharing


I guess that any comment can lead to something helpfull, even the one from 'testing' he he




Regards

I agree with gargamel about auto-updating. It's clever from software side to suggest auto-updating when running it only as root, because he's the only one who can do it. What's wrong with letting software to auto-update itself?

Maybe *tranparency*?

It already does. Install the A series and nothing else, and in fact, you can probably even cull out a few of those. That's the bare minimum packages you need to have a working system. Of course, the system isn't going to be useful for many purposes, but it's a "bare minimum" working system.

Anything over and above that is entirely up to the admin. A fileserver will need different packages than a print server which will need different packages than a web server which will need different packages than a router which will need [...]

Well, there goes that idea.

I believe it was already mentioned in the topic, but your best bet for a slimed down system (without breaking anything) is to use tag files. Once you get the install down to where you like it on a working system, generate the tags for it based on the installed packages and then use those to install the next system.

Well, this is more of a cosmetic change. You know when you bootup and a penquin is on the left-hand corner of the screen, symbolizing the processor you have? Maybe instead of the penguin, it can be the head of Bob, or maybe the penguin with Bob's face on his stomach?

http://www.slackware.com/~msimons/sl...dobbslack2.gif

Hey, thanks for the idea! I needed something to do! Will report back with results when done.

Changing the image in the frame-buffer during bootup would require patching the kernel -mostly a no-no in stock Slackware, even though the change would be a zero-risk thing. Still, the few times that Slackware has come with an altered or patched kernel, the changes were of a more serious nature. For instance, when the 2.4 kernel was still being used, the Slackware kernel always had a fundamental change in the code for the umsdos file system which would make sure that the underlying native FAT was read-only.

Maybe this is something we can ask Pat to do sometime. Still would be pretty cool, and it would fit just nicely since it is SLACKware

As some of my hardware is going to become outdated, I've started looking around for a new PC. And I found that almost everything is 64-bit, now. So, sooner or later, an "official" 64-bit Slackware would certainly be nice.

gargamel

I agree, although it looks like the Slamd64 port is pretty darned close.

Reinforcing the issue: a 64bit official release will be needed sooner then later... and also some official support for AMD and not only i386.

//eraosso

AMD declares x86 compatibility.

Replacing boot logo doesn't require patching. Copy one to /usr/src/linux/drivers/video/logo and replace logo_linux_clut224.ppm

Mine (or maybe stolen) is there: http://alien.none.lt/logo_linux_clut224.ppm

Does that require a kernel compile?