Cut me some slack jack. -No pun intended

Josh Beck
"Dan C" <youmustbejoking@invalid.lan> wrote in message
newsan.2005.08.15.11.43.54.565493@invalid.lan...
> On Mon, 15 Aug 2005 04:24:13 +0000, Josh wrote:
>
>> The reason I like slack is because rc.local can do just about anything
>> for
>> you. I would put something like this in:
>
> Just to clarify something, rc.local is not unique to Slackware. Any other
> distro that I've ever seen also has this...
>
> I guess you'll need to find another reason to like Slack.
>
> --
> If you're not on the edge, you're taking up too much space.
> Linux Registered User #327951
>

On Tue, 16 Aug 2005 02:47:30 +0000, Josh wrote:

< silly top-posting corrected >

>>> The reason I like slack is because rc.local can do just about anything
>>> for you. I would put something like this in:

>> Just to clarify something, rc.local is not unique to Slackware. Any other
>> distro that I've ever seen also has this...

> Cut me some slack jack. -No pun intended

I wasn't giving you a hard time. Just making sure you understand that
rc.local is not specific to Slackware. The way you wrote your comment
above makes it sound like you think it is a Slackware-only feature...

> X-Newsreader: Microsoft Outlook Express 6.00.2900.2180

Now all you've got to do is actually start using it (Slackware)...

--
If you're not on the edge, you're taking up too much space.
Linux Registered User #327951

On 2005-08-16, Dan C <youmustbejoking@invalid.lan> wrote:
>> X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>
> Now all you've got to do is actually start using it (Slackware)...

Interesting logic fallacy.

I use FreeBSD, Slackware, OSX and XP. Does using one exclude me from
using the others?

ab

On Tue, 16 Aug 2005 11:29:33 +0000, ab wrote:

>>> X-Newsreader: Microsoft Outlook Express 6.00.2900.2180

>> Now all you've got to do is actually start using it (Slackware)...

> I use FreeBSD, Slackware, OSX and XP. Does using one exclude me from
> using the others?

No, but it's quite clear from the OP's question(s) and knowledge level
that he is using Windoze (only). Do you disagree with that little piece
of detective work?

--
If you're not on the edge, you're taking up too much space.
Linux Registered User #327951

> "jevb" <jevb@bluebottle.com> wrote in message
> news:1123996014.db0b4510eced859f0ed095452e2a98ab@t eranews...
>> Running Slackware 10.1, SOYO KT-880 Dragon2 V2.0 motherboard, using the
>> onboard ethernet device, connected to a Linksys BEFW1154 router, then to a
>> Westell DSL modem. Sometimes, but not always, after a fresh boot up, eth0
>> is not always up. But then, if I run "# /etc/rc.d/rc.inet1 start" eth0
>> comes up okay. Currently, rc.inet1 is called from the rc.M startup script.

In case the IP is pausing or hesitating and you're using DHCP, change all the
time out values from 10 to 20 seconds (-t 20) in the rc.inet1 script file. I
had this problem with Road Runner and it solved the problem.

....Edwin
--
__________________________________________________ _____
"Once you have flown, you will walk the earth with your
eyes turned skyward, for there you have been, there you
long to return."-- da Vinci ... www.shreve.net/~elj

+Alan Hicks+ wrote:

> In alt.os.linux.slackware, jevb dared to utter,
>> Do you mean do I have a static IP, or a dynamic IP? If
>> that's the question, then I *think* it's dynamic. I use DHCP in my router
>> (see above), and the router assigns the IP to my computer.
>
> In this case it's a dynamic IP. If you look in /etc/rc.d/rc.inet1.conf
> you will see something like this:
>
> # Primary network interface card (eth0)
> IPADDR[0]=""
> NETMASK[0]=""
> USE_DHCP[0]=""
> DHCP_HOSTNAME[0]=""
>
> If USE_DHCP[0]="yes" you're using dhcp. If not, then you should see an
> ip address and netmask listed for IPADDR[0] and NETMASK[0].

I checked that file, yes I'm using DHCP.

>
>> I always do a soft shutdown, so
>> that I only have to do a Left_Click on the mouse to start it up.
>
> Ok, I'm having trouble resolving this statement with:
>
>>>> Sometimes, but not always, after a fresh boot up,
>>>> eth0 is not always up.
>
> Do you mean you are using software suspend and the interface doesn't
> come back up after a software resume, or are you talking about a cold
> boot, such as power off to power on.

Sorry for the confusion. What I mean is, I use APM and let Slackware power
down the machine. I don't physically shut off the power to the box. I have
the BIOS set so that all I have to do is click the left mouse button and
the machine will power up. So yes, I guess you could call that a cold boot.
>

notbob wrote:

> On 2005-08-15, +Alan Hicks+ <alan@lizella.netWORK> wrote:
>
>
>> come back up after a software resume, or are you talking about a cold
>> boot, such as power off to power on.
>
> I suspect a cold boot.
>
> I've noticed this happens to me occasionally, also. But, I shut down
> so seldom I usually forget all about it till it happens again. I
> increased the -t setting in rc.inet1 as suggested in another post and
> it seems to have solved the problem.
>
> nb

Thanks for this tip. I'm going to try it. I found four "-t" settings in the
"eth_up()" part of the script (rc.inet1). I changed all four from "10" to
"20". We'll see what happens.

In alt.os.linux.slackware, jevb dared to utter,
> I'm using DHCP.
>
> I use APM and let Slackware power
> down the machine. I don't physically shut off the power to the box. I have
> the BIOS set so that all I have to do is click the left mouse button and
> the machine will power up. So yes, I guess you could call that a cold boot.

Ok, in this case simply incrementing the timeout option in
/etc/rc.d/rc.inet1 should do the trick. Just follow the instructions
others have given and all should be good.

--
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

+Alan Hicks+ wrote:

>
> Ok, in this case simply incrementing the timeout option in
> /etc/rc.d/rc.inet1 should do the trick. Just follow the instructions
> others have given and all should be good.
>

Well, I changed all of the timeouts in rc.inet1 to 20 seconds, and the last
two days every time I started up my machine (three start ups), eth0 has
come up, so maybe that did the trick. I'll keep watching. :-)

jevb wrote:

> +Alan Hicks+ wrote:
>
>>
>> Ok, in this case simply incrementing the timeout option in
>> /etc/rc.d/rc.inet1 should do the trick. Just follow the instructions
>> others have given and all should be good.
>>
>
> Well, I changed all of the timeouts in rc.inet1 to 20 seconds, and the
> last two days every time I started up my machine (three start ups), eth0
> has come up, so maybe that did the trick. I'll keep watching. :-)

Well, so far eth0 has come up every time since I changed the timeouts to 20
seconds. :-)