I'm trying to build a live image using livecd-tools (livecd-creator), but this time i'd like to reuse the /root/anaconda-ks.cfg.
System: Fedora 3.16.7-200.fc20.x86_64
The building starts, the download begins, but it fails with networking.
Quote:
...
Installier: iwl6050-firmware ##################### [988/991]
Installier: mailcap ##################### [989/991]
Installier: iwl2030-firmware ##################### [990/991]
Installier: libertas-usb8388-firmware ##################### [991/991]
Installier: iwl135-firmware ##################### [992/991]
Installier: ivtv-firmware ##################### [993/991]
No '/dev/log' or 'logger' included for syslog logging
No '/dev/log' or 'logger' included for syslog logging
2072 blocks
Adding service 'mdns' to default zone.
success
Hinweis: Anfrage wird weitergeleitet an »systemctl enable NetworkManager.service«.
Hinweis: Anfrage wird weitergeleitet an »systemctl disable sshd.service«.
rm '/etc/systemd/system/multi-user.target.wants/sshd.service'
Error creating Live CD : No --device specified with network kickstart command
...
MAIN.ks
I started to experiment with the anaconda file, anyhow, this is the network section:
Any adivces?
Thank you in advance
Any idea what this error meant? I got this error "Anaconda Exception: parserError: xmlParseMemory() failed" while performing kickstart. My linux distro is a redhat4.
Thank You. (2 Replies)
i create ks.cfg for automatic install for centos 5.2 it's work perfectky for cutom install linux package.
and i want to install another program with shell scripts (assume test.tar include in DVD linux custom package)** single dvd include linux os and test.tar
sample
#!/bin/bash... (1 Reply)
hi
Howto configure Ralus at /usr/local/etc/be-agent.cfg on freeBSD 7.0 for Backup Exec 9.1?
I've tried the following:
# cat /usr/local/etc/be-agent.cfg
name bsd.domain
export / as root
export /usr as usr
export /var as var
export /tmp as tmp
force_address 10.10.1.50
tell... (0 Replies)
i have automated installation of my proprietory linux.. using PXE. it all goes well. but after complete installation, while using the admin interface.. i am facing display problems.
is it due to package dependencies.?
or i have to write post script in anaconda-ks.cfg file???
can some one tell... (10 Replies)
Hi All,
I was trying to create pxelinux.cfg/default file in a script that I use for creating backup of bootimage.
cat 2>${BACKUB_BOOTIMAGE_ERRINFO} >${pxelinux_cfg_file} <<EOF
prompt 1
timeout 0
display boot.msg
label restore
kernel kernel
append root=/dev/nfs... (0 Replies)
hi folks
I have issue in printing pdf while using ERP application, it's using pasta utility to print pdf. If i print from command line its successful while when ERP user give print command the printer doesnot print anything rather it gives error which is as follows
ESP Ghostscript 815.01:... (12 Replies)
I have been looking everywhere for a solution and it seems as though awk may do the trick. I am very much a newbie in the awk scripting world but it seems to appear one of the best text parsing tools from what I've read on this forum.
Scenario:
I have about 50 cisco config files randomly... (7 Replies)
cleanwork /saswork removes sas orphanded processes in the saswork directory. Subdirectories under sasem are sas94, sas92 and sasworks .
I am getting the following error messages:
1.
'/usr/bin/sudo -S apt-get update <~/opt/SiM/pos/ps/db_auth.cfg... (4 Replies)
Discussion started by: dellanicholson
4 Replies
LEARN ABOUT DEBIAN
upslug2
UPSLUG2(8) System Manager's Manual UPSLUG2(8)NAME
upslug2 - utility to upgrade the firmware of a NSLU2 via the network
SYNOPSIS
upslug2 [options]
DESCRIPTION
upslug2 is a command line program intended to allow the upgrade the firmware of a Linksys NSLU2 (Network Storage Link for USB 2.0 Disk
Drives) to new or different versions. When a NSLU2 in the local network is put in upgrade mode, upslug2 can connect to it and upload a new
firmware.
upslug2 will accept a full firmware image but it can also upgrade the flash from individual files holding the kernel, ramdisk and root
filesystem. upslug2 provides status information during the upgrade process and verifies the written image after the upgrade.
OPTIONS -C, --Complete-reprogram
Reprogram the complete flash, including the RedBoot boot loader and the SysConf partition holding configuration information. Using
this option may result in the NSLU2 becoming permanently unusable! By default, upslug2 will not touch these two partitions since
this allows flashing a new firmware if an uploaded firmware does not work. This is not possible if RedBoot itself is damaged. Use
with caution.
-d, --device
The network device on the host machine connected to the network on which the NSLU2 is located. (Default: eth0).
-e, --endian
The endianness of the files to be uploaded. upslug2 will usually detected the endianness automatically but this option can be used
to force byte swapping to occur. This option accepts three values, separated by comma: endianness of kernel, data and RedBoot FIS
directory. Valid values are l (little endian), p (pdp endian) and b (big endian). (Default: ,b,b)
-f, --from
The MAC address of the host system.
-h, --help
Show summary of options.
-i, --image
The complete flash image to use.
-j, --rootfs
A root filesystem, usually of type jffs.
-k, --kernel
A compressed kernel zImage image.
-n, --no-reboot
Do not reboot after upgrade
-p, --payload
FIS directory payload. There are about 140 Kb in the last block (between the FIS dir and the trailer at the end) which can be used
for data.
-r, --ramdisk
A compressed ramdisk image.
-R, --ram-payload
A ram paylod (replaced ramdisk). (FIXME: if it replaced the ramdisk, why cannot you just use the -r option? What's the difference)
-t, --target
The MAC address of the NSLU2 to upgrade. Without this option, upslug2 will only perform an upgrade if there is just one NSLU2 in
upgrade mode.
-U, --no-verify
Do not verify the image, only upgrade.
-v, --verify
Do not write to flash, only verify the image.
Options to specify firmware information
The following options should be used when individual kernel, ramdisk and root filesystem files are specified rather than a complete
firmware image.
-E, --extra-version
Extra version information, a 2 byte value. (Default: 0x90f7)
-F, --firmware-version
The firmware version, a 2 byte value. (Default: 0x2329)
-P, --product-id
The product ID, a 2 byte value. (Default: 1)
-T, --protocol-id
The protocol ID, a 2 byte value. (Default: 0)
USING UPSLUG2
In order to use upslug2 the NSLU2 which is to be upgraded has to be put in upgrade mode:
1. Disconnect any disks and/or devices from the USB ports.
2. Power off the NSLU2
3. Press and hold the reset button (accessible through the small hole on the back just above the power input).
4. Press and release the power button to power on the NSLU2.
5. Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset but-
ton.
6. The NSLU2 ready/status LED will flash alternately red/green (there is a 1 second delay before the first green). The NSLU2 is now in
upgrade mode.
If you decide not to flash the image the NSLU2 can be rebooted by disconnecting the power. If the ready/status LED does not turn green
after step four it will remain red for several seconds then flash amber. This happens if you do not release the reset button in time - pull
the power, reconnect it and repeat from the second step.
Once the NSLU2 is in upgrade mode it will remain in this state until either the power is connected or a new image has been flashed. If the
flash fails the NSLU2 will (eventually) return to upgrade mode
EXAMPLES
The most common use of upslug2 is the following:
upslug2 --image NSLU2_V23R63.bin
This specifies a complete firmware image which will be written to flash.
Alternatively, kernel, ramdisk and root filesystem can be specified individually:
upslug2 -k nslu2-zImage -r ramdisk -j root.jffs
In this case, the options -E, -F, -P and -T should typically be specified as well.
By default, upslug2 will search for the NSLU2 on the network on your eth0 network interface. If the network is on a different interface,
you can easily specify it:
upslug2 -d eth1 --image NSLU2_V23R63.bin
If there are potentially more than one NSLU2 in your network which may be in upgrade mode, you can specify its MAC address:
upslug2 -t 00:11:85:12:34:56 --image NSLU2_V23R63.bin
SEE ALSO slugimage(1)AUTHOR
John Bowler <jbowler@acm.org>
January 2006 UPSLUG2(8)