10:56 a.m.
This adds initial support for FreeBSD (8.0,8.1,8.2) media importing.
There are some additional manual steps that have to be taken in order
to actually get the install to work, but this sets you up and puts you
in a good spot so those are pretty minimal. I'll work on documenting
the manual stuff on the Cobbler wiki when I get a minute. It's mostly
changing the name of the pxeboot file (our kernel) that's found in the
media to pxeboot.bs, which isn't found in the media and needs to be
created and added to the media. Doug and I discussed a few different
ways we might deal with this.... and we can discuss them here.... but
for now just manually updating the name of the kernel following media
import works (from my chair).
https://github.com/jsabo/cobbler/commit/dfdcabf633d3ee3ca02fc1177b3e9b2d4...
I've tested this quite a few times.
Thanks,
Jonathan
1:02 p.m.
On Mon, Jul 11, 2011 at 8:56 AM, Jonathan Sabo <jsabo(a)criminal.org> wrote:
This adds initial support for FreeBSD (8.0,8.1,8.2) media importing.
There are some additional manual steps that have to be taken in order
to actually get the install to work, but this sets you up and puts you
in a good spot so those are pretty minimal. I'll work on documenting
the manual stuff on the Cobbler wiki when I get a minute. It's mostly
changing the name of the pxeboot file (our kernel) that's found in the
media to pxeboot.bs, which isn't found in the media and needs to be
created and added to the media. Doug and I discussed a few different
ways we might deal with this.... and we can discuss them here.... but
for now just manually updating the name of the kernel following media
import works (from my chair).
https://github.com/jsabo/cobbler/commit/dfdcabf633d3ee3ca02fc1177b3e9b2d4...
I've tested this quite a few times.
Thanks,
Jonathan
Thank you very much Jonathan - do you think your approach will also
work for OBSD or is it FreeBSD specific? Can FreeBSD be passed a
kickstart file? or are you limited to only installing preconfigured
images?
TIA Ed
2:01 p.m.
Ed - 0x1b, Inc. wrote:
Thank you very much Jonathan - do you think your approach will also
work for OBSD or is it FreeBSD specific? Can FreeBSD be passed a
kickstart file? or are you limited to only installing preconfigured
images?
I've not looked at OBSD at all.
For FreeBSD, the default installer wants the kickstart file to be baked
into the ramdisk. However it's easy enough to build a ramdisk that
fetches it's answer file remotely. And that's what I did.
For those who want to do this themselves, a quick primer to FreeBSD
automated installs, at least up to version 8. :)
1. The default PXE boot loader wants to use NFS. So you need to
recompile it. Build (by old methods) a FreeBSD system with all the
source code on it, and run
(cd /sys/boot; make; make LOADER_TFTP_SUPPORT=yes install)
2. The PXE boot loader uses absolute names. That means to support more
than one version at a time, you'll need to use the python tftp server.
3. The default sysinstall doesn't *really* do HTTP installs. The HTTP
method is just an HTTP proxy for an FTP server. You'll need to patch it
to do HTTP, or export your repository via FTP. Patch available upon
request. (Yes, I submitted it upstream, but the intent is to throw out
sysinstall, so it was not applied)
4. You need to create a new ram disk.
a. Path/recompile sysinstall?
b. Create a boot_crunch with some more tools in it, like "fetch"
and probably some more shell utils (see below)
c. Create a shell script that can download an answer file from
cobbler. That's short enough that I attached it
d. Create a new install.cfg that calls your handy doconfig.sh script
e. Combine all the above in a new mfsroot. That will be your initrd
in cobbler
IIRC, Jonathan's patch should handle most of the cobbler steps (the
/boot directory, setting fetchable_files.
If anyone wants the full breakdown on creating the ramdisk, let me know.
I've got an email around here somewhere with most of the details.
Doug
--
Doug Kilpatrick
kilpatds(a)oppositelock.org
# Turn on extra debugging.
debug=YES
# Turn off all prompting.
nonInteractive=YES
noWarn=YES
command=/bin/sh /stand/doconfig.sh
system
# Chain to the config we just downloaded
configFile=/stand/cobbler.cfg
loadConfig
2:38 p.m.
On Mon, Jul 11, 2011 at 3:01 PM, Douglas Kilpatrick
<kilpatds(a)oppositelock.org> wrote:
Ed - 0x1b, Inc. wrote:
>
> Thank you very much Jonathan - do you think your approach will also
> work for OBSD or is it FreeBSD specific? Can FreeBSD be passed a
> kickstart file? or are you limited to only installing preconfigured
> images?
I've not looked at OBSD at all.
For FreeBSD, the default installer wants the kickstart file to be baked into
the ramdisk. However it's easy enough to build a ramdisk that fetches it's
answer file remotely. And that's what I did.
For those who want to do this themselves, a quick primer to FreeBSD
automated installs, at least up to version 8. :)
1. The default PXE boot loader wants to use NFS. So you need to recompile
it. Build (by old methods) a FreeBSD system with all the source code on it,
and run
(cd /sys/boot; make; make LOADER_TFTP_SUPPORT=yes install)
2. The PXE boot loader uses absolute names. That means to support more
than one version at a time, you'll need to use the python tftp server.
3. The default sysinstall doesn't *really* do HTTP installs. The HTTP
method is just an HTTP proxy for an FTP server. You'll need to patch it to
do HTTP, or export your repository via FTP. Patch available upon request.
(Yes, I submitted it upstream, but the intent is to throw out sysinstall,
so it was not applied)
4. You need to create a new ram disk.
a. Path/recompile sysinstall?
b. Create a boot_crunch with some more tools in it, like "fetch"
and probably some more shell utils (see below)
c. Create a shell script that can download an answer file from
cobbler. That's short enough that I attached it
d. Create a new install.cfg that calls your handy doconfig.sh script
e. Combine all the above in a new mfsroot. That will be your initrd
in cobbler
IIRC, Jonathan's patch should handle most of the cobbler steps (the /boot
directory, setting fetchable_files.
If anyone wants the full breakdown on creating the ramdisk, let me know.
I've got an email around here somewhere with most of the details.
Doug
--
Doug Kilpatrick
kilpatds(a)oppositelock.org
# Turn on extra debugging.
debug=YES
# Turn off all prompting.
nonInteractive=YES
noWarn=YES
command=/bin/sh /stand/doconfig.sh
system
# Chain to the config we just downloaded
configFile=/stand/cobbler.cfg
loadConfig
_______________________________________________
cobbler-devel mailing list
cobbler-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler-devel
I've updated the Cobbler wiki's SupportForOtherDistros page with the
steps to install FreeBSD 8.X.
https://fedorahosted.org/cobbler/wiki/SupportForOtherDistros
Thanks,
Jonathan
5:56 p.m.
On Mon, 11 Jul 2011 11:56:46 -0400, Jonathan Sabo <jsabo(a)criminal.org> wrote:
This adds initial support for FreeBSD (8.0,8.1,8.2) media importing.
There are some additional manual steps that have to be taken in order
to actually get the install to work, but this sets you up and puts you
in a good spot so those are pretty minimal. I'll work on documenting
the manual stuff on the Cobbler wiki when I get a minute. It's mostly
changing the name of the pxeboot file (our kernel) that's found in the
media to pxeboot.bs, which isn't found in the media and needs to be
created and added to the media. Doug and I discussed a few different
ways we might deal with this.... and we can discuss them here.... but
for now just manually updating the name of the kernel following media
import works (from my chair).
https://github.com/jsabo/cobbler/commit/dfdcabf633d3ee3ca02fc1177b3e9b2d4...
I've tested this quite a few times.
Applied. Thanks.
--
Scott Henson
Red Hat SOC Operator
WVU Alum BSAE/BSME
4652
days inactive
4679
days old
cobbler-devel@lists.fedorahosted.org
4 comments
4 participants
participants (4)
-
Douglas Kilpatrick -
Ed - 0x1b, Inc. -
Jonathan Sabo -
Scott Henson