Bug 172413
| Summary: | Boot "loader" should accept additional parameters | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Zbigniew <zbigniew2011> |
| Component: | kern | Assignee: | Andrey V. Elsukov <ae> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
On 07.10.2012 01:41, Zbigniew wrote: > Installed recently FreeBSD 9.0 - and I've got a problem: while > booting, "loader" somehow gets incorrect currdevice value, stopping > boot process. It does get "disk1s6a", but it should be "disk1s7a" > ("lsdev" reports such number). I can boot system, when I set currdev > "manually", then type "boot". Of course, loader won't read its config > files, when not having access to root directory. Having multiple > OS-es on HDD, I'm using GRUB for booting. My FreeBSD section looks > like: Hi, it seems your problem is similar to one described in the http://www.freebsd.org/cgi/query-pr.cgi?pr=158358 Can you try the loader(8) binary from the FreeBSD 10.0-CURRENT? You can get it from a snapshot: https://pub.allbsd.org/FreeBSD-snapshots/ -- WBR, Andrey V. Elsukov 2012/10/7, Andrey V. Elsukov <bu7cher@yandex.ru>: > it seems your problem is similar to one described in the > http://www.freebsd.org/cgi/query-pr.cgi?pr=158358 > > Can you try the loader(8) binary from the FreeBSD 10.0-CURRENT? > You can get it from a snapshot: > https://pub.allbsd.org/FreeBSD-snapshots/ Thanks, it seems so! Downloaded the binary package base.txz from https://pub.allbsd.org/FreeBSD-snapshots/i386-i386/10.0-HEAD-20121006-JPSNAP/ftp/base.txz - then extracted "loader", replaced with it the former one, and yes - the system can be booted quite normally, I can see the logo/menu etc. Nevertheless I suppose, that ability to add boot-time parameters would be helpful as "workaround" in such cases. -- regards, Zbigniew Responsible Changed From-To: freebsd-bugs->ae Take it. State Changed From-To: open->closed Fixed in head/ and the fix merged to stable/9 with r243243. Thanks! |
Installed recently FreeBSD 9.0 - and I've got a problem: while booting, "loader" somehow gets incorrect currdevice value, stopping boot process. It does get "disk1s6a", but it should be "disk1s7a" ("lsdev" reports such number). I can boot system, when I set currdev "manually", then type "boot". Of course, loader won't read its config files, when not having access to root directory. Having multiple OS-es on HDD, I'm using GRUB for booting. My FreeBSD section looks like: root (hd0,5,a) kernel /boot/loader No, I can't change "root partition" - the solution would be to allow to pass the boot parameters to loader, like this: kernel /boot/loader currdev=disk1s7a I mean: each variable, that can be later examined by "show", should be possible to be changed in such GRUBs command-line, by passing sequence of such parameters, separated by spaces. Such ability is present since years in Linux - no problem there with passing boot parameters - why not in FreeBSD? BTW: I would to mention here, that at least two essential utilities - I mean boot0cfg and dumpon - (but maybe more of them) have "artifically" imposed a limit to handle at most fourth partition. It's an obvious nonsense, since I've got by now FreeBSD installed - and working - on "logical partition" 6 created inside "physical partition" 4. Why the most essential tools are ignoring the fact, that nowadays we're able to have - say - 20 partitions, not just four? The man page for dumpon is signed "12 may 1995", which suggests to me, that this utility has been left untouched since that time. Maybe 17 years ago keeping the limit "four partitions" was reasonable, but today HDDs of terabyte capacity aren't anything extraordinary. Time, and the work conditions, have changed - therefore such changes should be reflected in such basic tools, needed for proper disk partitioning and setting the boot process. I would to add, that on the very same partition I had a few days ago NetBSD installation, which had no problem with the partition number whatsoever. I've replaced Net- with FreeBSD, and since the very start such strange problems "we don't like your partitions schema". Almost twenty years later it's still not possible to install FreeBSD onto chosen partition the straight way, and then to run the system without additional "adventures". Being very essential thing, this really needs a fix! How-To-Repeat: Just by booting FreeBSD from some "unusul" partition (the one with "high" number)