From owner-freebsd-questions Sat Sep 22 21:57:45 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mta04.mail.mel.aone.net.au (mta04.mail.au.uu.net [203.2.192.84]) by hub.freebsd.org (Postfix) with ESMTP id 2C45037B42A for ; Sat, 22 Sep 2001 21:57:39 -0700 (PDT) Received: from pc99101401.homenet.xxx ([63.34.214.38]) by mta04.mail.mel.aone.net.au with SMTP id <20010923045732.UBVL6258.mta04.mail.mel.aone.net.au@pc99101401.homenet.xxx> for ; Sun, 23 Sep 2001 14:57:32 +1000 Message-ID: <005301c143ec$39951920$022aa8c0@homenet.xxx> From: "MurrayTaylor" To: Subject: Does a make world change the bootblock ... Date: Sun, 23 Sep 2001 14:57:05 +1000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0050_01C14440.02B69380" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0050_01C14440.02B69380 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am trying to get around the wd / ad drive problem that=20 has occurred on a new install i am doing... I have 4.2 CD roms -- I am on a virgin machine -- I am getting the=20 'specified device is not the same as curently mounted' error during the booting process ... and mount shows that / is on wd0s2a and all the rest are on ad0s2 ..... I have booted properly by intercepting the boot process and using=20 0:ad(0,a)/kernel instead of=20 0:ad(0,a)/boot/loader as the boot target .. I have cross-loaded the cvsup 16.1e stuff from a cousin machine and an(have) cvsupped to RELENG_4_4 ... I am about to=20 make buildworld make buildkernel -DKERNEL=3DGENERIC make iinstallkernel -DKERNEL=3DGENERIC reboot make installworld and want to know when or if the bootblock or whatever chunk is giving the old wd driver gets fixed/clobbered/overwritten correctly... ie will i need to snag the boot again and enter 0:ad(0,a)/kernel = ??? mjt ------=_NextPart_000_0050_01C14440.02B69380 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I am trying to get around the wd / ad = drive problem=20 that
has occurred on a new install i am=20 doing...
 
I have 4.2 CD roms -- I am on a virgin = machine -- I=20 am getting the
'specified device is not the same as = curently=20 mounted' error
during the booting process ... and = mount=20 shows
that / is on wd0s2a and all the rest = are on ad0s2=20 .....
 
I have booted properly by intercepting = the boot=20 process
and using
0:ad(0,a)/kernel
instead of
0:ad(0,a)/boot/loader
as the boot target ..
 
I have cross-loaded the cvsup 16.1e = stuff from a=20 cousin machine
and an(have) cvsupped to RELENG_4_4=20 ...
 
I am about to
make buildworld
make buildkernel = -DKERNEL=3DGENERIC
make iinstallkernel = -DKERNEL=3DGENERIC
reboot
make installworld
 
and want to know when or if the bootblock or whatever chunk = is
giving the old wd driver gets fixed/clobbered/overwritten=20 correctly...
 
ie will i need to snag the boot again and enter   =20 0:ad(0,a)/kernel   ???
 
 
mjt
 
------=_NextPart_000_0050_01C14440.02B69380-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message