Sponsored Content
Operating Systems Linux Linux system from the ground up. Post 302199010 by G_Morgan on Sunday 25th of May 2008 04:25:08 PM
Old 05-25-2008
Linux system from the ground up.

Does anyone know any good tutorials or books which basically start you off by creating a partition, sticking a Linux kernel on there and then booting it to launch some random binary? Then incrementally adds to it until you have something like a full system?

Essentially I want to see how a Unixy system fits together from boot onwards. I know that init gets the system up and running then launches the login shell but I'd like to bypass this and have a look at building my own primitive replacements in interesting cases just to see how it all slots together.

I've ran through LFS but it tells you how to get things working without really touching on how it all works. It doesn't give you any insight into how the kernel decides what it is doing after boot up. How the init system actually works, etc.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Executing scripts in back ground

Hi, Test1.ksh #! /bin/ksh for i in $* do #echo "$i" ksh test2.ksh $i & done test2.ksh #! /bin/ksh sleep 5s echo "From Test 1 ==> $1" exit 0; I am executing as follows: ksh test1.ksh a b c (10 Replies)
Discussion started by: risshanth
10 Replies

2. Shell Programming and Scripting

Run script in back ground

I have a script "a" running in background. From script "a" i will kick off script "b" which will also be in background. Is this possible. And actually what i want is, In script "b" when i do ps -ef, script "a" should not be seen. Current "a" script ---- --- ---- nohup b exit current... (1 Reply)
Discussion started by: vasuarjula
1 Replies

3. AIX

Help with back ground scripts...

I have a user that runs a menu driven application, is there a way to see what scripts this application is executing in the back ground? OS=AIX 4.3 (1 Reply)
Discussion started by: mangolinux
1 Replies

4. Shell Programming and Scripting

prevent multiple tail in back ground

Dears i have a scrip run in unix that need to use the tail -f command, as below: DATE=`date '+%m%d%y'` tail -f /var/messages | grep "start" >> /export/logs/start_${DATE}.out but the problem that the tail -f will be stop and working in the background in then end of the day (23:59:59)... (0 Replies)
Discussion started by: thehero
0 Replies

5. AIX

Accessing files on AIX system from Linux system

I have a following requirement in production system 1 : LINUX User: abcd system 2: AIX (it is hosting a production DB) Requirement user abcd from system 1 should have read access on archive log files created by DB on system 2. The log files are created with permissions 540 by user ora ,... (2 Replies)
Discussion started by: amitnm1106
2 Replies

6. Programming

Linux/Solaris System Administrator to become a Linux/Solaris System Programmer?

Hi all What is the qualification required by Linux/Solaris System Administrator to become a Linux/Solaris System Programmer as to gain complete knowledge on computers. Thanks (1 Reply)
Discussion started by: Tlogine
1 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
All times are GMT -4. The time now is 05:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy