Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The structure /a/g/isos/ is of course non-FHS but has the same permissions as my home.
I have tried this with and without the bash -i command same result.
3) It looks like a chroot...until you notice that hostname.
I suspect that this is the reason why I am getting some errors in trying to compile a kernel under chroot and or when I tried to install newt....it gave me errors consistent with finding my host locale and not the locale of the unpacked iso.
thanks for helping as well...I used copy and paste and here is a similar error
bash-3.2# ./chrootcode
./chrootcode: line 6: syntax error near unexpected token `('
./chrootcode: line 6: `int main (int argc, char *argv[]){'
2) And does anyone know if stat of / must produce inode of 2 or is return of 128 ok?
3) Trying to be smart...I wondered if chroot on host was rooted so I swapped in the unpacked iso edition of chroot but I still get my hostname from host showing up.
1) ok am just testing mandriva 2008.1 stat of / gives 2 inode...thats a relief.
thanks for the heads up on 2...my mdv 2008.0= the host =the real thing must have a weird glitch. Looks like I will be migrating faster than expected.
2) sorry for misleading you guys by running it as a executable file....shows I have more to learn.
3) but a repeat of normal chroot commands on 2008.1 and running hostname still gives my real host hostname...false tho it is....
gs.net
3) using gcc stuff....first attempt got a newline error so added a blank line to the c file and my host without chrooting....as expected...gives not chrooted. (So code works)
I am unable to complete the test inside the unpack at this stage as I just found out....it has not compiler.
I attempted to just copy the new c file that I called code into the unpack but get this error after chrooting into the unpack
bash-3.2# ./code
Floating point exception
but me thinks I need a gcc in there first.
4) I will have to sign off at this stage until I get my new distro up to the point where I am happy with it.
AFAIK "/" is points to the Virtual FileSystem, maybe searching for Filesystem or VFS HOWTO/texts or a copy of "Understanding the Linux Kernel" might help.
I am not prepared to buy the book sorry. I was hoping for a online instruction why / had to be inode 2
your second link shows
A single inode can be pointed to by multiple dentries...explains why I had proc and sysfs with same inode. (I hope)
I was hoping to find a reference that said something like
/ inode 2 ..../root inode x etc.
2) I have not solved the probable leaking chroot as indicated by the output of hostname
3) I will only post back when others indicate (maybe on Mdv) they too have an issue with leaking chroot or I discover a new way of fixing it.
After discovering I needed to install a slack gcc and dependencies to test the chroot code....I gave up because my initial reason for doing it...on another post appears to have lapsed with that poster. He wanted to build a new kernel with RIP.
ok my understanding is that....quote"
inode number
This is the number of the inode and is unique within this file system. The combination of device and inode number is unique within the Virtual File System,"
so ignoring virtual files...real files and folders should not have the same inode?
So inode of 2 is supposed to be for /...no problem
but / mounts to /dev/sda1
I have a new partition called /dev/sda2 and its mount point is
/mnt/a
it could of course be called /data or anything
....on IRC at sidux...an attempt was made by worthy ppl to try and explain it....and I almost understood it....as....
for each distro installed...each mount point has the same inode internal to each and different from a different distro....but I still can not resolve the initial quote...that inodes point to files and so I should have a different indode at /mnt/a
Anyone care to offer an explanation?
So do I have a corrupt filesystem or not?
thanks for reading and I hope you enjoy me squiriming with lack of understanding heh heh
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.