Problems:
* I installed 12.1 a few times. Just to test.
Use a single partition and the symbolic link to gcc has no target.
It links to the previous version of GCC which is not installed.
If I used more than one partition, a '/' and a '/home'
the link is connected.

Fix: delete the symbolic link and add a new one.
ln -s /usr/bin/gcc-4.2 /usr/bin/gcc

* KWifimanager connects to a wireless access point but will not fetch me an IP address.

Fix: Slackware includes the source, find the KDE Network package.
You will have to modify the Slackbuild or use the configure commands provided within the Slackbuild.

Inside the networkscan.cpp, I'm taking liberties with the filenames, locate a section where you'll find the statement "ifconfig %1 up".

Copy the three lines of code and create a new statement with "dhclient %1". This should appear obvious.

I sent this fix to the developer over kwifimanager. May or may not see it in 4.0.

Just build whats in the wifi directory. The remote desktop applications failed to build.

* Seems as though there is limited functionality for Slackware in KDE.
I recall reading where there are KDE developers using Slackware.
Hard to believe some of this stuff still don't work.

The network configuration screens can bring down the interfaces but can't restart them using dhcp. I suspect it will require rebuilding them with calls to dhclient.

KDE Network should be in placed in extras until it works.


* Originally I had a crack at the distro for not including the language packs,
it was unfounded as I went back and checked and they are there.

* Suspends somewhat but halfway resumes, No Hibernate!

Suspend works but returns with a black screen. Hibernate doesn't work at all.

There are two scripts missing. /usr/sbin/suspend and /usr/sbin/hibernate
Fix:
You have to manually change brightness when you return from suspend.
drop to a virtual console
echo "7" > `find /sys -name 'brightness'`

* udev / acpi

Fix:
canabalize other distributions for what you need.
I got my Wacom rules from Debian

*edit*
I thought about the default xorg.conf file.
It's sufficient.

* Compiz
No documentation and no references.
Fix:


In closing,

Originally I had some negative statements here but I decided to remove them.


L8r


me

Well, Slackware isn't for everybody. Hope you enjoy your Ubuntu.

/usr/bin/gcc points to /usr/bin/gcc-4.2.3

So that's one thing you're wrong about. I'll leave others to sort out the rest. Happy Ubuntuing!

Dang......you beat me to it:-) Slackware is for people who enjoy customizing their system without a lot of hand holding.
Ubuntu is a good choice for the OP. Enjoy:-)

Wow. You're special.

The network stuff in KDE is probably included just because it is part of KDE. You *could* use it, but `netconfig` and editing /etc/rc.d/rc.inet1.conf is the accepted way to do it in Slackware. If it doesn't work, it's because KDE is faulty, not Slackware. Technically Pat could hack it to get it to work, but that goes against his philosophy. If you don't want to use `netconfig` or edit /etc/rc.d/rc.inet1.conf, then go ahead and jump through all of the hoops required to get KWiFiManager working. You could always just install wicd and avoid the whole mess.
...what? 12.1 is extremely multingual, at least with KDE. All of the language packs you would need are included on the CD/DVD in the kdei/ directory, and there is an option to install this during the installation procedure. 12.1 also includes SCIM and includes information on getting it to work in CHANGES_AND_HINTS.TXT. In addition, even without any kdei stuff installed, I have no problem seeing international fonts in the Firefox included with Slackware. 'Arrogance' belongs to you, not Pat -- this stuff is already taken care of.
...what? If you want to suspend, use the following command:
I think in runlevel 4 there is an option in KDE at least -- but I'm not sure. You could create an alias for the command if you really want to issue 'suspend' to get it to work. As for resuming, works fine over here with the nVidia proprietary drivers. It is likely that your video card is having issues if resuming presents you with a black screen. What video card do you have? What driver are you using? Is DRI enabled? Hibernation works perfectly fine -- you just don't know what you're doing. You need to add an append line in /etc/lilo.conf and subsequently run /sbin/lilo to tell the kernel what partition it is supposed to resume from (your swap partition). In my lilo.conf I have the following line in my kernel stanza:
where /dev/sda5 is my swap partition. Hibernation works perfectly with no hiccups.
Nope, not over here. Again, probably a video card driver issue. If it's the ATI driver, then blame them -- it's not a good driver. If it's something else, then please tell us. If you just want to complain I suspect you will not try to fix the problem and will just say "it should have worked in the first place". And to that, I say use another distro.
No problems with udev over here. Slackware 12.1 includes udev rules that are more similar to those of other distros. See CHANGES_AND_HINTS.TXT.
`xorgconfig`
That's compiz's fault. Documentation of another application has nothing to do with Pat whatsoever. Compiz is a terrible piece of unstable software IMO, with some of the worst, non-existant documentation. If you want things to 'just work', install CCSM and the fusion icon using the SlackBuilds from slackbuilds.org, here. I don't think Compiz is a priority for Pat since it's so incredibly unstable and doesn't work well with KDE's pager. I tried compiz but quickly got frustrated and discontinued its use. It's really not ready, and is included more for the novelty. These forums have instructions on how to get compiz working without installing CCSM etc. -- but there is not much customizability in that. That's a compiz thing IMO.
You're right. Slackware is only one of the most stable and secure distros out there, not suffering from such bugs as the openssl fiasco and never crashing, at least for me. But it's definitely inferior to other distros that do crash or are insecure, right?

