I agree. I almost always make /boot a separate filesystem. I was just trying to clear up the difference between directories that must exist on / and those that are optional.
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Hi gurus
Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value
Is it /dev/kmem file or something... (1 Reply)
supermicro(dual core) server getting rebooted after "decompressing the kernel;booting the kernel" message comes.
I tried giving acpi=off to the kernel command line but same problem.It shows everything ok and no problem with memory and processors and power supplies.Wt could be the reason?
It has... (1 Reply)
Hello there:
I know that exist a procedure to convert an OS using 32bits kernel to 64 bits kernel. But, exist a procedure to convert an OS using 64bits to 32 bits kernel?
Please help me.
Regards. (2 Replies)
> how the sendmsg and recvmsg calls will know which kernel module to use (SCTP, RTP etc.) internally(kernel mapping: how kernel handle socket call) (1 Reply)
Hi All,
Is there a max number of slabs that can be used per kernel module? I'm having a tough time finding out that kind of information, but the array 'node_zonelists' (mmzone.h) has a size of 5. I just want to avoid buffer overruns and other bad stuff.
Cheers,
Brendan (4 Replies)
hi all!
i have developed a mechanism in system.c to count how many times each kernel call is called. The results are held in an array in system.c . What i want to do is to create a new kernel call which will print this array. I need help in passing the array from system.c to the new kernel call. ... (5 Replies)
ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before?
I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system.
Please Help... (2 Replies)
Again same issue with new kernel 2.6.18.1
root@world # iptables -L
modprobe: QM_MODULES: Function not implemented
modprobe: QM_MODULES: Function not implemented
modprobe: Can't locate module ip_tables
iptables v1.2.8: can't initialize iptables table `filter': iptables who? (do you... (10 Replies)
GPTBOOT(8) BSD System Manager's Manual GPTBOOT(8)NAME
gptboot -- GPT bootcode for UFS on BIOS-based computers
DESCRIPTION
gptboot is used on BIOS-based computers to boot from a UFS partition on a GPT-partitioned disk. gptboot is installed in a freebsd-boot par-
tition with gpart(8).
IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptboot only boots from tables with 128 partitions or less.
PARTITION ATTRIBUTES
gptboot checks and manages several attributes of GPT UFS partitions.
bootme Attempt to boot from this partition. If more than one partition has the bootme attribute set, gptboot will attempt to boot each
one until successful.
bootonce Attempt to boot from this partition only one time. Setting this attribute with gpart(8) automatically also sets the bootme
attribute. Multiple partitions may have the bootonce and bootme attributes set.
bootfailed The bootfailed attribute marks partitions that had the bootonce attribute set, but failed to boot. This attribute is managed by
the system. See BOOTING and POST-BOOT ACTIONS below for details.
USAGE
For normal usage, the user does not have to set or manage any of the partition attributes. gptboot will boot from the first UFS partition
found.
The bootonce attribute can be used for testing an upgraded operating system on an already-working computer. The existing system partition is
left untouched, and the new version of the operating system to be tested is installed on another partition. The bootonce attribute is set on
that new test partition. The next boot is attempted from the test partition. Success or failure will be shown in the system log files.
After a successful boot of the test partition, a user script can check the logs and change the bootme attributes so the test partition
becomes the new system partition. Because the bootonce attribute is cleared after an attempted boot, a failed boot will not leave the system
attempting to boot from a partition that will never succeed. Instead, the system will boot from the older, known-working operating system
that has not been modified. If the bootme attribute is set on any partitions, booting will be attempted from them first. If no partitions
with bootme attributes are found, booting will be attempted from the first UFS partition found.
BOOTING
gptboot first reads the partition table. All freebsd-ufs partitions with only the bootonce attribute set, indicating a failed boot, are set
to bootfailed. gptboot then scans through all of the freebsd-ufs partitions. Boot behavior depends on the combination of bootme and
bootonce attributes set on those partitions.
bootonce + bootme Highest priority: booting is attempted from each of the freebsd-ufs partitions with both of these attributes. On each
partition, the bootme attribute is removed and the boot attempted.
bootme Middle priority: booting is attempted from each of the freebsd-ufs partitions with the bootme attribute.
If neither bootonce nor bootme attributes are found on any partitions, booting is attempted from the first freebsd-ufs partition on the disk.
POST-BOOT ACTIONS
The startup script /etc/rc.d/gptboot checks the attributes of freebsd-ufs partitions on all GPT disks. Partitions with the bootfailed
attribute generate a ``boot from X failed'' system log message. Partitions with only the bootonce attribute, indicating a partition that
successfully booted, generate a ``boot from X succeeded'' system log message. The bootfailed attributes are cleared from all the partitions.
The bootonce attribute is cleared from the partition that successfully booted. There is normally only one of these.
FILES
/boot/gptboot bootcode binary
/boot.config parameters for the boot blocks (optional)
EXAMPLES
gptboot is installed in a freebsd-boot partition, usually the first partition on the disk. A ``protective MBR'' (see gpart(8)) is typically
installed in combination with gptboot.
Install gptboot on the ada0 drive:
gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0
gptboot can also be installed without the PMBR:
gpart bootcode -p /boot/gptboot -i 1 ada0
Set the bootme attribute for partition 2:
gpart set -a bootme -i 2 ada0
Set the bootonce attribute for partition 2, automatically also setting the bootme attribute:
gpart set -a bootonce -i 2 ada0
SEE ALSO boot.config(5), rc.conf(5), boot(8), gpart(8)HISTORY
gptboot appeared in FreeBSD 7.1.
AUTHORS
This manual page written by Warren Block <wblock@FreeBSD.org>.
BSD February 5, 2014 BSD