Date: Wed, 7 Jul 2010 13:00:32 -0700 From: Randi Harper <randi@freebsd.org> To: "Mikhail T." <mi+thun@aldan.algebra.com> Cc: freebsd-stable@freebsd.org Subject: Re: net-booting the install disks (Re: 8.x grudges) Message-ID: <AANLkTimQFCxQpCx32dxvYscGspUkqyRbyPE_ru8RS5My@mail.gmail.com> In-Reply-To: <4C34CA31.7010804@aldan.algebra.com> References: <4C34C5DE.7040007@aldan.algebra.com> <AANLkTil1jtcgOV5c5rLQabS2kJ2DA09haRY3VB0bgA8x@mail.gmail.com> <4C34CA31.7010804@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2010/7/7 Mikhail T. <mi+thun@aldan.algebra.com>:
> 07.07.2010 14:30, Randi Harper =CE=C1=D0=C9=D3=C1=D7(=CC=C1):
>
> =9A8.
>> =9A =9A I tried to do an install on one of the systems via netbooting
>> =9A =9A (pxeload) the disk1-image. It booted, but the sysinstall had to =
be
>> =9A =9A started manually and, once started, did not act the same as when
>> =9A =9A booted off of CD-ROM. Seems like a simple bit to correct so that
>> =9A =9A setting "init" to /usr/sbin/sysinstall/manually on every boot/ i=
s
>> =9A =9A not necessary...
>
>
> This shouldn't be the case. IIRC, nothing has changed that would cause
> this. More info on your environment please?
>
>
> Well, I never tried this part before, so I'm not claiming, there is
> regression here. Just lack of progress :-)
>
> I have the following special entry in the dhcpd.conf:
>
> subnet 192.168.1.0 netmask 255.255.255.0 {
> =9A=9A=9A=9A=9A=9A=9A range dynamic-bootp 192.168.1.150 192.168.1.186;
> =9A=9A=9A=9A=9A=9A=9A next-server 192.168.1.140;
> =9A=9A=9A=9A=9A=9A=9A option broadcast-address 192.168.1.255;
> =9A=9A=9A=9A=9A=9A=9A option routers 192.168.1.1;
> =9A=9A=9A=9A=9A=9A=9A option root-path "192.168.1.140:/cdrom";
> =9A=9A=9A=9A=9A=9A=9A filename=9A=9A=9A=9A=9A=9A=9A "pxeboot";
> }
>
> The filesystem accessible as /cdrom was an md-accessed
> FreeBSD-8.1-RC1-i386-disc1.iso (or bootonly). Can't easily recreate this,
> because the netbooting machine has now gone back to its owner.
>
> The problem did not surprise me, because I followed (loosely) the
> instructions, where it was mentioned -- along with a work-around. If some
> simple logic can be put into the boot-image to allow it to do the right
> thing without manual fiddling, it would be great. Thanks!
>
> -mi
>
So.... you're complaining that you have to modify the loader.conf? I
fail to see the problem. This is by design, and isn't a lack of
progress.
-- randi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimQFCxQpCx32dxvYscGspUkqyRbyPE_ru8RS5My>