After all the diatribe the frg guys have been giving me, I took the plunge (again)

After a fresh, working perfect slackware-current install, with 2.6.16, I decided:
"What the heck. I'll try FRG"

Well, to sum it up in two words:

IT SUCKS

The issues:

1. GDM does not work. It sits there with the 'stopwatch'. Nothing. I had to use KDM. (Should have clued me in right there, but I thought "minor")
2. Refuses to accept that my wireless card is working. But that is what I am using right now.
3. Epiphany refuses to load
4. I cannot browse files , nor use any GUI to see my home folders
5. Refuses to connect to my webcam
6. Refuses to connect to my nfs and samba server
7. Galeon does not load
8. Gnomemeeting does not load

So what do you all have to say? I've gunked up my hdd w/a crappy DE that 80% of the stuff I REQUIRE will not work.

And that is just the stuff that I've tried.

i never tried frg...i did try dropline once...with less than desirable results...i've seen both sides here...those who swear BY it...those who swear AT it. for me, i swear by fluxbox. all the libs and stuff i need are already included in slack, or easily found.

I agree. Getting rid of it now.

Next myth to debunk: Dropline. Lets see if it does any better

Well, you should've suspected that something was wrong. You don't think that FRG guys will release something in which nothing works, do you?

The thing is, FRG is made for a clean Slack installation, and all that stuff you mentioned became broken after one of the slack-current upgrades. This has been discussed in several topics (in particular, threads about gdm and Nautilus). So you'll have to wait for a new FRG release. FRG is not that bad (imho not bad at all), really.

You misread.

CLEAN CURRENT INSTALL. I do not 'upgrade'

And I wasn't surprised.

Well, as I said, FRG gone bye-bye now.

Sorry, I really skipped that line. But I'm a FRG user, too. It worked on a clean install. It worked well for quite some time until I made that upgrade which broke the stuff you mentioned. I have no idea why or how your FRG install failed so badly...

why do you test such things on a Slackware-current install ?
the -current branch is moving, changing slowly into Slack-11.

do you expect the fgr dev.'s to foresee all the changes?
don't think you do.

so, why didn't you test it on a stable Slack-10.2 install ?
almost sound like you wanted it to fail.

egag

Gware, FRG, and Dropline are all built for 10.2, not current. Dropline's site specifically says it won't work on current.

Please don't bother installing any of these GNOME desktops on Current if you're attempting to test how well they work. They are intended for the latest stable version of Slackware (10.2).

I can see about 5 things on your list that are attributed to using Slackware Current. In particular, FRG relies on the Slackware 10.2 Mozilla libraries for Epiphany and Galeon... But I'm sure you already knew that.

Please don't bother with Dropline. You'll likely only cob your install up with Current and experience things that don't work. I can guarantee that Epiphany will be one of those things because of the glibc incompatibilities (among other things).

WTF!!! I installed a carburator on my 2006 SUV and it wont work... I'm trashing the SUV!!!

I bought a new PowerPC processor yesterday. I'm gonna replace my current Pentium 3 with it. Sure, it says on the box that it's not compatible with socket 370 motherboards, but what do they know? It's my pc and I will do what I want with it!! I'm sure I can force it in if I try hard enough!


Oh, but if anything goes wrong, i'm going to blame IBM.

'nuff said

Later,
MMYoung