I'm talking about Unix (invention of Dennis Ritchie et al), you're talking about UNIX® (trademark used by suits for marketing). Sorry, I never meant the latter, otherwise I would have stated that explicitly.

I'm sorry but that still makes zero sense as far as I am concerned. Otherwise I can just call my hamburgers 'big macs' and CentOS can call their distro 'red hat' and nobody will think it odd or wrong.

It is also incorrect from a legal standpoint, since Trademark law doesn't only protect exact naming or logos but also anything similar that could potentially cause people to be confused between a trademarked and non trademarked product. This is why Microsoft was able to force Lindows to change their name to Linspire. Legally the name Lindows (in the software market) was considered close enough to Windows that customers might be confused about the OSes being related to one other.

If you think my logic is wrong and you disagree with Trademark law, perhaps you should consider this, the FreeBSD foundation doesn't call FreeBSD UNIX or Unix either and hence you won't find them making any such statements anywhere on freebsdfoundation.org or freebsd.org. Rather they use factual descriptions like 'Based on BSD UNIX' and 'Unix-like' but they never say it is actual UNIX or Unix (the same is also true for OpenBSD, NetBSD and DragonFly BSD for that matter). So no, FreeBSD is not an actual UNIX/Unix OS, even in the eyes of those that help manage its development.

3 members found this post helpful.

What about things to remove? I don't think I have ever installed Tex in 18 years, but the default install has Tex included unless you uncheck it.

Others need it.

See post #224 in the same thread.

How about bits of programs we would like to see included? Openvpn is included by default, but there doesn't seem to be a /etc/rc.d/rc.openvpn. I have used for a few years now the script found at the link below:

http://openvpn.net/archive/openvpn-u.../msg00030.html

It basically starts openvpn on all files in /etc/openvpn/config ending in ".conf" (I modified mine to start on the files ending in .ovpn - as the OpenVPN tradition of naming config files seems to be - not that it matters much).

Something like the script above would be really handy if it was included by default in Slackware. Maybe with a corresponding entry in /etc/rc.d/rc.inet2 or whichever the most appropriate place might be - ready to do just a chmod to activate it.

2 members found this post helpful.

TeX is one of the few things on the linux desktop that is not a stupid imitation of Windows stupid software. That's why you can get a real professional result of it. And you want to remove it!? (I am doing a big effort to not insult you).

4 members found this post helpful.

Using Lyx on top of TeX for technical writing is far superior to any office suite application.
I also use LaTeX for producing PDF documents.

The TeX install in Slackware comprises 4-5% of the total install disk space and I consider it a mandatory part of Slackware.

Me too, but I'd like to find a way to update the components that make up teTeX to make things a little more modern. TeXlive really isn't an option due to the size. If we had that, it'd be at least 50% of the total install disk space. :/

How big are the packages compressed? If they compress well, could they perhaps go in /extra? Not the same I know but still, something.

There is no need not to put the whole of Texlive in.
Just follow what other distros like Debian do.

I use latex to edit books. And groff for letters and small documents.

I miss just one thing in groff, it's not as clever as latex is resolving widows and orphans. Utf-8 support is another limitation but I can convert my docs to iso-latin, so it's not a big problem. Groff is more unix like but it's true that for big documents (a novel) latex save a lot of work.

Now the texlive issue

Debian install 432M just of texlive documentation.

I've compiled and packaged texlive for Slackware from slackbuilds.org (thanks Robby Workman). The resultant tgz file size is 1.7G.

My personal opinion is unless texlive developers find a solution (a linux liveCD with a whole desktop fits in one 700M CD!) Slackware should stay with the old version.

1 members found this post helpful.

How about the xfce4-kbdleds-plugin?

BTW, many thanks to whomever (Mr. Workman?) "fixed" the xfce4-weather-plugin.

Sorry -- I wiped this post since I mistakenly quoted/posted on the wrong thread.

I'd only like to see the KDE versions more thoroughly tested before being shipped with Slackware's next releases.
For me, the default KDE 4.5.x in 13.37 had issues with opening large files in external USB hard disks, which I resolved using AlienBob's KDE 4.6.5. And in 14.0 a lot of guys including I had that silly issue of two tiny launchers re-appearing and strangely a single virtual desktop given by default in KDE 4.8.5.
Not to say it's Slackware's fault. Other that that, perfect OS to learn, beat and drag by any means.

Regards.

Since the latest version of the radeon drivers now also support video acceleration via VDPAU (now only Intel doesn't support it) I would like to see libvdpau in the Slackware tree, so that MPlayer and other video-players can support it by default.