NFS vs eth0

I set up a diskless laptop (actually, it has a hard disk, but I don't want
to touch it) so it boots over the network, with / served via NFS over 100BT.
I would like network access too, so I can do normal network stuff, but the
distribution (Redhat 8) kills eth0 at shutdown, which kills the OS by taking
away / . How do I modify things so / stays up regardless? Thanks.

--
-eben (E-Mail Removed)m home.tampabay.rr.com/hactar
Are you confident that you appear to be professional in your electronic
communication? Consider this: A: No
Q: Can I top post? from (E-Mail Removed)

Hactar <(E-Mail Removed)> wrote:
> I set up a diskless laptop (actually, it has a hard disk, but I don't
> want to touch it) so it boots over the network, with / served via NFS
> over 100BT. I would like network access too, so I can do normal
> network stuff, but the distribution (Redhat 8) kills eth0 at shutdown,
> which kills the OS by taking away / . How do I modify things so /
> stays up regardless? Thanks.

Modify your runlevel configuration so that the
/etc/rc.d/init.d/networking is run last at shutdown. This is probably
achieved with the chkconfig tool, but I'm not all that familiar with
RedHat.

If its not the "networking" script, look for the file that runs ifdown
eth0 (grep -lr ifdown /etc/rc.d/init.d/)

Naturally, some experimentation may be neccessary.

PS. If you're looking for a X-Terminal solution, have a look at LTSP
(www.ltsp.org).

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!

In article <(E-Mail Removed)>,
Cameron Kerr <(E-Mail Removed)> wrote:
> Hactar <(E-Mail Removed)> wrote:
> > I set up a diskless laptop (actually, it has a hard disk, but I don't
> > want to touch it) so it boots over the network, with / served via NFS
> > over 100BT. I would like network access too, so I can do normal
> > network stuff, but the distribution (Redhat 8) kills eth0 at shutdown,
> > which kills the OS by taking away / . How do I modify things so /
> > stays up regardless? Thanks.
>
> Modify your runlevel configuration so that the
> /etc/rc.d/init.d/networking is run last at shutdown.

Won't that still produce an unclean shutdown, since it'll die after that?
An unclean dismount forces an fsck on reboot (which fails, as fsck.nfs
doesn't exist).

> If its not the "networking" script, look for the file that runs ifdown
> eth0 (grep -lr ifdown /etc/rc.d/init.d/)

Yeah, I'm pretty sure it's that.

> Naturally, some experimentation may be neccessary.

Heh. This whole thing is experimentation. Installing RH8 was an adventure.

> PS. If you're looking for a X-Terminal solution, have a look at LTSP
> (www.ltsp.org).

Isn't that rather inefficient (in terms of labor expended versus benefit
gained) if there's only one client, especially for a non-dedicated server and
a rarely-used client?

--
-eben (E-Mail Removed)m home.tampabay.rr.com/hactar
LEO: Now is not a good time to photocopy your butt and staple
it to your boss' face, oh no. Eat a bucket of banana pudding
and wash it down with a gallon of strawberry Quik. -- Weird Al

Hactar <(E-Mail Removed)> wrote:
> In article <(E-Mail Removed)>,
> Cameron Kerr <(E-Mail Removed)> wrote:

