Date: Wed, 22 Dec 2004 17:31:30 +0900 From: Pyun YongHyeon <yongari@kt-is.co.kr> To: "R. Tyler Ballance" <tyler@tamu.edu> Cc: freebsd-sparc64@freebsd.org Subject: Re: sysinstall dead in -CURRENT? Message-ID: <20041222083130.GA8947@kt-is.co.kr> In-Reply-To: <1103702026.2542.50.camel@localhost.localdomain> References: <20041221025023.GB4468@kt-is.co.kr> <200412210643.iBL6hHEK085224@smtp-relay.tamu.edu> <20041221071417.GA5301@kt-is.co.kr> <20041222034846.GA8065@kt-is.co.kr> <1103702026.2542.50.camel@localhost.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 22, 2004 at 01:53:46AM -0600, R. Tyler Ballance wrote:
> > Ok, here is a better workaround. This patch should also fix another
> > error of sysinstall. At present, sysinstall presents SCSI CDROM
> > to available disks in Fdisk/Label menu. It seems that the root
> > cause is GEOM's disk handling.("kern.disk" always shows SCSI CDROM
> > and it is used as an argument to Open_Disk())
> >
> > So I added an additioanl check for CDROM in sysinstall instead of
> > touching libdisk. Please let me know how it goes. And I'd like
> > to know it doesn't break i386 sysinstall too. Due to lack of i386 with
> > SCSI CDROM I couldn't verify the patch.
>
> Yep, your patch does work, I think it's a valid workaround that would
> help if worked into -CURRENT, I cannot imagine anywhere else where
Thanks, committed.
> addressing the SCSI CD-Rom like you would a regular HD would get you
> into trouble, any other libdisk-caused errors?
>
Users would be confused if CDROM device appear on Fdisk/Label memu.
> -R. Tyler Ballance
--
Regards,
Pyun YongHyeon
http://www.kr.freebsd.org/~yongari | yongari@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041222083130.GA8947>