04-08-2011
Is an extra line on bootup really that important to you? These things are loaded on boot to make the system more flexible and really aren't a drain on resources; you could do more harm than good digging deep enough to remove it that completely.
10 More Discussions You Might Find Interesting
1. Red Hat
We have a Red Hat linux server running on IBM x445 hardware. There are external disks in an IBM EXP300 disk enclosure. The system is running RAID 5. One of the four IBM disks (73.4 GB 10k FRU 06P5760) has become faulty. The system is still up and running OK because of the RAID. In that same EXP300... (3 Replies)
Discussion started by: pdudley
3 Replies
2. Solaris
Hi.
I need to move a 5 disk RAID5 array from a SE3310 box to a different SE3310 array. After installing the disks in the "new" StorEdge device, I "would like" ;) to be able have access to the data which is on the RAID.
Essentially, the quesion is, how can this be done? :confused:
I checked... (5 Replies)
Discussion started by: alexs77
5 Replies
3. Red Hat
I have an HP blade with Qlogic HBA's connected to an EVA8000. I have downloaded the latest multipath.conf from HP's website. The drive presented to the server appears to be configured and working except the output of "multipath -l" shows for all paths. What is causing this output?
mpath0... (2 Replies)
Discussion started by: manzier
2 Replies
4. Red Hat
Hi,
I had a doubt regarding device mapper notations and their corresponding LVM volumes.
I have configured a volume group with two logical volumes in it as root and swap.
The entries in the /etc/fstab file show the dm notations namely,
/dev/mapper/VolGroup00-LogVol01... (2 Replies)
Discussion started by: kanna_geekworkz
2 Replies
5. Solaris
I've just installed Sol 10 Update 9 on a Sun 4140 server and have a RAID 1 configuration (2 136 Gb drives) for the OS and have created a RAID 5 array (6 136 GB) drives. When i log into the system I am unable to see the RAID 5 disks at all. I've tried using the devfsadm command but no luck and... (9 Replies)
Discussion started by: goose25
9 Replies
6. AIX
Hello,
I have a scsi pci x raid controller card on which I had created a disk array of 3 disks
when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk )
suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies
7. Red Hat
Good morning
Recently we needed to change the password from a redhat 6.5 system that no one knew the root password.
Starting the system with the init=/bin/bash method took us to the following scenario:
system_vg active with only root_lv and tmpfs mounted.
our entries at fstab are like... (1 Reply)
Discussion started by: Ikaro0
1 Replies
8. Solaris
Dear All ,
Pl find the below command ,
# raidctl -l
Controller: 1
Volume:c1t0d0
Disk: 0.0.0
Disk: 0.1.0
Disk: 0.3.0
#
raidctl -l c1t0d0
Volume Size Stripe Status Cache RAID
Sub Size ... (10 Replies)
Discussion started by: jegaraman
10 Replies
9. UNIX for Advanced & Expert Users
Currently I am using this laborious command
lvdisplay | awk '/LV Path/ {p=$3} /LV Name/ {n=$3} /VG Name/ {v=$3} /Block device/ {d=$3; sub(".*:", "/dev/dm-", d); printf "%s\t%s\t%s\n", p, "/dev/mapper/"v"-"n, d}'
Would like to know if there is any shorter method to get this mapping of... (2 Replies)
Discussion started by: royalibrahim
2 Replies
10. Ubuntu
I suddenly don't see my folders into /mnt/md0.
What can be reason?
mdadm --detail /dev/md*
/dev/md0:
Version : 1.2
Creation Time : Fri Jan 18 09:54:27 2019
Raid Level : raid1
Array Size : 1953383488 (1862.89 GiB 2000.26 GB)
Used Dev Size : 1953383488 (1862.89 GiB... (8 Replies)
Discussion started by: tomislav91
8 Replies
LEARN ABOUT FREEBSD
loader.4th
LOADER.4TH(8) BSD System Manager's Manual LOADER.4TH(8)
NAME
loader.4th -- loader.conf processing tools
DESCRIPTION
The file that goes by the name of loader.4th is a set of commands designed to manipulate loader.conf(5) files. The default /boot/loader.rc
includes loader.4th and uses one of its commands to automatically read and process the standard loader.conf(5) files. Other commands exists
to help the user specify alternate configurations.
The commands of loader.4th by themselves are not enough for most uses. Please refer to the examples below for the most common situations,
and to loader(8) for additional commands.
Before using any of the commands provided in loader.4th, it must be included through the command:
include loader.4th
This line is present in the default /boot/loader.rc file, so it is not needed (and should not be re-issued) in a normal setup.
The commands provided by it are:
boot
boot kernelname [...]
boot directory [...]
boot -flag ... Boot as specified by the loader.conf(5) files read.
Depending on the arguments passed, it can override boot flags and either the kernel name or the search path for
kernel and modules.
boot-conf
boot-conf kernelname [...]
boot-conf directory [...]
boot-conf -flag ... Works like boot described above, but instead of booting immediately, uses autoboot, so it can be stopped.
start Reads /boot/defaults/loader.conf, all other loader.conf(5) files specified in it, then loads the desired kernel
and modules (if not already loaded). After which you can use the boot or autoboot commmands or simply exit
(provided autoboot_delay is not set to NO) to boot the system. start is the command used in the default
/boot/loader.rc file (see loader(8)).
initialize Initialize the support library so commands can be used without executing start first. Like start, it reads
/boot/defaults/loader.conf and all other loader.conf(5) files specified in it (but does not load kernel or
modules). Returns a flag on the stack to indicate if any configuration files were successfully loaded.
read-conf filename Reads and processes a loader.conf(5) file. Does not proceed to boot.
enable-module module Enables the loading of module.
disable-module module Disables the loading of module.
toggle-module module Toggles the loading of module on and off.
show-module module Shows the information gathered in the loader.conf(5) files about the module module.
retry Used inside loader.conf(5) files to specify the action after a module loading fails.
ignore Used inside loader.conf(5) files to specify the action after a module loading fails.
try-include file [file ...]
Process script files if they exist. Each file, in turn, is completely read into memory, and then each of its
lines is passed to the command line interpreter. If any error is returned by the interpreter, the try-include
command aborts immediately, without reading any other files, and silently returns without error.
FILES
/boot/loader The loader(8).
/boot/loader.4th loader.4th itself.
/boot/loader.rc loader(8) bootstrapping script.
/boot/defaults/loader.conf
File loaded by the start command.
EXAMPLES
Standard /boot/loader.rc:
include /boot/loader.4th
start
Load a different kernel with the standard configuration:
set kernel="kernel.old"
unload
boot-conf
Read an additional configuration file and then proceed to boot:
unload
read-conf /boot/special.conf
boot-conf
Disable the loading of the splash screen module and bitmap and then proceed to boot:
unload
disable-module splash_bmp
disable-module bitmap
boot-conf
SEE ALSO
loader.conf(5), loader(8)
HISTORY
The loader.4th set of commands first appeared in FreeBSD 3.2.
AUTHORS
The loader.4th set of commands was written by Daniel C. Sobral <dcs@FreeBSD.org>.
BUGS
A British espionage series.
BSD
November 13, 2013 BSD