Re: GEOM + GRUB = ??
Wesley Morgan wrote: Trying to install a new version of GRUB not having much success. I'm wondering if GEOM is interacting with it in some strange way. I am fairly certain grub reads the partitions itself, but this would be through the geom layer would it not? The port might need to be marked broken for 5.0, or someone with geom know-how submit a patch to the grub folks (if that is really the problem). Can anyone else verify this? I'm using grub with a device-map file that used to work just fine. GEOM is merely a byte array layout manager interface layer, of the type I first described BSD needing in about 1995 (according to Google). As such, GEOM is just an abstraction, and just for FreeBSD. The GRUB stuff does not use GEOM, because GEOM is an abstraction that lives in FreeBSD only. GRUB reads the data directly, itself. To do this, it has to have some knowledge of how to at least get at the code in the boot1/boot2 case (try booting one of the files in /boot instead of /kernel), and it needs to understand the FS layout for where the files are stored, and/or use a sector map. It will need to be updated for UFS2, when that becomes an issue. You need to provide a little more information about your failure to PHK or Bruce Evans, who will be able to better tell you how to deal with the FreeBSD boot code. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM + GRUB = ??
On Wed, 4 Dec 2002, Terry Lambert wrote: The GRUB stuff does not use GEOM, because GEOM is an abstraction that lives in FreeBSD only. GRUB reads the data directly, itself. To do this, it has to have some knowledge of how to at least get at the code in the boot1/boot2 case (try booting one of the files in /boot instead of /kernel), and it needs to understand the FS layout for where the files are stored, and/or use a sector map. It will need to be updated for UFS2, when that becomes an issue. It's not the booting that is a problem. That was working fine until I had to wipe out the MBR when my disklabel was chomped last week.. It's the grub command-line shell/installer that won't work now (admittedly I have not updated my grub boot blocks in a while either, so it may be a pre-GEOM issue). Would not accessing /dev/adX with open() or so go through GEOM? -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM + GRUB = ??
On Wed, Dec 04, 2002 at 02:56:10PM -0500, Wesley Morgan wrote: On Wed, 4 Dec 2002, Terry Lambert wrote: The GRUB stuff does not use GEOM, because GEOM is an abstraction that lives in FreeBSD only. GRUB reads the data directly, itself. To do this, it has to have some knowledge of how to at least get at the code in the boot1/boot2 case (try booting one of the files in /boot instead of /kernel), and it needs to understand the FS layout for where the files are stored, and/or use a sector map. It will need to be updated for UFS2, when that becomes an issue. It's not the booting that is a problem. That was working fine until I had to wipe out the MBR when my disklabel was chomped last week.. It's the grub command-line shell/installer that won't work now (admittedly I have not updated my grub boot blocks in a while either, so it may be a pre-GEOM issue). Would not accessing /dev/adX with open() or so go through GEOM? Actually I was having problems with the installer in -STABLE also, so it may also be something with the port itself. - Christian -- http://www.unixpages.org[EMAIL PROTECTED] GPG Pub-Key: www.unixpages.org/cbrueffer.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D GPG Key ID : 0xA0ED982D msg48098/pgp0.pgp Description: PGP signature
Re: GEOM + GRUB = ??
Wesley Morgan wrote: It's not the booting that is a problem. That was working fine until I had to wipe out the MBR when my disklabel was chomped last week.. It's the grub command-line shell/installer that won't work now (admittedly I have not updated my grub boot blocks in a while either, so it may be a pre-GEOM issue). Would not accessing /dev/adX with open() or so go through GEOM? OK, I misunderstood; I thought you were saying it's a boot probelm, when it's actually a write the MBR problem. Yes, GEOM breaks a number of things that used to work in that area; you probably need to beat on Poul (there was a seperate report of a port that broke because it could not write the disklabel, that was posted yesterday -- diskcheckd, I believe). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
