Yes, it would be nice to have more multimedia libraries. I would define "more libraries" as "all VLC dependencies packaged". It would be good for Slackware to have a media player that can open a DVD saved to HDD without "tricks".

As for GRAB as the default, GRUB worked for me only in a VM. Besides, as far as I know there is no easy way to undo GRUB. So, no default GRUB please.

I've never had problems using xine to watch dvds from harddisk. I use vobcopy to copy them to harddisk then a xine dvd://path/to/directory does the rest.

My only thing on what i do NOT want to see in Slackware is WINE.

Regarding boot loaders IMO lilo today is in a much better state than GRUB.
Hopefully this will change when GRUB2 is released (if ever).
Both bootloaders for linux suck big time really..

I prefer gxine - start opening MRL and replace file: with dvd: and remove the file itself. Or mplayer when all I need is the movie.

The problem is not that it is impossible or hard. The problem is that it is tricky.

BTW, the xine help gives this example:Not a path/to/directory. Trick No.1 - trust nothing.

It is amazing that all that "Open MRL" in gxine has is the File button. I cannot show this to anyone without immediately being told Linux is a usability disaster.

VLC is the only player I know that properly provides the "Open directory" button.

I do not say that VLC should be included in Slackware since when I looked into the (as of testing, broken) Alien Bob's monolithic slackbuild I immediately decided that I would better forget it and stay with gxine and mplayer. But if the Slackware team has resources to add more multimedia then VLC is the way to go.

Unfortunately, I find myself agreeing with you on that point. It always seems to be that last little bit of UI polish that tend to let down linux apps.

Their developers make them available for free, so I don't think anyone really has the right to complain, but it's frustrating non the less.

Anyway, getting way off topic now, so I'll leave it there.

Even though i dont use bash, i suppose many users would like to see bash-completion updated even if its in extra/ .
Its maintained by Debian now and they recently did their first release.
http://bash-completion.alioth.debian.org/

Keep kde3 (or provide downgrade options from kde4) but upgrade mesa and xserver... 8]

KDE3 is gone from current; I seriously doubt that it will be included in the next stable version of Slackware. However, there are other excellent choices such as XFce 4.6.0 if KDE4 is not to your liking.

I don't know if its been said... but I would like to see a bootsplash configured kernel

i think that grub dont work with xfs filesystem.since i use xfs, lilo for me.

Too bad if that is the case, but it looks like you are correct.
I did a fresh install of 12.2 a few days ago and while KDE 3.5.10 is not as pretty as 4.x, it beats the pants off of 4.x in "configurability" and functionality.
Hopefully KDE 4.x will get there soon, but having just left 4.2.2 a few days ago I can see where the KDE team has a long way to go before 4.x and its applications are as functional as 3.5.10.

I don't presume to know exactly how grub works, but I know that xfs doesn't really like to have lilo loaded in it's mbr, if xfs is used on as /. I would imagine though that at least grub would also let you install it on other places too, rather just /. Maybe search for grub+xfs to see if anyone has been successful in getting grub to work with xfs as the / fs.


On another note. You know, this Slackware is so darn stable, its sickening. I would like to see a more buggy release next time.

Hi,
Sorry but the 'MBR' has nothing to do with the filesystem other than to pass to the 'SPL' from the 'IPL. The boot loader is transparent to the filesystem. Boot loaders do pass information to the kernel to effect the initialization of the environment.

The 'MBR' is not part of the filesystem but placed on the device at the start or the sector zero of a device. If you are speaking of the problem with 'XFS' and the install attempt of the 'XFS boot' partition instead of the 'MBR' then that is a different problem. Lilo or Grub should work from the 'IPL' without difficulty as long as the 'MBR' is written properly.

The configuration files for GNU/Linux for the boot loaders are generally stored in the '/etc' directory. These are used to create the boot loader for the 'MBR' or superblock of a partition/device.

It's the users that are unstable. Watch the sh1t fly when the next version of Slackware is released without KDE3.

How ridiculous was the "debate" about the flippy logo...