Slackware Interactive Boot Scripts 12.0.0-6 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Slackware Interactive Boot Scripts 12.0.0-6 (Default branch)
# 1  
Old 01-15-2008
Slackware Interactive Boot Scripts 12.0.0-6 (Default branch)

ImageslakbootIBS (Slackware Interactive Boot Scripts)is an enhanced set of replacement boot scripts forthe Slackware Linux distribution. It includes aset of control and dispatch tools for configuringand booting with colorized interactive scripts.The new boot process allows the operator to selector skip start-up components in realtime. Itfacilitates debugging of startup problems andallows operators to maintain a common baseline tosupport several local configurations or multipleservers with a single set of scripts.License: Free for non-commercial useChanges:
A new release of the emit (shell or GUI) interactive screen prompts and rendering engine was included. The rc.M and rc.inet2 scripts were upgraded to add better hotplug support with cleaner HAL/udev daemon startup logic. The new boot time interactive scripts can now support a wider range of customized Slackware configurations.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Slackware

Sbin/agetty loop Prevents Boot of Slackware 12.1 Fileserver

HI everyone, Nice to meet you all. I recently rebooted Slackware 12.1 running on a Dell PowerEdge 2400. after 240 days of continuous run-time, and discovered it gets stuck in a sbin/agetty loop. We were rebooting because trying to mount root in webmin broke a bunch of things. Couldn't even get... (3 Replies)
Discussion started by: 5pac3m0nk3y
3 Replies

2. Shell Programming and Scripting

Bash -c interactive scripts

i have to run the following script through a pipe: script.sh: #!/bin/bash echo "Hello World" echo -e "The \033 here's how its currently being run: bash -c "$(cat script.sh)" This is an interactive script. the problem is, when i run it this way, if you go to another terminal and... (4 Replies)
Discussion started by: SkySmart
4 Replies

3. Shell Programming and Scripting

Identifying interactive scripts

so for the purposes of this thread, interactive scripts are shell scripts that prompts for a response from a user and then waits for the user to enter a response before proceeding. now, from my understanding of this, the one common string i can expect to find in all interactive scripts is some... (1 Reply)
Discussion started by: SkySmart
1 Replies

4. Shell Programming and Scripting

Bash interactive scripts

i have a script that contains: script.sh #!/bin/bash echo -e "\t\t\t0. Exit" echo -e "\t\t\t1. Help" echo -e "\t\t\t2. Notes" echo -e "\t\t\t3. Classes" echo "${newline}" echo -n -e "\t Please enter option number : " read Type case $Type in 1) clear ... (1 Reply)
Discussion started by: SkySmart
1 Replies

5. Shell Programming and Scripting

interactive scripts with user input that includes quotes

I'm writing a basic ldapsearch script that prompts the user for their search criteria. The input they're being asked for is the search filter portion of the ldapsearch command. This string must be quoted. When the script executes the command it returns nothing. If I hard code a search filter it... (1 Reply)
Discussion started by: donniemac
1 Replies

6. Red Hat

Interactive PXE Boot Menu

I have been asked to modify our PXE server such that there will be only one entry in the pxelinux.cfg/default file, where the same kernel and initrd.img will be used regardless of what operating system is to be installed, and the user will type in the path to the kickstart file that will be used. ... (7 Replies)
Discussion started by: ceb
7 Replies

7. Shell Programming and Scripting

Interactive scripts for Oracle

Hello friends, I am a ORACLE user, we have some internal database file, lets say "demo.config" and an internal tool to patch this file....lets call that tool as "dbfixer". We have 100's-1000's of such files "demo.config" which need to get patched by the tool. So we need to write a script ...... (1 Reply)
Discussion started by: Newbie456267uni
1 Replies

8. Shell Programming and Scripting

Automating interactive scripts

Hi all, I am trying to write a program that will automate interactive scripts that use 'pkgadd'. Easily enough I can use 'pkgask' and a response file for most of what I want to do, but unfortunately there are parts of some pkg installations that are configured to only take input from /dev/tty!!... (2 Replies)
Discussion started by: bookoo
2 Replies
Login or Register to Ask a Question
pdc(1M) 																   pdc(1M)

NAME
pdc - processor-dependent code (firmware) DESCRIPTION
is the firmware that implements all processor-dependent functionality, including initialization and self-test of the processor. Upon com- pletion, it loads and transfers control to the initial system loader (isl(1M)). Firmware behavior varies somewhat, depending on the hard- ware as described below. To load from an external medium, must know the particular device on which resides. Typically the device is identified by the Primary Boot Path that is maintained by in Stable Storage. A path specification is an I/O subsystem mnemonic that varies according to hardware model. When the processor is reset after initialization and self-test complete, reads the Console Path from Stable Storage, and attempts to ini- tialize the console device. If the initialization fails, attempts to find and initialize a console device. Algorithms used to find a con- sole device are model-dependent. then announces the Primary Boot, Alternate Boot, and Console Paths. If (see isl(1M)) is enabled, provides a 10-second delay, during which time the operator can override the sequence by typing any character on the console. If the operator does not interrupt this process, initializes and reads from the Primary Boot Path. On models that support autosearch, if this path is not valid and (see isl(1M)) is enabled, then searches to find a bootable medium. If allowed to complete, a list of potentially bootable devices is displayed, labeled with abbreviated path identifiers (P0, P1, etc). A simple menu is then displayed where the user can: o Boot a specific device, using the abbreviated path identifier, or the full mnemonic. o Start a device search where the contents are searched for IPL images (note the first search only identified devices and did not check the contents). o Enter the boot administration level. o Exit the menu and return to autobooting o Get help on choices If the sequence is unsuccessful, overridden by the operator, or not enabled in the first place, interactively prompts the operator for the Boot Path to use. Any required path components that are not supplied default to zero. The Primary Boot, Alternate Boot, and Console Paths as well as and enable can be modified via SEE ALSO
boot(1M), isl(1M). PA-RISC Systems Only pdc(1M)