![]() |
|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
![]() |
|
Thread Tools | Display Modes |
|
|||
![]()
Which is the best solution from start bsd.mp?
Is there a configuration file to modify (if it's possible)? Or the preferentially leave only bsd.mp on the root? |
|
|||
![]()
Study Section 14.6 of the FAQ:
http://openbsd.org/faq/faq14.html#Boot386 ..& the manpage for boot.conf(8). |
|
|||
![]()
Thanks.
![]() The solutions is: /etc/boot.conf bsd.mp |
|
|||
![]()
Not quite. The contents of /etc/boot.conf should be:
Code:
set image /bsd.mp |
|
|||
![]()
It's not clear for me.
When i setting the file as before I obtain the desired result which is the real difference between the two notations? |
|
|||
![]()
the openbsd bootloader, which reads /etc/boot.conf, actually allows different ways to point to a certain kernel; for example, you could also have "boot wd0a:/bsd.mp", which will do the same thing (if you boot from wd0a)...
|
|
|||
![]()
Mine's cooler...
![]() Seriously, as I look back at the manpage, I can see that your abbreviated form may work, but most documentation standardizes on "set image <pathname>". If you are really curious, you always have the source to answer the question yourself. |
|
|||
![]()
Oko, did you try?
IMHO none of these are correct. The keyword disable is not listed in boot(8) ![]() You can modify the OpenBSD kernel with the config(8) command, either temporarily or permanently. This man page as well as http://www.openbsd.org/faq/faq5.html#config have an example.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
||||
![]() Quote:
Code:
boot> -c ukc> disable uscanner ukc>quit for boot.conf it occurred to me that above might be possible. This is the quote from the man pages for boot.conf 5. If the file /etc/boot.conf exists on the filesystem boot was loaded from, open and parse it. This file may contain any commands boot accepts at the interactive prompt. Though default settings usually suffice, they can be changed here. boot.conf processing can be skipped by holding down either Control key as boot starts. I have not read things carefully nor I played with it so I am probably wrong. By the way the man pages are from 4.3 current i386 with GENERIC bsd.mp kernel. Thank for the quick response. |
|
||||
![]()
Well, it's not my field.. but
disable dev -> is in the config and boot_config manuals, difference being config for running kernels, BOOT_CONFIG for boot prompts or launched through config. So I would reckon you could use boot.conf to do it, if it boot_config can be accessed or scripted through it. Like all good curiosities, the best way of finding out what works and what doesn't work boils down to read the code or back it up and play with it. general disclaimer: I know the least about OpenBSDs intricate boot details of any system I use -- simply put, it's always worked for me out of the box ^_^.
__________________
My Journal Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo'' someone someday shall type ``supercalifragilisticexpialidocious''. |
|
||||
![]()
If you have used boot -c, and made changes from the UKC console which you wish to make permanent, config -u will pick up those changes.
If I wished to maintain multiple kernel configurations, as Oko is suggesting, then I would have multiple kernels, each configured differently, and select the appropriate kernel at the boot> prompt. |
|
|||
![]()
The craftsman's way:
mv /bsd /bsd.orig && cp /bsd.mp /bsd && reboot ![]() |
|
|||
![]()
I do not reading misc@... I never accidentally copied something into /bsd. That means I'm a lucky fart or I'm a good craftsman, or I use sparc64.
Code:
# uname -m sparc64 # man boot.conf man: no entry for boot.conf in the manual. |
|
||||
![]()
The sparc64 architecture has an equivalent capability:
Quote:
|
|
|||
![]()
Nope, it's not equivalent! Try that remote... :}
The craftsman's way works 'with OpenBSD'... and in case of doing no mistake, it's an very usefull way... for me since years... And finally, if needed you can boot 'bsd.orig' to get your system running with the original GERNERIC kernel. Last edited by sternchenschaf; 23rd June 2008 at 05:14 PM. |
|
||||
![]()
[I'm resurrecting this old thread to discuss "set image" in boot.conf, mentioned above.
As of -current installlation scripting, and therefore for 4.6 this fall, "set image" is no longer considered best practice. The install script sets the appropriate kernel as "/bsd". "set image" is only available for i386/amd64 and not for other architectures. |
|
||||
![]() Quote:
http://archive.openbsd.nu/?ml=openbs...-05&m=10592603 Particularly pay attention to Theo's posts. |
![]() |
Tags |
boot, bsd.mp |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Any Solution for Xorg high CPU usage in Ubuntu 9.04? | Mantazz | Other BSD and UNIX/UNIX-like | 11 | 14th July 2009 06:10 AM |
consider OpenVPN production-grade solution? | nimnod | Off-Topic | 1 | 26th March 2009 12:22 AM |
MYSQL HOW TO START | disappearedng | FreeBSD General | 7 | 18th September 2008 09:48 AM |
Solution: FreeBSD 7 and Sigmatel 9274D codec | ronaldmcdonald9 | FreeBSD General | 0 | 19th July 2008 01:04 AM |
KDE wont start up | dctr | FreeBSD General | 9 | 11th June 2008 05:59 AM |