Date: Thu, 14 Nov 2013 09:36:50 +0100 From: rank1seeker@gmail.com To: "Devin Teske" <dteske@freebsd.org> Cc: FreeBSD Hackers <hackers@freebsd.org> Subject: Re: Loader forth changes for customization Message-ID: <20131114.083650.674.2@DOMY-PC> In-Reply-To: <18E6668A-3837-40D1-BCA0-9D68DCCD70AD@fisglobal.com> References: <5282E56F.4020307@freebsd.org> <52832003.8080406@freebsd.org> <09673101-DB54-4D25-9989-8C80D06E266B@fisglobal.com> <5283933E.30603@freebsd.org> <A0800C10-2455-477C-A2DF-FBE5A6FE6F87@mail.turbofuzz.com> <5283CBD1.9010606@freebsd.org> <86F0F59A-2DE0-42A3-9B8B-ADB1F3CA55A1@fisglobal.com> <20131114.080608.007.1@DOMY-PC> <18E6668A-3837-40D1-BCA0-9D68DCCD70AD@fisglobal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Um,
> >
> > Little of thread, but could you rewrite loader in just 1 task?
> > That is, once it has been pulled by STAGE 2 boot, ALL loader's path
should be RELATIVE to loader itself, instead currently using full path
approach (/boot/...)
> >
> > I.e;
> > Line: (from: '/sys/boot/common/interp.c')
> > include("/boot/boot.conf");
> > into:
> > include("boot.conf");
> > and so on ...
> >
> > Thanks.
> >
>
> Is that true for the Forth layer? I didn't think there was a relative
path.
> Just tested on 9.2-R loader(8):
>
> Contents of /boot/loader.rc.local:
> echo "Hello, World!"
>
> At loader(8) prompt:
> OK include /boot/loader.rc.local
> Hello, World!
> OK include loader.rc.local
> can't open 'loader.rc.local': no such file or directory
>
> --
> Devin
No no. Loader's prompt, where you type CMD's ... is out of context.
Normal loader's boot sequence should work with paths relative to loader
binary itself.
I.e; Upon boot it would pull 'defaults/loader.conf' as it is relative to
it, instead via current full path '/boot/defaults/loader.conf'
This isn't a current behaviour, but something that should be done.
Domagoj
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131114.083650.674.2>