Get over yourself. You like to complain. If you feel this way about Slackware, it's obviously not for you. Go pick another distro. Slackware has a small demographic and this demographic would likely be upset if anything changed. Slackware is for stability, usability and customizability -- not for automation. Some people just don't seem to get that.

You're looking for Ubuntu, so go with it and be happy :-)

Wow indeed . I think I learned more tips from that single post than from just about every where else.

The O.P.'s post is what's IMO wrong with quite a few Linux users. They assume the creators of the Distro created the software that's included. This is just wrong. If package A doesn't work, complain to the people that wrote package A, not Pat. So many people install Ubuntu, and think Ubuntu actually did some kind of magic to the software. Ubuntu doesn't code the software, they don't fix the software, they barely do anything at all besides sync with Debian, change the branding, and add some hacks that cause issues with 30-60% of the hardware. Try filing an upstream bug, and state you use Ubuntu. The first thing the dev's will want you to do is compile a vanilla source without all the Debian patches and Ubuntu breakage. Try getting someone from Mozilla to notice anything from a discrepancy from Iceweasel, or Icedove. Got a problem burning discs with K3b? Too bad. Try using cdrtools (cdrecord, mkisofs..) not wodim, and genisoimage. Yeah those aren't available are they

Now file an Upstream bug against a Slackware package. Those devs will actually take notice. Because they know a Slackware package isn't some hacked and slashed piece of code of what used to be dev's original intentions.

You can't even file an upstream kernel bug against Ubuntu's kernel, because of the plethora of patches they impose on it. Who knows if it's a kernel bug or an Ubuntu bug? Funny how when something works - OMG Ubuntu did it - but when it doesn't work - must be upstream and not one of 15 different Debian/Ubuntu only patches that where applied

It was pointed to 4.2.1 and a dead link none the least.

I was able to recreate this twice and I did send it into info @ slackware.com but I probably need to find their bugzilla type aparatus.

If your 12.1 has gcc-4.2.1, then it's different from everybody elses, unless you installed 4.2.1 yourself.

Exactly how did you "recreate" this? It is impossible to have a screwed up gcc symlink if you use installpkg or upgradepkg to install Slackware's gcc package.

The Slackware 12.1 gcc package contains a doinst.sh file with the following lines:
When you use installpkg or upgradepkg to install gcc, this file is executed and the symlink is created.

strange happenings.

OK, you've just made me waste half an hour of my time to prove a point I already knew was true. I installed Slackware 12.1 in a VM from scratch, creating ONLY the root partition (/) without swap or a /home partition. I admittedly didn't install the x/ series (or the xap/, kde/ or kdei/ series), but that shouldn't make a difference here. The /usr/bin/gcc symlink is correct -- I didn't do anything at all to change it. Here is the output of `ls -l /usr/bin/gcc*`:
Either your install media (CDs/DVD) are corrupt (did you check the md5sum of the disks?) or you did not format the old partition and there are still some old files hanging around. Beyond that, you may wish to completely delete your partition table and write the empty partition table, followed by creating a new partition table with the desired partitions if the problem continues. That should completely destroy any remaining files -- though a format, checking for bad blocks, should not let this happen anyway.

gcc-4.2.3 is included with Slackware 12.1, and 4.1.2 is included with Slackware 12.0. There has never been a gcc-4.2.1, except possibly in -current at one point in time.

As far as I can tell, the only valid argument you have involves KWiFiManager, which I don't use and can't help you with. KWiFiManager isn't encouraged in Slackware anyway, but you do have a point that it should be functional (though I don't know if it actually is broken or not since I don't have wireless on my desktop). The suspend/resume thing should, hopefully, be able to be fixed depending on your video card. Other than that, I can't find much truth to your statements.

What means of sorcery is this? I'm a Half-Elven Ranger not a Wizard.

Basically I just used a root partition with Reiserfs and everything selected... And I believe you are correct it was a 12.0 compiler. But I did not upgrade the distribution. It was a clean install.

Who knows.. I'll pop out the cd and try it again myself tomorrow. I originally pulled it off the torrent on Slackware's homepage.

.....
...
....


sleep

I ran some more tests and I am unable to reproduce the symbolic link problem I encountered.

Maybe it was a smear on the disc.

Solar flares anybody?


L8r