From: hume.spamfilter on
Richard B. Gilbert <rgilbert88(a)comcast.net> wrote:
> As usual, what the OP wrote is lost in the mists of time. Overly
> vigorous trimming has not helped matters much.

The "mists of time" being three days ago. You need to have a talk with your
Usenet provider.

> Booting from the CD/DVD, as I suggested, gives you a minimal system that
> should run on just about any supported hardware configuration and,

And it does absolutely nothing to fix the problem. His system is up, his
system is functional, and he has access to root. Walking him through the
steps of HOW to boot from DVD, and then HOW to mount his existing filesystems,
puts us back in the SAME PLACE of trying to figure out what's wrong with
his system so he can fix it in the first place.

> which drivers are available. It is an occasionally useful technique
> but not the solution to every problem.

Which is why you try to find out what's really going on. You don't read the
simple question "how do i find out if root's homedir exists" and say "OMG NO
ROOT HOMEDIR his system is wrecked now I can show my leet skillz!"

But then you wouldn't be able to take little holier-than-thou "I expect a
little more!" potshots at people, would you?

--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
From: happytoday on
On Feb 19, 6:40 pm, hume.spamfil...(a)bofh.ca wrote:
> Richard B. Gilbert <rgilber...(a)comcast.net> wrote:
>
> > As usual, what the OP wrote is lost in the mists of time.  Overly
> > vigorous trimming has not helped matters much.
>
> The "mists of time" being three days ago.  You need to have a talk with your
> Usenet provider.
>
> > Booting from the CD/DVD, as I suggested, gives you a minimal system that
> >  should run on just about any supported hardware configuration and,
>
> And it does absolutely nothing to fix the problem.  His system is up, his
> system is functional, and he has access to root.  Walking him through the
> steps of HOW to boot from DVD, and then HOW to mount his existing filesystems,
> puts us back in the SAME PLACE of trying to figure out what's wrong with
> his system so he can fix it in the first place.
>
> > which drivers are available.  It is an occasionally useful technique
> > but not the solution to every problem.
>
> Which is why you try to find out what's really going on.  You don't read the
> simple question "how do i find out if root's homedir exists" and say "OMG NO
> ROOT HOMEDIR his system is wrecked now I can show my leet skillz!"
>
> But then you wouldn't be able to take little holier-than-thou "I expect a
> little more!" potshots at people, would you?
>
> --
> Brandon Hume    - hume -> BOFH.Ca,http://WWW.BOFH.Ca/

I found /etc/passwd with /home/root for the root user. I changed into /
root and I reboot with the same wrror messages .
From: Tony Sequeira on
happytoday wrote:

>
> I found /etc/passwd with /home/root for the root user. I changed into /
> root and I reboot with the same wrror messages .

How did you change it?

--
S. Anthony Sequeira
++
You can always pick up your needle and move to another groove.
-- Tim Leary
++
From: hume.spamfilter on
happytoday <ehabaziz2001(a)gmail.com> wrote:
> I found /etc/passwd with /home/root for the root user. I changed into /
> root and I reboot with the same wrror messages .

But does /root exist? Does /home/root exist? This problem, if it IS the
problem, is that root's home directory is set to a directory that does not
exist. Changing root's home directory from one directory that doesn't
exist to ANOTHER directory that doesn't exist doesn't fix anything. Or,
worse, you might change it from a directory that DOES exist to one that
doesn't.

Please don't blindly change things without thinking about what you're
trying to accomplish.

--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
From: Richard B. Gilbert on
hume.spamfilter(a)bofh.ca wrote:
> Richard B. Gilbert <rgilbert88(a)comcast.net> wrote:
>> As usual, what the OP wrote is lost in the mists of time. Overly
>> vigorous trimming has not helped matters much.
>
> The "mists of time" being three days ago. You need to have a talk with your
> Usenet provider.
>
>> Booting from the CD/DVD, as I suggested, gives you a minimal system that
>> should run on just about any supported hardware configuration and,
>
> And it does absolutely nothing to fix the problem. His system is up, his
> system is functional, and he has access to root. Walking him through the
> steps of HOW to boot from DVD, and then HOW to mount his existing filesystems,
> puts us back in the SAME PLACE of trying to figure out what's wrong with
> his system so he can fix it in the first place.
>
>> which drivers are available. It is an occasionally useful technique
>> but not the solution to every problem.
>
> Which is why you try to find out what's really going on. You don't read the
> simple question "how do i find out if root's homedir exists" and say "OMG NO
> ROOT HOMEDIR his system is wrecked now I can show my leet skillz!"
>
> But then you wouldn't be able to take little holier-than-thou "I expect a
> little more!" potshots at people, would you?
>

Thank you for the lecture!

In order to find out if root's home directory exists, you must first
find out where it is supposed to be. It defaults to "/". AFAIK it
*could* be anywhere in the directory tree!

And if I'm "holier-than-thou" I'm sure that the deficiency is yours!

)*(