12-18-2002
A unix admin suggested that if I do not want to lose my data then I can just move my root filesystem to the /export/home slice. I didnt really have anything I needed in export home so what I did was a ufsdump/restore from s0 (root slice) to s7 (/export/home). I then edited the vfstab in the /export/home/etc directory on s7 to point the root filesystem to s7. Then, made a bootblock on s7 with installboot.
My question is, how do I tell the OS to boot off of slice 7 instead of slice 0? I am running Solaris 8 intel.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Anyone know if SUN recommends users to install the root parition on 1 single slice or break out the /var , /etc, /opt etc on separate slices?
What if i only have a single hdd that is only 2 GB (1 Reply)
Discussion started by: owls
1 Replies
2. UNIX for Dummies Questions & Answers
How do I create new disk slices taking space from an existing slice? Right now I have slice 6 (/usr) with 16G. I'd like to create slices 5 (/opt) and 7 (/export/home) and steal space from slice 6.
Thanks (3 Replies)
Discussion started by: kmgrady01
3 Replies
3. Filesystems, Disks and Memory
Can you have a second primary slice on a second hdd?
I know that primary slices are defined in the mbr, but where are all the sub partitions defined at?
From the OBSD installation FAQ:
What exactly is in the PBR? (0 Replies)
Discussion started by: Derrek
0 Replies
4. UNIX for Dummies Questions & Answers
I have a Sun box running Solaris 9.
My root disk was slices too small when it was installed and I am now at 99% capacity for my root partition.
Is it possible, and if so how?, to increase the size of slice 0 and decrease the size of slice 7??
Thanks!
Current partition table... (6 Replies)
Discussion started by: FredSmith
6 Replies
5. Solaris
Good morning to one and all :-) Thank god its Friday, as its bee na rubbish week for me !
So, a quick question. Disks ! Ive got a few local disks, and a few SAN disks used on my solaris server. Whats confusing me, and Im not sure if there's an issue at the SAN end, or my end, regarding the... (3 Replies)
Discussion started by: sbk1972
3 Replies
6. Solaris
Hi all
I'm having difficulty setting up a proper disk structure on a 72GB HDD. The drive was previously part of a zfs pool. The zpool has ben destroyed and now I want to use the disk in a raid 5 array. I need to partition the disk accordingly though.
This is what the partition table currently... (7 Replies)
Discussion started by: notreallyhere
7 Replies
7. Solaris
how do you get start and end sector of a UFS slice? (2 Replies)
Discussion started by: orange47
2 Replies
8. BSD
I need to shrink a UFS slice with NetBSD on SPARC. seems the only way is backup+reformat. can someone please give me exact commands for that? presumably backup is file-by-file instead of sector-by-sector, but how to preserve permissions/dates/attributes.. ? thanks. (0 Replies)
Discussion started by: orange47
0 Replies
9. Solaris
Hi Admins,
Server is sparc solaris 9
I am new into solaris with little experiemce with SVM.
/dev/dsk/c3t0d1s4 /u05
/dev/dsk/c3t0d1s3 /u02
/dev/dsk/c3t0d1s5 /u11
There are 3 file system created on slices of disk c3t0d1. Now i want to scrap all the slices and... (5 Replies)
Discussion started by: newsol
5 Replies
10. UNIX for Dummies Questions & Answers
Hello,
I am using solaris 10 x86. my root and backup slices is having same memory 10 GB and same cylinders numbers . My root and backup cylinders ends at same cylinder number 1031. so for creating a new slice i am giving starting cylinder from 1302 and this is giving me error as "out of range" .... (2 Replies)
Discussion started by: bhargav90
2 Replies
LEARN ABOUT XFREE86
systemd.slice
SYSTEMD.SLICE(5) systemd.slice SYSTEMD.SLICE(5)
NAME
systemd.slice - Slice unit configuration
SYNOPSIS
slice.slice
DESCRIPTION
A unit configuration file whose name ends in ".slice" encodes information about a slice unit. A slice unit is a concept for hierarchically
managing resources of a group of processes. This management is performed by creating a node in the Linux Control Group (cgroup) tree. Units
that manage processes (primarily scope and service units) may be assigned to a specific slice. For each slice, certain resource limits may
be set that apply to all processes of all units contained in that slice. Slices are organized hierarchically in a tree. The name of the
slice encodes the location in the tree. The name consists of a dash-separated series of names, which describes the path to the slice from
the root slice. The root slice is named -.slice. Example: foo-bar.slice is a slice that is located within foo.slice, which in turn is
located in the root slice -.slice.
Note that slice units cannot be templated, nor is possible to add multiple names to a slice unit by creating additional symlinks to its
unit file.
By default, service and scope units are placed in system.slice, virtual machines and containers registered with systemd-machined(1) are
found in machine.slice, and user sessions handled by systemd-logind(1) in user.slice. See systemd.special(5) for more information.
See systemd.unit(5) for the common options of all unit configuration files. The common configuration items are configured in the generic
[Unit] and [Install] sections. The slice specific configuration options are configured in the [Slice] section. Currently, only generic
resource control settings as described in systemd.resource-control(5) are allowed.
See the New Control Group Interfaces[1] for an introduction on how to make use of slice units from programs.
IMPLICIT DEPENDENCIES
The following dependencies are implicitly added:
o Slice units automatically gain dependencies of type After= and Requires= on their immediate parent slice unit.
DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set:
o Slice units will automatically have dependencies of type Conflicts= and Before= on shutdown.target. These ensure that slice units are
removed prior to system shutdown. Only slice units involved with late system shutdown should disable DefaultDependencies= option.
SEE ALSO
systemd(1), systemd.unit(5), systemd.resource-control(5), systemd.service(5), systemd.scope(5), systemd.special(7), systemd.directives(7)
NOTES
1. New Control Group Interfaces
https://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/
systemd 237 SYSTEMD.SLICE(5)