| 04:44.10 | *** join/#familiar award (i=admin@p54BE7C40.dip.t-dialin.net) |
| 04:46.02 | *** join/#familiar Amidamaru (n=Amidamar@p54A4BA47.dip.t-dialin.net) |
| 07:09.16 | *** join/#familiar inomine (n=inomine@vlad-vishnyakov.jde.aca.mmu.ac.uk) |
| 10:28.17 | *** join/#familiar Ge0rgy (n=Christop@dsl-084-057-145-253.arcor-ip.net) |
| 10:49.12 | *** join/#familiar PalatisAcerNB_ (n=palatisa@220-131-228-218.HINET-IP.hinet.net) |
| 10:54.41 | *** join/#familiar bluelightning (n=blueligh@219-89-20-156.dialup.xtra.co.nz) |
| 11:56.40 | *** join/#familiar jamey (n=jamey@30-5-42.wireless.csail.mit.edu) |
| 12:51.48 | *** join/#familiar inomine (n=inomine@213.121.151.210) |
| 13:07.40 | *** join/#familiar sageLin (n=Miranda@62.183.100.121) |
| 13:08.07 | sageLin | hi |
| 13:09.28 | sageLin | when ~ release of familiar 0.8.3? september? |
| 13:29.31 | *** join/#familiar incinerator (n=incinera@82-41-24-164.cable.ubr04.edin.blueyonder.co.uk) |
| 14:38.43 | *** join/#familiar {-award-} (i=admin@p54BE7C40.dip.t-dialin.net) |
| 15:05.00 | *** join/#familiar jamey (n=jamey@30-5-42.wireless.csail.mit.edu) |
| 15:07.49 | *** join/#familiar Amidamaru (n=Amidamar@p54A4F0D3.dip.t-dialin.net) |
| 16:21.06 | *** join/#familiar inomine (n=inomine@81-178-79-206.dsl.pipex.com) |
| 16:45.11 | *** join/#familiar peck__ (n=peck@maisel-gw.enst-bretagne.fr) |
| 19:24.22 | *** join/#familiar NetJunior (n=AnyKey@gprs-pool066.mobnet.ru) |
| 21:25.08 | *** join/#familiar oO_will_Oo (n=will@adsl-69-152-93-210.dsl.stlsmo.swbell.net) |
| 21:25.35 | oO_will_Oo | so...I can get HaRET to start up linux fine on my iPAQ 4350. If I attempt to boot it off of the initrd file that I found somewhere, it boots up, until it gets to the point where I can ssh to it. But GPE never starts like it should. So now I'm trying to boot the GPE image via NFS. I got the server running properly, but when my iPAQ goes to access it, it says "Root-NFS: Server returned error -13 while mounting /home/ip |
| 21:25.44 | oO_will_Oo | aq_rootfs". I did some (read: a lot!) of googling, but the only information I could find related to this was that it had something to do with the permissions. Or possibly the hostname, except that I use the IP address of the iPAQ. Does anyone else know of any such nfs mount errors? |
| 21:26.17 | oO_will_Oo | I'm thinking that it may have something to do with the way it's being exported. The line goes "I'm thinking that it may have something to do with the way it's being exported. The line goes "/home/ipaq_rootfs 192.168.0.202/32(rw,insecure,sync,no_wdelay,no_root_squash)" |
| 21:38.46 | *** join/#familiar BBrox (n=ulmer@bbrox.org) |