Date: Sun, 23 Sep 2001 14:57:05 +1000 From: "MurrayTaylor" <mjtlx@ozemail.com.au> To: <freebsd-questions@freebsd.org> Subject: Does a make world change the bootblock ... Message-ID: <005301c143ec$39951920$022aa8c0@homenet.xxx>
next in thread | raw e-mail | index | archive | help
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 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>I am trying to get around the wd / ad = drive problem=20 that </FONT></DIV> <DIV><FONT face=3DArial size=3D2>has occurred on a new install i am=20 doing...</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I have 4.2 CD roms -- I am on a virgin = machine -- I=20 am getting the </FONT></DIV> <DIV><FONT face=3DArial size=3D2>'specified device is not the same as = curently=20 mounted' error</FONT></DIV> <DIV><FONT face=3DArial size=3D2>during the booting process ... and = mount=20 shows</FONT></DIV> <DIV><FONT face=3DArial size=3D2>that / is on wd0s2a and all the rest = are on ad0s2=20 .....</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I have booted properly by intercepting = the boot=20 process</FONT></DIV> <DIV><FONT face=3DArial size=3D2>and using </FONT></DIV> <DIV><FONT face=3DArial size=3D2>0:ad(0,a)/kernel</FONT></DIV> <DIV><FONT face=3DArial size=3D2>instead of </FONT></DIV> <DIV><FONT face=3DArial size=3D2>0:ad(0,a)/boot/loader</FONT></DIV> <DIV><FONT face=3DArial size=3D2>as the boot target ..</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I have cross-loaded the cvsup 16.1e = stuff from a=20 cousin machine</FONT></DIV> <DIV><FONT face=3DArial size=3D2>and an(have) cvsupped to RELENG_4_4=20 ...</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I am about to </FONT></DIV> <DIV><FONT face=3DArial size=3D2>make buildworld</FONT></DIV> <DIV><FONT face=3DArial size=3D2>make buildkernel = -DKERNEL=3DGENERIC</FONT></DIV> <DIV><FONT face=3DArial size=3D2> <DIV><FONT face=3DArial size=3D2>make iinstallkernel = -DKERNEL=3DGENERIC</FONT></DIV> <DIV>reboot</DIV> <DIV>make installworld</DIV> <DIV> </DIV> <DIV>and want to know when or if the bootblock or whatever chunk = is</DIV> <DIV>giving the old wd driver gets fixed/clobbered/overwritten=20 correctly...</DIV> <DIV> </DIV> <DIV>ie will i need to snag the boot again and enter =20 0:ad(0,a)/kernel ???</DIV> <DIV> </DIV> <DIV> </DIV> <DIV>mjt</DIV> <DIV> </DIV></FONT></DIV></BODY></HTML> ------=_NextPart_000_0050_01C14440.02B69380-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005301c143ec$39951920$022aa8c0>