Sounds great

VectorLinux also has their own version which is similar. I do like their use of the "echoc" command which takes a second arg for the color of the text to display. That function could use the switch to determine if colors are used and if so, which color configuration.

Yes, it is mostly there. Manually entering boot parameters is too complicated and it is also necessary to manually install the key to have a secure shell from the very start, so it is either modifying initrd, or Slax, or whatever. For me and for now it is sufficient to know that this is not hard to do.

The idea was to allow for completely unattended remotely controlled installation out of the box, that is, without burning new installation media, just adding some additional one.

When originally posting, I thought no distro does that. Now, after trying to formulate the idea better, I see that Slax does exactly that. Email somebody the changes file and the link to download the standard Slax - and you are all set to create a remotely managed server, Slackware or not.

Thus, what I wanted was actually the Slax "changes file" feature implemented with the Slackware installer. This would help everyone who wants to modify initrd in any way (just not having to burn any media is good) but with Slax already existing I agree this is not worth the effort.

BTW, thanks for comments!

I don't know if theres a reason for grub legacy to still be in /extra when grub2 is available, also i'd love to see slackware move from lilo to grub. I use grub because of the command line option that lilo doesnt offer and because it can boot kernels from any partition not just the root partition.

anyway if you feel like checking it out my grub2 slackbuild is at http://landofconfusion.comze.com/grub-1.96-i486-1.tgz and the source is at http://landofconfusion.comze.com/grub2.tar.gz

i couldnt get grubconfig in the package because it doesnt seem to like the fact that there's no /usr/sbin/grub. And I'm not sure if its just my computer or if the package could use recompiling somehow but grub-install took 10-15 min and the update-grub took 30 min.

The new linux logo http://torvalds-family.blogspot.com/.../new-logo.html when 2.6.29 hits current

1 members found this post helpful.

Yeekkk!!! what an ugly little thing...
Linus always seems to have a great time each year in down underland. What next?

Here's the real thing, without the penguin beak:

http://en.wikipedia.org/wiki/Tasmanian_Devil

Cute little critter, ain't it?

Master Build Script
That topic got left too soon. That is a great idea.

You definitely need to document the dependencies though. Somebody is doing something to that nature now.
There has to be a build plan written down somewhere. Perhaps they even have a script.
Maybe the inner circle has a copy of this.

I know I have notes written down for building glibc, gcc, and Xorg.

Possible reasons for a master build script:
1. Automate a recompile for your architecture (Xeon / i686 / 64 bit)
2. Package up your build of the system for your home network.

List could grow.


Also,

Where do you file bug reports for Slackware? Info@Slackware.com ?

That's a bit like telling somebody to leave a message on your answering machine.

So another wish for Slackware 13 is to have a bug report page, similar to Debian's / Fedora for example.

This would allow for the creation of a proper procedure.

Task could be assigned, you'd have more visibility of the problem.

* Bug Kde KSnapshot Segfault
* Status --//-- Assigned to AlienBob
* State --//-- InProc
--------------
Fowarded to KDE Dev for review


L 8 R

If you have a genuine reproducible bug and are running the stock kernel with all stock slackware packages then feel free to email Pat directly.

You are in the very best place to submit bugs right here on LQ.

The slackware team all keep a very close eye on the forums here and deal with issues as they arise.

Although each person does tend to concentrate on certain areas, we do not assign tasks to individuals but would rather attack each problem as a team.

We think the current procedure is proper thanks

The build script is a very bad idea, in maintainance terms.
An example is the latest GCC 4.3 update in current.
I bet many packages in Slackware dont build with that version of GCC.
Providing patches just for that is a waste of time.
Slackware is a 100% binary distribution.

Noone is preventing you from doing all that yourself.
Documenting dependencies doesnt even require scripting skills.
I say go for it. If you lead the way maybe others who feel the same as you will follow.

I used to feel the same about this too until some point.
I had even asked Alien Bob in the IRC once about it. This involves a more open development. Not gonna happen any time soon.
FWIW with the size of Slackware i no longer think there is a need for a bug tracker. As others have pointed out, LQ and info@slackware.com is adecuate.
Your example with KDE sucks, because KDE has a bug tracker. Whats the use in letting Alien Bob know about it? Its a waste of his time..
Hes just a Slackware packager, not a KDE developer.

I want to see Slackware released on floppies again... I miss making the bare.i boot and color.gz root floppies.

lol, Don't forget to download them over a v32 modem too for that authentic taste.

That's why I cap my dsl at 52k

This can be avoided if you use technique I mentioned before, but:

It won't correctly handle recompile. Only clean build from scratch.

Ha-ha, good one! I've been modem-free for quite a few years. I still remember my crappy old 28.8 modem.......****shudder****

only 28.8?
try a 1200bit modem.