CD bootcode

[John Baldwin]

On Friday, June 08, 2012 10:33:00 am rank1seeker at gmail.com wrote:
> ----- Original Message -----
> From: John Baldwin <jhb at freebsd.org>
> To: rank1seeker at gmail.com
> Cc: hackers at freebsd.org
> Date: Thu, 7 Jun 2012 11:16:33 -0400
> Subject: Re: CD bootcode
> 
> > On Thursday, June 07, 2012 9:58:25 am rank1seeker at gmail.com wrote:
> > > ----- Original Message -----
> > > From: John Baldwin <jhb at freebsd.org>
> > > To: freebsd-hackers at freebsd.org
> > > Cc: rank1seeker at gmail.com
> > > Date: Thu, 7 Jun 2012 08:21:39 -0400
> > > Subject: Re: CD bootcode
> 
> > > But even when loader is finally started, loader handles symlinks on UFS (kicked by '/boot/boot'), BUT fails so, on Rock-Ridge iso (kicked by 
> > '/boot/cdboot')
> > > Looks like loader must be made into looking at Rock-Ridge extensions.
> > 
> > It is src/lib/libstand/cd9660.c that would have to be patched.  It already has
> > limited Rock-Ridge support, so adding symlink support to cd9660_open() may not
> > be that hard to do.
> > 
> > -- 
> > John Baldwin
> 
> 
> Problem should be solved in 2 groups/steps.
> 
> First
> -----
> stage 2 boot '/boot/boot' AND '/boot/cdboot' shouldn't be made into working with symlinks.
> Just leave them, the way they are. First one can be navigated to loader via 'boot.config' file.
> So only '/boot/cdboot' should be edited, to react to the same 'boot.config' file as '/boot/boot' does.
> Simply because they both target 'loader', 'boot.config' should work for both bootcodes.

Adding /boot.config support to cdboot is non-trivial.  Also, cdboot is
intended for read-only media, so dynamic configuration via a file is not
quite as useful.

> Second
> ------
> 'loader' should be edited, to work with Rock-Ridge extensions.

It already supports RR for names, it is merely symlink support that has to be
added.

-- 
John Baldwin