Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
soc:2009:pravin:journal:fedora11bko [2009/07/21 16:46] less1 |
soc:2009:pravin:journal:fedora11bko [2009/07/27 05:35] (current) less1 |
||
|---|---|---|---|
| Line 130: | Line 130: | ||
| - | ====== Fedora over NFS ====== | + | ====== Fedora 11 live over NFS ====== |
| - | Booting Fedora over NFS. Plan is to export the ISO over NFS from my laptop and see if it works. | + | Trying to see if Fedora 11 live can boot over NFS.\\ |
| + | The reasoning behind this experimentation is that, if it works over NFS then it may help in locating the problem. | ||
| ==== Testing NFS setup ==== | ==== Testing NFS setup ==== | ||
| Line 179: | Line 181: | ||
| The only issue with NFS_Fedora is that ''plymountd'' still creates a problem and is disabled and it somehow stops GUI coming up automatically.\\ | The only issue with NFS_Fedora is that ''plymountd'' still creates a problem and is disabled and it somehow stops GUI coming up automatically.\\ | ||
| So, the user need to login in run-level 3 and then do the ''startx'' | So, the user need to login in run-level 3 and then do the ''startx'' | ||
| + | |||
| + | |||
| + | ==== HTTPFS improvement ==== | ||
| + | Some progress has been done on HTTPFS front also. Till now, all the tests of booting over HTTPFS were done using ''qemu'' which is inherently slow as it is emulation. | ||
| + | When same tests were run on vmware, which is much faster, errors started comming after runlevel - 3 login prompt\\ | ||
| + | Following are the errors, which are quite same as those errors which use to come around sendmail daemon before. | ||
| <code> | <code> | ||
| Line 189: | Line 197: | ||
| EXT4-fs error (device dm-0): ext4_find_entry: reading directory #10651 offset 0 | EXT4-fs error (device dm-0): ext4_find_entry: reading directory #10651 offset 0 | ||
| </code> | </code> | ||
| + | With this observation, we can claim that errors are thrown because there is delay in response from fuse. The ext4-fs is giving up because of this delay.\\ | ||
| + | Now, I need to find a way to increase the tolerance for this delay. | ||
| + | |||
| + | |||
| + | ===== Removing plymouth ===== | ||
| + | As marc has suggested, remove ''plymount'' from original iso, and see if it works without plymount. | ||
| + | If it doesn't then blame can be surely put on ''plymount'' and not the network related complications. \\ | ||
| + | |||
| + | ==== Modifying ISO ==== | ||
| + | Now, the question is, how to add new initramfs into ISO and still keep it bootable?\\ | ||
| + | From Remastering Knoppix Howto, following is the command which works for knoppix | ||
| + | <code> | ||
| + | mkisofs -pad -l -r -J -v -V "KNOPPIX" -no-emul-boot -boot-load-size 4 \ | ||
| + | -boot-info-table -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat \ | ||
| + | -hide-rr-moved -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/knx/master | ||
| + | </code> | ||
| + | |||
| + | and I need to modify it, so that it will work for fedora. | ||
| + | |||
| + | <code> | ||
| + | mkisofs -pad -l -r -J -v -V "Fedora-11-i686-Live" -no-emul-boot -boot-load-size 4 \ | ||
| + | -boot-info-table -b isolinux/isolinux.bin -c isolinux/boot.cat \ | ||
| + | -hide-rr-moved -o /var/www/iso/fedora_11.iso /home/pravin/Etherboot/git/BKO.git/pxeknife/red_hat/fedora_11_live_cd/newfedora | ||
| + | </code> | ||
| + | ===== running startx from single user mode ===== | ||
| + | Tried an experiment of running ''startx'' from single user mode and see if it works.\\ | ||
| + | Well it did not worked atall. | ||
| + | |||
| + | ===== Problem Found ===== | ||
| + | With help of andyTim, the cause of problem has been located.\\ | ||
| + | The ''network'' and ''NetworkManager'' do restart the networking which breaks the existing HTTPFS mount. | ||
| + | |||
| + | |||
| + | ===== Solution ===== | ||
| + | The temporary solution tried is delete both of following files | ||
| + | - ''/etc/init.d/network'' | ||
| + | - ''/etc/init.d/NetworkManager'' | ||
| + | So, user has to first boot into single user mode, delete above files, | ||
| + | and then boot into runlevel 5. | ||
| + | |||
| + | |||
