Ways to analyse root disk slice Post: 302297579

9 More Discussions You Might Find Interesting

1. Solaris

mirroring the boot slice (slice 8) on x86

Hi there I am about to mirror a Solaris 10 x86 box (SunFire X4100) onto a secondary disk using svm (current system is one disk). My question is this, on X86 boxes there is a slice 8 defined as boot partition (and also a slice 9, dunno what its used for tho). Do I need to mirror this boot slice...

2. Solaris

Move root filesystem to other slice

Hi, df -h display: # df -h Filesystem size used avail capacity Mounted on /dev/dsk/c1t0d0s0 9.8G 8.1G 1.7G 84% / /proc 0K 0K 0K 0% /proc mnttab 0K 0K 0K 0% /etc/mnttab fd 0K 0K 0K 0% /dev/fd swap 1.0G 152K 1.0G 1% /var/run swap 1.1G 24M 1.0G 3% /tmp /dev/dsk/c1t0d0s3 57G 13G 43G 24%...

3. UNIX for Dummies Questions & Answers

Does formatting slice 2 (backup) destroy disk geometry?

I am a new Unix Sys Admin who is learning mostly from books with minimal classroom training (ie: no certificates, training is largely hands-on, conducted at work). I work with Solaris 8 through 10, and with some fairly outdated hardware. In my work restoring old workstations I have been instructed...

4. Shell Programming and Scripting

Looking for help with script to assign all disk space to slice#0 on multiple disks of varying sizes

Hi Folks, I am trying to make a script to assign all diskspace to slice 0, on multiple sized disks. Since the disks are new they may need to be labelled also to avoid the error: Cannot get disk geometry Below is my code struggling with logic which doesn't seem to be producing the desired...

5. Solaris

label a slice on disk erorr

Hi there, I am trying to do root volume mirroring on SunFire V210 server. I have two disks in it.First one is c1t0do and second one is c1t1do. Both disks already have partitions in them so I am deleting the partitions of second disk(c1t1do) using format command and selecting cylinder start 0...

6. Solaris

Lost Root Password on VXVM Encapsulated Root Disk

Hi All Hope it's okay to post on this sub-forum, couldn't find a better place I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under...

7. Solaris

ZFS - whole disk Vs slice

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...

8. Solaris

Trouble creating a disk partition slice (EFI)

Hi all, I am using SPARC Solaris 11.1 with EFI labelled disks. I am new to ZFS file systems and slightly stuck when trying to create a partition (slice) on one of my LUNs. EFI labels use sectors and blocks and I am not sure how exactly it works. From here I can try and create a...

9. Solaris

ZFS Slice disk

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 ...

LEARN ABOUT MINIX

dpkg-checkbuilddeps

dpkg-checkbuilddeps(1)						    dpkg suite						    dpkg-checkbuilddeps(1)

NAME

       dpkg-checkbuilddeps - check build dependencies and conflicts

SYNOPSIS

       dpkg-checkbuilddeps [option...]	[control-file]

DESCRIPTION

       This  program checks the installed packages in the system against the build dependencies and build conflicts listed in the control file. If
       any are not met, it displays them and exits with a nonzero return code.

       By default, debian/control is read, but an alternate control filename may be specified on the command line.

OPTIONS

       --admindir=dir
	      Change the location of the dpkg database (since dpkg 1.14.0).  The default location is /var/lib/dpkg.

       -A     Ignore Build-Depends-Arch and Build-Conflicts-Arch lines (since dpkg 1.16.4).  Use when only arch-indep packages will be	built,	or
	      combine with -B when only a source package is to be built.

       -B     Ignore  Build-Depends-Indep  and Build-Conflicts-Indep lines. Use when only arch-dep packages will be built, or combine with -A when
	      only a source package is to be built.

       -I     Ignore built-in build depends and conflicts (since dpkg 1.18.2).	These are implicit dependencies that are  usually  required  on  a
	      specific distribution, the so called Build-Essential package set.

       -d build-depends-string

       -c build-conflicts-string
	      Use the given build dependencies/conflicts instead of those contained in the debian/control file (since dpkg 1.14.17).

       -a arch
	      Check  build  dependencies/conflicts  assuming  that  the  package  described  in the control file is to be built for the given host
	      architecture instead of the architecture of the current system (since dpkg 1.16.2).

       -P profile[,...]
	      Check build dependencies/conflicts assuming that the package described in the control file is  to  be  built  for  the  given  build
	      profile(s) (since dpkg 1.17.2).  The argument is a comma-separated list of profile names.

       -?, --help
	      Show the usage message and exit.

       --version
	      Show the version and exit.

ENVIRONMENT

       DEB_BUILD_PROFILES
	      If  set,	it will be used as the active build profile(s) for the package being built. It is a space separated list of profile names.
	      Overridden by the -P option.

1.19.0.5							    2018-04-16						    dpkg-checkbuilddeps(1)