What do you feed your computer...steroids?



Nice!

LocoMojo

just a standard 9800xt 256mb with the working ati drivers (finally). now if i could only get wine to run world of warcraft. might try cedega.

I got wine to run the original Unreal, but it's too fast...lol

In lieu of the conspiracy stories, I have to state that Dropline does not modify rc.inet1. On all of my Dropline build systems, my files match the file that is included on a stock Slackware package.

However... There may be a GNOME network configuration tool that does this. If that is the case, all Slackware GNOME variants (Dropline, GWARE, GSB/Freerock GNOME) would all do the same unless it's patched out. This seems to be very possible, and we will investigate it.

For the curious, the following packages are replaced on a Slackware 10.2 system when Dropline is installed:

http://dropline-gnome.sourceforge.ne...pic.php?t=4739

Please note that tcpip-0.17-i486-35 (which provides rc.inet1) is not one of them.

1. WoW runs just fine with wine
2. I use Dropline and have for a long time now and have no
eth_up in my inet1.
3. Maybe one day Pat will get with the times and actually fix
half these broken programs that are shipped with Slackware
these days. Getting tired of crap not working just to find
that in his scripts that things are removed or disabled be-
cause for some lame brain reason he feels they don't need to
be there.

Thanks zborgerd.

I just verified it and what you say regarding the tcpip package not being from Dropline is true. I also checked the tcpip package installed on my system and I saw that the rc.inet1 file does not contain any instances of "eth_up 0".

Something, somewhere has modified my rc.inet1 file, but I don't know what. I'd like to find out though.

Thanks for the list of packages replaced by Dropline.

LocoMojo

I don't think Pat put it in, it isn't his fault.

LocoMojo

Makes sense, DHCP is trying to get an IP address from a server that isn't there if the cable is not in.

It appears to be a "feature" (I use that term loosely) of gnome-system-tools. We're going to look into patching it out. It appears to be a bit distro-centric (e.g. Anything except for Slackware).

Ahh, glad you found it and glad to hear you're thinking of fixing it.

LocoMojo

wow just keeps crashing with wine. i have an opengl patch that is supposed to fix it but i can't quite figure it out. i'm just going to try with the cedega cvs.

Diffie, one of our developers, has traced it to system-tools-backends:

http://cvs.freedesktop.org/system-to...13&view=markup

Patch submissions from any Perl coders are greatly encouraged (and appreciated).

Wasn't really refering to the eth_up situation, Just the general
Dlg breaks slackware philosophy that some are spreading around when
in fact they really have no clue. Most people will tell you this
from heresay. Most of them haven't even tried it or have tried it
and instead of helping someone if they have a problem it's easier
for them to tell the person if they are running dlg that it's dlg's
fault. Personally I have had less problems with dlg's packs and re-
placements than I get with pats original packs. Probably the whole
slackware world vs pam thing.. One day they will wake up, but
probably not in our lifetime.. Remember, What Pat says is the word
and nothing else is right

Got that right ;}


Cheers,
Tink

The reason your system hangs for 60 seconds during bootup is because of this line:

/sbin/dhcpcd -d -t 60 ${DHCP_OPTIONS} ${1}

as shown in LocoMojo's rc.inet1 posting.

This attempts to connect your ethernet card to a dhcp server and has a 60 second timeout. What you could do is change the 60 to a lower time, or add an & at the end to run this process in the background. Naturally when you have the cable plugged in it starts right up because it doesn't have to wait for the 60second timeout.