Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Simple\s+XFS\s+read\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Simple\s+XFS\s+read\?\s*$/: 8 ]

Total 8 documents matching your query.

1. Simple XFS read? (score: 1): Author: Rob Aagaard <rob@xxxxxxxxxxxxxxxxxxx>; Date: Mon, 17 Apr 2000 18:01:59 -0700; How complicated would it be to have a simple XFS reading program? Would this be an involved process? or something trivial? The reason I am asking is because of programs like grub and milo, bootloader; /archives/xfs/2000-04/msg00221.html (7,110 bytes)
2. Re: Simple XFS read? (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Mon, 17 Apr 2000 19:24:03 -0500; If you mean actually do the mapping from a path name to an inode and then get the file blocks without kernel support, then the amount of code involved is somewhat large - given the potential meta-da; /archives/xfs/2000-04/msg00222.html (8,820 bytes)
3. Re: Simple XFS read? (score: 1): Author: Jim Mostek <mostek@xxxxxxx>; Date: Mon, 17 Apr 2000 20:40:48 -0500 (CDT); You can also use the xfs_db command. With this command you can walk the path ... Do a help. For example, sb 0 p prints the super block and you can see the root inode number, usually 128. inode 128 p; /archives/xfs/2000-04/msg00223.html (10,246 bytes)
4. Re: Simple XFS read? (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Mon, 17 Apr 2000 19:44:02 -0500; Grub is a bootloader (I think) so far as I know, it is running before the kernel - it needs to be self contained, sort of like sash on Irix. Steve; /archives/xfs/2000-04/msg00224.html (8,066 bytes)
5. Simple XFS read? (score: 1): Author: Rob Aagaard <rob@xxxxxxxxxxxxxxxxxxx>; Date: Mon, 17 Apr 2000 18:01:59 -0700; How complicated would it be to have a simple XFS reading program? Would this be an involved process? or something trivial? The reason I am asking is because of programs like grub and milo, bootloader; /archives/xfs/2000-04/msg00497.html (7,110 bytes)
6. Re: Simple XFS read? (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Mon, 17 Apr 2000 19:24:03 -0500; If you mean actually do the mapping from a path name to an inode and then get the file blocks without kernel support, then the amount of code involved is somewhat large - given the potential meta-da; /archives/xfs/2000-04/msg00498.html (8,820 bytes)
7. Re: Simple XFS read? (score: 1): Author: Jim Mostek <mostek@xxxxxxx>; Date: Mon, 17 Apr 2000 20:40:48 -0500 (CDT); You can also use the xfs_db command. With this command you can walk the path ... Do a help. For example, sb 0 p prints the super block and you can see the root inode number, usually 128. inode 128 p; /archives/xfs/2000-04/msg00499.html (10,246 bytes)
8. Re: Simple XFS read? (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Mon, 17 Apr 2000 19:44:02 -0500; Grub is a bootloader (I think) so far as I know, it is running before the kernel - it needs to be self contained, sort of like sash on Irix. Steve; /archives/xfs/2000-04/msg00500.html (8,066 bytes)

Current List: 1 - 8
Page: [1]