home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!torn!cunews!revcan!software.mitel.com!sharman!sharman
- From: sharman@Software.Mitel.COM (Richard Sharman)
- Newsgroups: comp.os.linux
- Subject: Re: Problem compiling the kernel.
- Message-ID: <SHARMAN.92Jul23181022@sharman.Software.Mitel.COM>
- Date: 23 Jul 92 22:10:22 GMT
- Sender: sharman@Software.Mitel.COM
- Organization: Mitel. Kanata (Ontario). Canada.
- Lines: 29
-
- In article <1992Jul21.154453.13339@gmuvax2.gmu.edu> esaffle@gmuvax2.gmu.edu (Ed Saffle) writes:
-
- In article <1992Jul21.124846.2263@rhrk.uni-kl.de> herfert@arctecserv-1.informatik.uni-kl.de (Michael Herfert) writes:
- >I use Linux 0.96c and GCC 2.2.2.
- >Compilation of the kernel is succesfull but when running there come error messages like:
- > getwd: can not access parent directory
- >Any help ?
-
- This is the same kind of thing that happened when I first tried the linux
- boot & root images after rawrite'ing then to disks...maybe if someone comes
- up with an answer to this one, it would also be valid toward my problem.
-
-
- I think this means that that a parent of your home directory is not
- searchable. I *believe* that getwd routines typically "walk up" the
- tree from the current directory until they get to the top (the root)
- to find out "where they started from" -- i.e. the initial working
- directory. (Typically the kernel does not maintain a printable string
- corresponding to every process's current working directory, so they
- have to work it out.)
-
- So, if, say, your home directory was /home/people/fred
- check that /home and /home/people had the "other"'s 'r' and 'x'
- permission bits set.
-
-
- If the above is inacurrate would someone please let me know?
-
- rs
-