From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200401292327.i0TNR3V07615@zamenhof.cs.utwente.nl> To: 9fans@cse.psu.edu Subject: Re: [9fans] boot via aan from fileserver? In-reply-to: Your message of "Mon, 26 Jan 2004 09:19:57 +0100." <7936203a0948a36b8954bb9f3f73d4d1@plan9.escet.urjc.es> References: <7936203a0948a36b8954bb9f3f73d4d1@plan9.escet.urjc.es> From: Axel Belinfante MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7609.1075418823.1@zamenhof.cs.utwente.nl> Date: Fri, 30 Jan 2004 00:27:03 +0100 Topicbox-Message-UUID: c58b35d6-eacc-11e9-9e20-41e7f4b1d025 nemo replied to my question about using aan to boot from fileserver: > In the mean time you can perhaps reexport your > worm fs form a cpu server, and use aan on that. > But I'd say you better switch to fossil. You could > have used aan directly then. I'm now trying the reexport approach. The simplest approach seemed to use import to get /root from the cpu server, and let import use aan. However, import -p uses /bin/aan, whereas in the boot trick I will have /boot/aan. As work around I added a -P aanprog flag to import, and hacked the boot code to have a new bootmethod 'tcpaan' that run's this import to get /root from the cpu server, in a way similar to fossil is started. I at least succeeded to boot, and indeed aan is 'in' the connection, as far as I can see. I'll just let it run for some days and see what happens.\ Just curious: what network outage would I 'need' to benefit from aan improved reliability? (So far, I got the root fs via tcp over cable modem to cpu which run trampoline to get to worm fs via il.) Out of curiousity: would there have been a simpler way than the on I described above? And just one remark: once I had been browsing the boot code enough to be a bit comfortable with its structure, adding the new boot method turned out to be surprisingly simple (the fact that all pieces I needed similar code already appeared here and there (tcp, fossil boot) of course helped immensely) Axel.