Date: Thu, 14 Nov 2013 16:08:53 +0000 From: "Teske, Devin" <Devin.Teske@fisglobal.com> To: "<rank1seeker@gmail.com>" <rank1seeker@gmail.com> Cc: FreeBSD Hackers <hackers@freebsd.org>, Devin Teske <dteske@freebsd.org>, "Teske, Devin" <Devin.Teske@fisglobal.com> Subject: Re: Loader forth changes for customization Message-ID: <9DEB3851-653A-46EF-ACE2-03EF1978831F@fisglobal.com> In-Reply-To: <20131114.083650.674.2@DOMY-PC> 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> <20131114.083650.674.2@DOMY-PC>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 14, 2013, at 12:36 AM, <rank1seeker@gmail.com> wrote:
>>> Um,
>>>=20
>>> 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=20
> should be RELATIVE to loader itself, instead currently using full path=20
> approach (/boot/...)
>>>=20
>>> I.e;
>>> Line: (from: '/sys/boot/common/interp.c')
>>> include("/boot/boot.conf");
>>> into:
>>> include("boot.conf");
>>> and so on ...
>>>=20
>>> Thanks.
>>>=20
>>=20
>> Is that true for the Forth layer? I didn't think there was a relative=20
> path.
>> Just tested on 9.2-R loader(8):
>>=20
>> Contents of /boot/loader.rc.local:
>> echo "Hello, World!"
>>=20
>> 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
>>=20
>> --=20
>> Devin
>=20
>=20
> 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=20
> binary itself.
> I.e; Upon boot it would pull 'defaults/loader.conf' as it is relative to=
=20
> it, instead via current full path '/boot/defaults/loader.conf'
>=20
So I tried... changing a path in /boot/loader.rc
E.g., in my patchset, I changed...
try-include /boot/loader.rc.local
To instead:
try-incude loader.rc.local
The result is that the file is no longer included.
> This isn't a current behaviour, but something that should be done.
>=20
I'm finding that currently all paths in the Forth layer must be
absolute paths.
I just don't see how relative paths could work in Forth.
There's no "cd" command, to start with (what would dictate
the current working directory?? -- but more importantly,
would "include" actually adhere to it?)
--=20
Devin
_____________
The information contained in this message is proprietary and/or confidentia=
l. If you are not the intended recipient, please: (i) delete the message an=
d all copies; (ii) do not disclose, distribute or use the message in any ma=
nner; and (iii) notify the sender immediately. In addition, please be aware=
that any message addressed to our domain is subject to archiving and revie=
w by persons other than the intended recipient. Thank you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9DEB3851-653A-46EF-ACE2-03EF1978831F>