>> Modify your runlevel configuration so that the
>> /etc/rc.d/init.d/networking is run last at shutdown.
>
> Won't that still produce an unclean shutdown, since it'll die after that?
> An unclean dismount forces an fsck on reboot (which fails, as fsck.nfs
> doesn't exist).

Then just remove the bit that runs ifdown. You might also remove the bit
that tries to run fsck.nfs.

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!

In article <(E-Mail Removed)>,
Cameron Kerr <(E-Mail Removed)> wrote:
> Hactar <(E-Mail Removed)> wrote:
> > In article <(E-Mail Removed)>,
> > Cameron Kerr <(E-Mail Removed)> wrote:
>
> >> Modify your runlevel configuration so that the
> >> /etc/rc.d/init.d/networking is run last at shutdown.
> >
> > Won't that still produce an unclean shutdown, since it'll die after that?
> > An unclean dismount forces an fsck on reboot (which fails, as fsck.nfs
> > doesn't exist).
>
> Then just remove the bit that runs ifdown.

That might work. Apparently I screwed up a bit modifying
/etc/rc.d/init.d/{netfs,halt} , as I get a scrolling message during
shutdown, something about an RPC server. I know, I know, it might help to
be more vague. (I could've said "It doesn't work".) Until I shut down, the
computer works fine, modulo the usual extra keys and lack of a keypad
inherent in laptops.

I was hoping for some flag that means "This filesystem is very important;
do not molest it", but no dice, I guess.

> You might also remove the bit that tries to run fsck.nfs.

Yeah, I will, but since that's not a show-stopper, it gets a lower priority.

--
-eben (E-Mail Removed)m home.tampabay.rr.com/hactar
LEO: Now is not a good time to photocopy your butt and staple
it to your boss' face, oh no. Eat a bucket of banana pudding
and wash it down with a gallon of strawberry Quik. -- Weird Al

Hactar <(E-Mail Removed)> wrote:
> In article <(E-Mail Removed)>,
> Cameron Kerr <(E-Mail Removed)> wrote:
>> Hactar <(E-Mail Removed)> wrote:

>> > An unclean dismount forces an fsck on reboot (which fails, as fsck.nfs
>> > doesn't exist).

IIRC, any network filesystem checker is just a null program (it doesn't
do anything), since you don't fsck remote filesystems.

>> Then just remove the bit that runs ifdown.
>
> That might work. Apparently I screwed up a bit modifying
> /etc/rc.d/init.d/{netfs,halt} , as I get a scrolling message during
> shutdown, something about an RPC server. I know, I know, it might help to
> be more vague. (I could've said "It doesn't work".) Until I shut down, the
> computer works fine, modulo the usual extra keys and lack of a keypad
> inherent in laptops.

Don't stop portmapper either.

> I was hoping for some flag that means "This filesystem is very important;
> do not molest it", but no dice, I guess.

Well, I guess you _could_ try to threaten it with castration, but I
wouldn't place any wagers as to it listening.

>> You might also remove the bit that tries to run fsck.nfs.
>
> Yeah, I will, but since that's not a show-stopper, it gets a lower priority.

Actually, you could achieve that by changing the last field for the /
partition in /etc/fstab to be 0 (man fstab).

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!

In article <(E-Mail Removed)>,
Cameron Kerr <(E-Mail Removed)> wrote:
> Hactar <(E-Mail Removed)> wrote:
> > In article <(E-Mail Removed)>,
> > Cameron Kerr <(E-Mail Removed)> wrote:
>
> IIRC, any network filesystem checker is just a null program (it doesn't
> do anything), since you don't fsck remote filesystems.

Hmm, I guess I could create /sbin/fsck.nfs as just

,-
| #! /bin/true
'-

,-
| #! /bin/sh
| :
'-

has the same number of characters, but may take longer to run.

> >> You might also remove the bit that tries to run fsck.nfs.
> >
> > Yeah, I will, but since that's not a show-stopper, it gets a lower
> > priority.
>
> Actually, you could achieve that by changing the last field for the /
> partition in /etc/fstab to be 0 (man fstab).

I read fstab(5), and it said something about assuming 0 for an absent 5th
and 6th fields, so I ended the line after the 4th field. Guess that doesn't
cut it. I'll try putting in actual zeroes.

--
-eben (E-Mail Removed)m home.tampabay.rr.com/hactar
CANCER: The position of Jupiter says that you should spend the
rest of the week face down in the mud. Try not to shove a roll of
duct tape up your nose when taking your driver's test. -- Weird Al

In article <bvjkbf$pk3$(E-Mail Removed)>,
Hactar <(E-Mail Removed)> wrote:
> In article <(E-Mail Removed)>,
> Cameron Kerr <(E-Mail Removed)> wrote:
> > Hactar <(E-Mail Removed)> wrote:
> > > In article <(E-Mail Removed)>,
> > > Cameron Kerr <(E-Mail Removed)> wrote:
> >
> > IIRC, any network filesystem checker is just a null program (it doesn't
> > do anything), since you don't fsck remote filesystems.
>
> Hmm, I guess I could create /sbin/fsck.nfs as just
>
> ,-
> | #! /bin/true
> '-

That works. Still haven't fixed that "touch /.autofsck" nonsense.

> > >> You might also remove the bit that tries to run fsck.nfs.
> > >
> > > Yeah, I will, but since that's not a show-stopper, it gets a lower
> > > priority.
> >
> > Actually, you could achieve that by changing the last field for the /
> > partition in /etc/fstab to be 0 (man fstab).
>
> I read fstab(5), and it said something about assuming 0 for an absent 5th
> and 6th fields, so I ended the line after the 4th field. Guess that
> doesn't cut it. I'll try putting in actual zeroes.

Something "fixed" the file, and "fixed" it with pnes. Grr. But changing
them to zero didn't help. At least I changed the "dump" field to zero...

Turns out /etc/rc.d/init.d/network is being run on shutdown. Is there any
reason to bring down the network before shutdown? Obviously, I can't kill
eth0 while / goes through it.

--
-eben (E-Mail Removed)m home.tampabay.rr.com/hactar
PISCES: Try to avoid any Virgos or Leos with the Ebola virus.
You are the Lord of the Dance, no matter what those idiots at
work say. -- Weird Al, _Your Horoscope for Today_

Hactar <(E-Mail Removed)> wrote:

> Turns out /etc/rc.d/init.d/network is being run on shutdown. Is there any
> reason to bring down the network before shutdown? Obviously, I can't kill
> eth0 while / goes through it.

Just being tidy.

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!