8 More Discussions You Might Find Interesting
1. Red Hat
I want to implement an FTP server on RHEL 5.8 system where the users can upload files either from RHEL or Windows systems but am not able to copy files to it from a browser session. For eg.
URL - ftp://10.101.17.80/incoming
I want to copy files from to it from my Windows... (3 Replies)
Discussion started by: RHCE
3 Replies
2. HP-UX
When we executed a lpadmin command, the following error was output.
# lpadmin -phsaprinter -v/home/hoge/lpfile -mrmodel -ocmrcmodel
-osmrsmodel -ormhsaprinter -orphsaprinter
lpadmin: can't access file "/home/hoge/lpfile"
/home/hoge/lpfile is the file other user made.
The... (1 Reply)
Discussion started by: madhurtripathi
1 Replies
3. OS X (Apple)
Hi,
I have a problem controlling devices on my iMac.
The internal DVD is no longer working. Therefore I have bought a new external DVD, but some programs use the internal by default (Boot Camp for instance).
Since iMac, runs UNIX beneath the Mac OS X, I hope to do some magic, by unmounting... (1 Reply)
Discussion started by: ASL123
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I have a problem controlling devices on my iMac.
The internal DVD is no longer working. Therefore I have bought a new external DVD, but some programs use the internal by default.
Since iMac, runs UNIX beneath the Mac OS X, I hope to do some magic, by unmounting the internal DVD and put... (0 Replies)
Discussion started by: ASL123
0 Replies
5. UNIX for Dummies Questions & Answers
Hey, I was wondering how I can write/edit files on my FreeBSD hdd from windows XP. I specifically need to fix a change I made to /boot/defaults/loader.conf that made it impossible to boot into my FreeBSD hdd. It's a simple fix, but since I can't boot into FreeBSD, I have to fix it from my Windows... (2 Replies)
Discussion started by: Xandor
2 Replies
6. HP-UX
Hi,
Currently, we are doing make recovery in our servers but dds tape drive of 1 of our servers is not working. I suppose to use external dds tape drive but the problem is that there is no slot from the server for the scsi type external dds device. Is it possible to use drives from other... (5 Replies)
Discussion started by: Tris
5 Replies
7. Shell Programming and Scripting
Hello All
I am need of amke recover tape for solaris.Could anybody tell me how do i create a make recovery tape for solaris.I am on sun-solaris 2.8
regards
Hrishy (2 Replies)
Discussion started by: xiamin
2 Replies
8. HP-UX
A customer called me and stated that when they created a make recovery tape for their hp-ux 9000/770, it wiped out three of their volume groups from the lvmtab, fstab, /dev directory(all associated files). I didn't believe them until I conducted a tech assist. I restored their system by recreating... (3 Replies)
Discussion started by: spawarrior
3 Replies
re-preinstall(1M) System Administration Commands re-preinstall(1M)
NAME
re-preinstall - installs the JumpStart software on a system
SYNOPSIS
cdrom-mnt-pt/Solaris_XX/Tools/Boot/usr/sbin/install.d/re-preinstall [-m Solaris_boot_dir] [-k platform_name] target-slice
DESCRIPTION
re-preinstall installs the JumpStart software (preinstall boot image) on a system, so you can power-on the system and have it automatically
install the Solaris software (perform a JumpStart installation on the system). When you turn on a re-preinstalled system, the system looks
for the JumpStart software on the system's default boot disk. All new SPARC systems have the JumpStart software already preinstalled. The
XX in Solaris_XX is the version number of the Solaris release being used.
You can use the re-preinstall command in several ways. The most common way is to run re-preinstall on a system to install the JumpStart
software on its own default boot disk. This is useful if you want to restore a system to its original factory conditions. (See the first
procedure described in EXAMPLES.)
You can also run re-preinstall on a system to install JumpStart software on any attached disk (non-boot disk). After you install the Jump-
Start software on a disk, you can move the disk to a different system and perform a JumpStart installation on the different system. (See
the second procedure described in EXAMPLES.)
re-preinstall creates a standard file system on the specified target-slice (usually slice 0), and re-preinstall makes sure there is enough
space on the target-slice for the JumpStart software. If sufficient space is not available, re-preinstall fails with the following message:
re-preinstall: target-slice too small xx Megabytes required
You can use the format(1M) command to create sufficient space on the target-slice for the JumpStart software.
OPTIONS
The following options are supported:
-k platform_name Platform name of the system that will use the disk with the JumpStart software. The default is the platform name of
the system running re-preinstall. (Use the uname(1) command (-i option) to determine a system's platform name.)
-m Solaris_boot_dir Absolute path to the Solaris_XX/Tools/Boot subdirectory of a mounted Solaris CD or a Solaris CD copied to disk that
re-preinstall uses to install the JumpStart software. The default is root (/), which is where the Solaris CD is
mounted in single-user mode.
OPERANDS
The following operands are supported:
target-slice Device name of the disk slice where the JumpStart software will be installed (usually slice 0), for example, c0t3d0s0.
EXAMPLES
Example 1: Installing the JumpStart Software on a System's Own Default Boot Disk
The following procedure installs the JumpStart software on a system's own default boot disk:
1. From the ok prompt, boot the system from the Solaris media CD or DVD in single-user mode:
ok boot cdrom -s
2. The following command installs the Jumpstart software on the System default boot disk, c0t0d0s0 on a Solaris 9 system:
example# /usr/sbin/install.d/re-preinstall c0t0d0s1
3. Reboot the slice:
example# reboot disk:b
Example 2: Installing the JumpStart Software on a System's Attached (non-boot) Disk
The following procedure installs the JumpStart software on a system's attached (non-boot) disk:
1. Mount the Solaris CD or DVD if vold(1M) is not running or CD or DVD is not mounted.
2. Use the format(1M) command to determine the target-slice where JumpStart will be installed.
3. Use the uname(1) command (-i option) to determine the platform name of the system that will use the re-preinstalled disk
4. Run re-preinstall with the -m Solaris_boot_dir option if the Solaris CD or DVD is not mounted on /cdrom.
The following command installs the JumpStart software on the system's attached disk for a system with a Sun4u kernel architecture, and
it uses the Solaris CD or DVD mounted with vold(1M) on a Solaris 9 system:
example# /cdrom/cdrom/s1/usr/bin/install.d/re-preinstall -m
/cdrom/cdrom/s1 -k sun4u c0t2d0s0
EXIT STATUS
The following exit values are returned:
0 Successful completion.
1 An error has occurred.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcdrom (Solaris CD, |
| |SPARC Platform Edition) |
+-----------------------------+-----------------------------+
SEE ALSO
uname(1), eeprom(1M), format(1M), mount(1M), vold(1M), attributes(5)
Solaris 10 Installation Guide: Basic Installations
SunOS 5.10 9 Apr 2002 re-preinstall(1M)