Politics??? In Debian??? Don't be ridiculous.

+1 Funny

With the new package format (txz) there's some extra space (about 500MB) on the install discs. I can imagine a lot of people would like to fill some of that with OpenOffice.

I wonder if the Slackware team has been wanting to add any particular software in the past, but has not done so for lack of space.

Isn't the I18n and L10n a problem, while doing this? Are there language packs for Oo.org? It is imho ugly enough, that firefox comes only in the english version, which makes the package unusable for my purposes (Users whose majority doesn't understand english).


cu

I would like to see the latest, most stable kernel available...with a keen eye on VirtualBox interoperability re usb....:D VB is my salvation, eveything else, program wise doesn't really matter...I have the latest VB working now, but had to hack a file...that's what I'm talking about....small thing, but nice.

Maybe the extra space could be used for replacing tetex with texlive? I know this has been discussed before.

"latest, most stable kernel available"
This is a non-sensical sentence, you know...
latest = 2.6.29.3
most stable = 2.6.27.23 (or 2.6.16.62)

"I would like the latest-most-stable-bleeding-edge software(s) available!"

Sorry, just couldn't help myself. :D

It's not when I look at what Debian Lenny is using...can't use it on my Precision....my point is just to support new hardware with the 'most stable' version out at the time, really. But I see your point.

Yes there are language packs for OOo.

About Firefox (same goes for Thunderbird), that can easily be fixed:
* install the language pack you want
* typ about:config in the address bar, find the line general.useragent.locale and change the value to your locale.

Although I am so accustomed to LILO, I now have become rather curious about GRUB since a few people are asking about it. I know that it is in /extra, but just out of curiosity, how feasible, or how much trouble would it be to add a GRUB option along with LILO during the boot setup stage, of the installation of Slackware? I know Debian offers you a choice between GRUB or LILO during the initial setup, so couldn't Slackware do the same? I like LILO, but I think having that choice during the initial setup would be a good idea. Thoughts?

A generic kernel with HIGHMEM64GB enabled please (to save impatient fools like me who read Eric's excellent instructions but still ****-up some trouble). :redface: :D

Please add GRUB with care
 

GRUB never worked for me, maybe because whenever I tried it there were more than one OS and disk. Thus, I guess automated and reliable installation of GRUB is not an easy task.

I experienced GRUB damaging another OS, maybe because the GRUB version in a brand new distro was still too old for Vista.

I failed to find out how to uninstall GRUB. Actually I had some ideas but the road looked too long to take. Thus, I refuse to consider GRUB a safe option.

I am a bit skeptical about GRUB and happy Slackware uses LILO, but I understand that, provided it works, GRUB may be much more convenient, especially for a single boot system, and I find the desire to have it at installation time legitimate.

However, I will not be happy with GRUB as setup option unless other parts of Slackware that currently assume LILO, like slackpkg (actually it is the only one I remember), are modified accordingly.

I find the Slackware installation process straightforward and I never paid much attention to it, but I guess there should be a stage when I am chrooted into my new system and running configuration scripts. If there is one, it may be emphasized with a message like "now you can go to command prompt and install additional packages from /extra, install GRUB, or fine tune your system". If there is no one, I guess it should be added. Since the option not to install LILO already exists, this may be the minimal change that will make GRUB fans happy.

Afterthought. For boot I would like mkinitrd, kernel, and slackpkg packages to be a bit smarter so that when slackpkg upgrades the kernel it could prompt "it looks like you are using generic kernel with initrd created with "mkinitrd ...". Should I recreate initrd and run LILO now?"

Hi,
Hand holding? Not with my Slackware. I think that is one of the reasons loads of people use Slackware; 'KISS'! :D