That depends on if I can find out where they live.

Absolutely classic:-) Funny stuff, Robby!
If you're a BSD user then Slackware will feel right at home for you. I think the Slackware ncurses installer should be easy enough to see for a visually impaired person (unless you are very visually impaired). For me, ncurses is very similar to sysinstall in FreeBSD.
Each to his own though.

Someone just drove by my house and threw some cookies at it.

cheers,

Hi,

So your house's browser can load their location.

its a drive by cookie throwing!

I guess this is exactly what should not be done.

1. It is not a matter of a graphical installer, but of a larger command line letters. As far as I remember, the installer runs in 640x480, so there is nothing to do.

2. I am not getting the "out of the box support" argument. A distro cannot support what the kernel does not support. It MAY be nice to have a set of boot options like "for Lenovo 300 N5900", "for Toshiba without probing for SCSI RAID" and so on, but this should be the lowest priority task, that is, something that is always possible but never done. In other words, a working base system is better than a collection of proprietary blobs.

I guess it may help do add a doc describing how to install the Slackware installer on a HD with a Live CD. Something like "if you have a problem, boot a live CD, install the Slackware installer onto what will later be swap, adjust it and reboot to it."

3. Why? VirtualBox comes as RUN file and installs itself perfectly. How is VB different from other apps that install themselves in the same way?

I guess yet another package generation tool may help with that, something like "package what is in opt and the links that lead there from standard directories excluding everything that has been already packaged from opt". I doubt Slackware developers should do that, just an idea.

4. A dual library Slackware is twice as much work without clear benefits. I guess it may be interesting to have 64-bit only official Slackware, but I am not sure it should be the next release.

5. Same as 2.

Personally, I was surprised to see Qt-4 missing from the official 12.2, but I guess it is already too late to vote for it since KDE 4 is very likely to be in the next release.

I would love that, preferably before this weekend:-)

I'd like to have the option of colorized boot scripts. Something similar to Woodsman's implementation is what I am talking about (where you have a switch that can turn it on or off).

Perhaps all of the echo statements could just use a wrapper instead and that function would handle the colors based upon the statement type defined.


Also, I wonder if sbopkg could ever be included in /extra. I'm sure a lot of Slackware users who don't know about it would get good use out of it.

Well, as several already point out, you can really go two ways:

1. Install the binary from the VirtualBox site [1]
2. Install the VirtualBox OSE with help from the SlackBuilds.org scripts [2]

[1] Should work reasonably well and painless
[2] I know that these work well. And especially since the VirtualBox 2.1.x series it's a dream to work with (networking is so much easier these days, no longer do you need to set up bridges etc).

Granted [2] is not a pre-compiled package, but it really isn't that much work to do. And if you want, you can even use sbopkg to do it.

-M

Thanks a lot for the reply and the suggestions. I am tempted to start with the first option and see how it goes.
Incidentally, Twirssi really looks cool! Tweet on!

Yesterday I hit a minor problem that would best be solved by the distribution itself. The command "git add -p", which allows you to pick specific file differences to be included in the next commit, requires the Error CPAN module. There could be an official package for it because it's a bit of a pain in the ass to install it and maintain it if you are not used to Perl and CPAN (I'm not).

+1 for inclusion of MPlayer, although I realise there are probably license/other issues with this.

Mostly I don't want to see it change much

I would like to see a port system, which grab slackbuilds from slackbuilds.org, sources from links and compile a package with fakeroot.

I would like to see an official 64bit Slackware... although i really don't want PV to work twice ^^. I used Slamd64, but i get strange issues, like Slamd64 changed my bios clock (yes, you read well).

Many other ideas here :
http://www.linuxquestions.org/questi...lackware+super

rg3, src2pkg should package that perl module for you without much trouble -just download the sources and run 'src2pkg tarball-name' and you shgould get a package.

Short of not using fakeroot (And that is because SlackBuilds.org doesn't use fakeroot), sbopkg does exactly that.