10 More Discussions You Might Find Interesting
1. Solaris
Hi,
How to to make a slice and define as ufs from zpool? Please advice me.
Thanks.
---------- Post updated at 01:53 AM ---------- Previous update was at 12:24 AM ----------
Before slice:
Part Tag Flag Cylinders Size Blocks
0 root wm 0 ... (2 Replies)
Discussion started by: mzainal
2 Replies
2. Solaris
we have a ZFS file system that was created as a pool of just one disk (raid on a SAN) when this was created it was done as a whole disk, and so EFI label.
now we want to mount this file system into an LDOM.
my understanding of how ldom's and disk works this is that we can only do this as a... (1 Reply)
Discussion started by: robsonde
1 Replies
3. Solaris
Part Tag Flag Cylinders Size Blocks
0 root wm 259 - 2666 4.70GB (2408/0/0) 9863168
1 swap wu 3 - 258 512.00MB (256/0/0) 1048576
2 backup wm 0 - 4091 7.99GB (4092/0/0) 16760832
3... (4 Replies)
Discussion started by: chidori
4 Replies
4. Solaris
is there a command that would zero swap slice? I found these instructions: but hoping there is some swap-specific command (3 Replies)
Discussion started by: orange47
3 Replies
5. Linux
Hi all
I am testing backupPC as a backup solution for machines, as far as i knew, backuppc cannot combine more than storage from different slices so it have to be in one slice my question is, what is the easy way to offer a virtual logical drive expanded/expandable to backuppc, i mean i want to... (1 Reply)
Discussion started by: XP_2600
1 Replies
6. IP Networking
I new to linux and am setting up a slice server. I actually made it to installing Apache but some how I messed up the ip tables. I cant access the server by sftp or putty. Im using the web interface at slice. I am logged in as a super user but cant do certain funtions. I guess i need to be logged... (0 Replies)
Discussion started by: DigitalExtreme
0 Replies
7. Solaris
Hey guys,
This is how I originally had my drive setup... This is on a solaris 10 box
***BEFORE***
Current Disk = c0t1d0
Current partition table (original):
Total disk cylinders available: 7506 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks... (2 Replies)
Discussion started by: kingdbag
2 Replies
8. AIX
if the system pegs at 100%, can I reserve .2cpu to allow for logins and such? the oracle rman/other activities take up some resources on occassion ... 3.8 procs for the system and .2 reserved?
I'm not sure how to tackle this issue ... is this a good use for WLM?
any thoughts? (1 Reply)
Discussion started by: A Stewart
1 Replies
9. UNIX for Advanced & Expert Users
Can any one Explain the artichture of Slice on SOLARIS PLATFORM.
OR else
where can i found artical on these topic.
akram shaik OCA
akram_tri_a@yahoo.com (2 Replies)
Discussion started by: smdakram
2 Replies
10. Filesystems, Disks and Memory
Hi,
I'd like to add two new disk (mirrored each other) in a machine still on line.
The machine is mirrored with SDS. the idea is to add two new disk and mirroring them in order to add a new mount point like "/produit" with only half of the new disk.
who could send me exemples or tell me how to... (1 Reply)
Discussion started by: guillaume35
1 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)