Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Why bind to LiveCD /proc before building initramfs ? Post 303001574 by hicksd8 on Monday 7th of August 2017 02:04:06 PM
Old 08-07-2017
Technically, the 'initramfs' on the 'Live CD' should contain ALL common drivers and load modules needed for commonly found hardware and therefore should run on your box (unless you loaded third-party driver(s) at install time). Therefore, once up and running, the O/S recovery function can probe your hardware and check that the required drivers are installed and uncorrupted. The recovery function should/probably/hopefully only check for the really required drivers for your platform.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Cannot log on to FreeBSD LiveCD

Hi, I just download FreeBSD LiveCD and burn it to the CDROM (Because I want to learn UNIX). But when I boot the computer from the CDROM, it display the username and password. I type "root" and the password blank. But it does not allow me to login. I try many user name and password that I guest but... (3 Replies)
Discussion started by: 012633023
3 Replies

2. Debian

change initramfs by hand?

What's the correct way to change the initramfs file that's used during boot? I know that it's a gzipped cpio archive, but when I gunzip, extract, re-archive (without changing any files), and gzip, then the result is that the system does not boot any more. And I even set the cpio archive type. ... (18 Replies)
Discussion started by: frankie06
18 Replies

3. Linux

initramfs on 2.4 kernel

Is there a patch available to support initramfs on the 2.4 kernel? We can't upgrade to 2.6 for legacy purposes. All I found on google were early references to how initramfs is better than the 2.4 initrd. Thanks much! (0 Replies)
Discussion started by: amoeba
0 Replies

4. UNIX for Dummies Questions & Answers

_/proc/stat vs /proc/uptime

Hi, I am trying to calculate the CPU Usage by getting the difference between the idle time reported by /proc/stat at 2 different intervals. Now the 4th entry in the first line of /proc/stat will give me the 'idle time'. But I also came across /proc/uptime that gives me 2 entries : 1st one as the... (0 Replies)
Discussion started by: coderd
0 Replies

5. UNIX for Dummies Questions & Answers

LiveCD help

hey, I am build an operating system but i cant seem to get it to boot. I am using GRUB as the boot loader, but I'm not sure if I have all the files need, on the CD, to load the operating system. So can anyone tell me what files I need in order for GRUB to load my OS. P.S. The OS is neither... (1 Reply)
Discussion started by: neur0n
1 Replies

6. Debian

Only have initramfs now...

Long story short, I had a ps3 with both Lenny and Sid repositories. Knowing this is a bad idea and that Lenny is being deprecated I decided I wanted to move everything to Sid. I changed my repos and ran apt-get-update, upgrade, dist-upgrade. Had one warning during the apt-get upgrade that... (0 Replies)
Discussion started by: Azrael
0 Replies
DEVICE_ADD_CHILD(9)					   BSD Kernel Developer's Manual				       DEVICE_ADD_CHILD(9)

NAME
device_add_child, device_add_child_ordered -- add a new device as a child of an existing device SYNOPSIS
#include <sys/param.h> #include <sys/bus.h> device_t device_add_child(device_t dev, const char *name, int unit); device_t device_add_child_ordered(device_t dev, int order, const char *name, int unit); DESCRIPTION
Create a new child device of dev. The name and unit arguments specify the name and unit number of the device. If the name is unknown then the caller should pass NULL. If the unit is unknown then the caller should pass -1 and the system will choose the next available unit num- ber. The name of the device is used to determine which drivers might be appropriate for the device. If a name is specified then only drivers of that name are probed. If no name is given then all drivers for the owning bus are probed. In any event, only the name of the device is stored so that one may safely unload/load a driver bound to that name. This allows busses which can uniquely identify device instances (such as PCI) to allow each driver to check each device instance for a match. For busses which rely on supplied probe hints where only one driver can have a chance of probing the device, the driver name should be speci- fied as the device name. Normally unit numbers will be chosen automatically by the system and a unit number of -1 should be given. When a specific unit number is desired (e.g. for wiring a particular piece of hardware to a pre-configured unit number), that unit should be passed. If the specified unit number is already allocated, a new unit will be allocated and a diagnostic message printed. If the devices attached to a bus must be probed in a specific order (e.g. for the ISA bus some devices are sensitive to failed probe attempts of unrelated drivers and therefore must be probed first), the order argument of device_add_child_ordered() should be used to specify a par- tial ordering. The new device will be added before any existing device with a greater order. If device_add_child() is used, then the new child will be added as if its order was zero. When adding a device in the context of DEVICE_IDENTIFY(9) routine, the device_find_child(9) routine should be used to ensure that the device has not already been added to the tree. Because the device name and devclass_t are associated at probe time (not child addition time), pre- vious instances of the driver (say in a module that was later unloaded) may have already added the instance. Authors of bus drivers must likewise be careful when adding children when they are loaded and unloaded to avoid duplication of children devices. Identify routines should use BUS_ADD_CHILD(9) instead of device_add_child(9). RETURN VALUES
The new device if successful, NULL otherwise. SEE ALSO
BUS_ADD_CHILD(9), device(9), device_find_child(9), DEVICE_IDENTIFY(9) AUTHORS
This manual page was written by Doug Rabson. BSD
September 12, 2006 BSD
All times are GMT -4. The time now is 12:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy