Date: Wed, 14 Mar 2018 09:11:55 -0400 From: Mark Saad <nonesuch@longcount.org> To: Warner Losh <imp@bsdimp.com> Cc: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net>, Kristoffer Eriksson <ske@pkmab.se>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, Theron <theron.tarigo@gmail.com> Subject: Re: GSoC Idea: per-process filesystem namespaces for FreeBSD Message-ID: <CAMXt9Na-Mzc2GtQoUQe3%2BYaqDwg3MoGa-ztCa4w=BwQSQv=Bmg@mail.gmail.com> In-Reply-To: <CANCZdfrpSUX9NMkzJuHtJY2ySkdOYE_61RT4C%2BgNnfZAT_mUNA@mail.gmail.com> References: <CAMXt9NbsZ%2B2K4JhBOvEWVGoa5tq5PeUY6=ab=MOW1M47RJOeMw@mail.gmail.com> <201803140353.w2E3rHN1086319@pdx.rh.CN85.dnsmgr.net> <CANCZdfrpSUX9NMkzJuHtJY2ySkdOYE_61RT4C%2BgNnfZAT_mUNA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner
I'll see if I can get this working , later today. From what I
remember with NetBSD changes back in 2004 they wanted to get Xen
working booting from Grub with out chain loading.
If memory serves me that's what led them into getting the kernel to
boot via the multiboot protocol . Solaris/Illumos can also do the same
. I use iPXE at work to network boot an Illumos derivative with a
kernel, boot archive and some variables to govern console bits and
what not. In a weird sort of coincidence Illumos imported FreeBSD's
loader to try and dump Grub so
maybe everything is there already ? Lets see what I can get working today.
>> > >> > Warner
>> > >>
>> > >> I am going down the rabbit hole to see how it works .
>> > >
>> > > If you have any questions I am happy to share my working tooling.
>> > >
>> >
>> > I think you are both missing my point. I can boot FreeBSD with ipxe
>> > loading mfsbsd style setups like this
>> >
>> > :freebsd
>> > initrd ${base-root}/freebsd/mfsroot.gz
>> > chain ${base-root}/other/memdisk harddisk raw
>>
>> Nope, not what I am doing.
>>
>> > I want to be able to boot and run it like I would Linux or ESXi with
>> > the ability to directly load an kernel and a mfsroot/initrd and pass
>> > kernel loader arguments
>> >
>> > :centos674
>> > set centos674_args edd=off ramdisk_size=50000 nomodeset
>> > ks=${centos-root}/CentOS6.7_x64/ks/supermicro-4drives.ks
>> > ksdevice=${net0/mac} verbose ip=dhcp
>> > root-path=${centos-root}/CentOS6.7_x64/OS/ net.ifnames=0 biosdevname=0
>> > nousb
>> > echo ${centos674_args}
>> > kernel ${base-root}/centos/CentOS6.7_x64/isolinux/vmlinuz
>> > ${centos674_args}
>> > initrd ${base-root}/centos/CentOS6.7_x64/isolinux/initrd.img
>>
>> :freebsd6411
>> set root-path 192.168.48.38:/B/FreeBSD/11.0/amd64
>> iseq ${platform} efi && chain
>> nfs://192.168.48.38/B/FreeBSD/11.0/amd64/boot/loader.efi || chain
>> nfs://192.168.48.38/B/FreeBSD/11.0/amd64/boot/pxeboot
>> boot || goto failed
>> goto start
>>
>> I agree it would be nice to get the "variable=value" stuff working.
>> I do know the above does infact pass that root-path to the kernel,
>> and without that mountroot fails, so some of this is working
>
>
> right, loader.efi and/or pxebooot is what sets the root path (and other
> variables). What others are asking for is some kind way to do just load the
> kernel + a bundle of variables with some kind of 'mini /boot/loader' (in our
> terms) that can turn the bundle into the metadata the kernel needs to do
> it's job. We have an extra layer of with loader.efi/pxeboot and linux
> doesn't...
>
> Warner
--
mark saad | nonesuch@longcount.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMXt9Na-Mzc2GtQoUQe3%2BYaqDwg3MoGa-ztCa4w=BwQSQv=Bmg>