Of course, the /proc mount point has to exist, procfs support has to be
compiled into the kernel, and you need the proper /etc/fstab entry (yours,
btw, looks a bit bogus; the option should be "defaults", not "default").
Since you copied your filesystem from one device to another, I'd suspect
that the copy process fouled up your target directory structure (likely by
not copying the /proc mountpoint).
Take a look; do you _have_ a /proc? Is it empty (when the procfs isn't
mounted)? What permissions does it have? What user and group is it assigned
Lew Pitcher, Information Technology Consultant, Toronto Dominion Bank Financial Group
(Opinions expressed are my own, not my employer's.)
The /proc filesystem is only an illusion; the mount point was not created.Quote:
> What are the issues for moving an entire system to another hdd? I
> tried that, and copied all the files using... whatever it was they
> recommended (something like "cp -dpR"?) , then fought with lilo for a
> while, but now when I start up I get "mount point proc does not
> exist", and it goes into a maintenance login prompt. The only
> interesting thing in my fstab is:
> none /proc proc default 0 0
> What could have happened to the proc file system? So far the only
> answer I've gotten to that was a bunch of twaddle from some disturbed
> Dutch dork.
At the maintenance prompt:
# mkdir /proc; chown root:root /proc; chmod 0555 /proc; exit
and things should be OK.
Yep. That must have been it. I think when I was copying theQuote:
>The /proc filesystem is only an illusion; the mount point was not created.
>At the maintenance prompt:
># mkdir /proc; chown root:root /proc; chmod 0555 /proc; exit
When I run pppd, I got below message from /var/log/messages. Can anyont
tell what it means and how to resolve it?
Mar 10 22:32:14 kernel: Cannot read proc file system: 9 - Bad file