From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <85bf7121860414351258e9f66e14f165@quintile.net> References: <5d375e920908271227r28126d0n4c00f6fb14127982@mail.gmail.com> <85bf7121860414351258e9f66e14f165@quintile.net> Date: Thu, 27 Aug 2009 19:05:31 -0300 Message-ID: From: Iruata Souza To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] new 9atom.iso Topicbox-Message-UUID: 58738ab2-ead5-11e9-9d60-3106f5b1d025 On Thu, Aug 27, 2009 at 6:57 PM, Steve Simon wrote: > 9fat is also a pain in that the 9load file must be created with, > and retain its append only file, which has a special meaning to 9fat > telling it to create the file in sequential blocks. > > This could (and has) caused problems if you access the 9fat partition > from os's other than plan9. > > The only times I have had to change plan9.ini from somthing else > than the booted system (because I have broken the boot process) > I booted the plan9 live cdrom. > > I would be happy if 9load and 9fat disappeared and it was > replaced with a plan9 bootstrap kernel and (say) an rc(1) script. > that's just what 9null is: new pbs, 9pcload (bootstrap kernel), /boot/boot using rc(1) scripts. instead of a 'root from' you may get a 'kernel is at' prompt to which you can ask for a shell (!rc) iru