Sponsored Content
Operating Systems AIX LibC.a usage in /usr/lib/boot/chrp.disk.proto Post 302772865 by Sachin1987 on Wednesday 27th of February 2013 03:10:17 AM
Old 02-27-2013
IBM LibC.a usage in /usr/lib/boot/chrp.disk.proto

Hi,

I am new to C programming, In my protofile we are adding libC.a entry.
I want to know about the usage of libC.a in ptotofile, we are doing this modification before taking bosboot image.

I tried to take a bosboot image without libC.a entry in protofile. I didn't observed any difference in both the cases.

Can someone should brief me the usage of libC.a in /usr/lib/boot/chrp.disk.proto.

Thanks,
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/usr/lib/32/32-> Question

Hello UNIX people. I was just cruising around my UFS and came across the directory /usr/lib/32. This directory continues up many directories (/usr/lib/32/32/32/32->). Each level of 32/ directory seems to be a copy of the previous one. I have been working with UNIX for a little while now, but I... (3 Replies)
Discussion started by: shaggy
3 Replies

2. Shell Programming and Scripting

sh script to traul through /usr/lib/perl5 ...

Hey, Im trying to create a script to create a dir-tree of pod converted to html. so far this is the script: #!/bin/sh cd /usr/lib/perl5 for d in ./* ; do # is it a dir? if ; then # yes! get the basename cd $d ; dir=`basename $d` for f in ./* ; do ... (1 Reply)
Discussion started by: emcb
1 Replies

3. UNIX for Advanced & Expert Users

/usr/lib on a seperate partition

I want to move /usr/lib on a seperate partition. ( is is now all at / ) I know how to copy data and update fstab but... At boot time, the mepis distro already needs stuff from /usr/lib but it is not mounted yet. So i get error before /usr/lib is mounted. Does this mean you cannot move... (4 Replies)
Discussion started by: progressdll
4 Replies

4. AIX

Getting Symbol resolution failed for ../../../lib/libc.a Error

Hi I have compiled a binary on AIX 5.3.0.0 but when i run i get following error Could not load program ACE_wrappers/bin/gperf: Symbol resolution failed for ../../../lib/libc.a(posix_aio.o) because: Symbol _posix_kaio_rdwr (number 2) is not exported from dependent module... (0 Replies)
Discussion started by: khan_nayeem
0 Replies

5. HP-UX

Core Dump in /usr/lib/hpux32/libc.so.1

Hi, I am working on a core dump issue, where the dumps happens in OS library, /usr/lib/hpux32/libc.so.1 and version for my OS is as specified by uname -a is: "HP-UX B.11.23 U ia64". Below is the core dump file. Our program terminated with Signal 6. ... (0 Replies)
Discussion started by: vivek.gkp
0 Replies

6. UNIX for Dummies Questions & Answers

use of /usr/lib/nsr

Hello, I have this folder on my one of the machine but not on other. /usr/lib/nsr can anyone tell me for what this folder is used ? Thanks (2 Replies)
Discussion started by: yatrik007
2 Replies

7. Solaris

/usr/lib/vhost.so missing Solaris 5.10

Hi, i have a solaris 5.10 machine on which i am getting below error while executing cat command ld.so.1: cat: fatal: vhost.so: open failed: No such file or directory Killed it is related to file vhost.so missing Also when i did ldd cat result is as below libc.so.1... (1 Reply)
Discussion started by: Jcpratap
1 Replies

8. Red Hat

./Vega6: /lib/libc.so.6: version `GLIBC_2.15' not found (required by ./Vega6)

Hello, I am trying to run a chess pairing program called Vega Chess on RHEL 6.5 Server $ uname -a Linux CDMA 2.6.32-431.el6.i686 #1 SMP Sun Nov 10 22:20:22 EST 2013 i686 i686 i386 GNU/Linux $ cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.5 (Santiago)This is the way I... (6 Replies)
Discussion started by: Ferocci
6 Replies

9. UNIX for Advanced & Expert Users

/usr/lib/libv12n.so

Hi, I want to use the function "v12n_domain_uuid" on solaris box. The library "libv12n" is present in /usr/lib but i can't locate the header "libv12n.h" anywhere in the box. How do i run the API "v12n_domain_uuid" (4 Replies)
Discussion started by: skyineyes
4 Replies

10. BSD

FreeBSD: /usr/bin/ld not looking in /usr/local/lib

I'm not sure if this is the default behavior for the ld command, but it does not seem to be looking in /usr/local/lib for shared libraries. I was trying to compile the latest version of Kanatest from svn. The autorgen.sh script seems to exit without too much trouble: $ ./autogen.sh checking... (2 Replies)
Discussion started by: AntumDeluge
2 Replies
DISKLABEL(8)						    BSD System Manager's Manual 					      DISKLABEL(8)

NAME
disklabel -- read and write disk pack label SYNOPSIS
disklabel [-ACDFrtv] disk disklabel -e [-CDFIrv] disk disklabel -i [-DFIrv] disk disklabel -R [-DFrv] disk protofile disklabel -w [-DFrv] [-f disktab] disk disktype [packid] disklabel [-NW] disk disklabel -l DESCRIPTION
disklabel can be used to install, examine, or modify the label on a disk drive or pack. When writing the label, it can be used to change the drive identification, the disk partitions on the drive, or to replace a damaged label. The -e, -i, -l, -R, -w, -N, and -W options determine the basic operation. If none are specified the label is displayed. -e Edit the existing label (using EDITOR) and write it back to the disk. If EDITOR is undefined, then vi(1) is used. -i Interactively update the existing label and write it back to the disk. -l Show all known file system types (those that can be specified along a partition within the label) and exit. -R Write (restore) a label by reading it from protofile. The file should be in the same format as the default output. -w Write a standard label for the specified disktype. See disktab(5). -N Disallow writes to the disk sector that contains the label. This is the default state. -W Allow writes to the disk sector that contains the label. This state may not persist if no programs have the disk open. The majority of the rest of the options affect more than one form of the command: -A Read all labels from the disk, including ones deleted with disklabel -D. Implies -r. -C Output the partition offset and size values in <cylinder/head/sector> format. Note this format is always accepted on input with either the -e or -R flags. -D Delete all existing labels (by 1's complementing the magic number) before writing any labels to their default location. Implies -r. If -D is specified without a request to write the label, then existing labels are just deleted. -F Treat disk as a regular file. This suppresses all ioctl(2) calls, and is the default if disk is a regular file. disk is always opened using opendisk(3) even if -F is specified. Implies -r. -I If a label cannot be read from disk request the default one from the kernel. Implies -r. -f disktab Specify the name of a file to use instead of /etc/disktab. -r Read/write the disk directly rather than using ioctl(2) requests on the kernel. When writing a label, the kernel will be told about the label before the label is written and asked to write afterwards. This is the historic behaviour and can be supressed by specifying -F. -t Format the output as a disktab(5) entry. -v Be verbose about the operations being done, in particular the disk sectors being read and written. Specifying -v more than once will increase the verbosity. On systems that expect to have disks with MBR partitions (see fdisk(8)) disklabel will find, and update if requested, labels in the first 8k of type 169 (NetBSD) MBR labels and within the first 8k of the physical disk. On other systems disklabel will only look at the start of the disk. The offset at which the labels are written is also system dependent. disklabel will detect byteswapped labels, but currently cannot display them. Previous versions of disklabel could update the bootstrap code on some architectures. This functionality has been subsumed by installboot(8). FILES
/etc/disktab EXIT STATUS
The exit status of disklabel is set to indicate any errors or warnings. The values used are: 0 The disklabel utility has completed successfully. 1 A fatal error has occurred, such as unknown options passed on the command line, or writing the disklabel failed. 4 An I/O error of some sort occurred. 101..n One or more warnings occured while reading the disklabel. Subtract 100 to get the number of warnings detected. EXAMPLES
disklabel sd0 Display the in-core label for sd0 as obtained via /dev/rsd0c. disklabel -i -r sd0 Read the on-disk label for sd0, edit it using the built-in interactive editor and reinstall in-core as well as on-disk. disklabel -i -I sd0 As previous, but don't fail if there was no label on the disk yet; provide some default values instead. disklabel -e -I sd0 As previous, only edit using $EDITOR disklabel -w -r /dev/rsd0c sd2212 foo Create a label for sd0 based on information for ``sd2212'' found in /etc/disktab, using foo as the disk pack label. If you do not have an entry for your disk in /etc/disktab, you can use this style to put an initial label onto a new disk. Then dump the label to a file (using disklabel sd0 > protofile), editing the file, and replacing the label with disklabel -R sd0 protofile. disklabel -R sd0 mylabel Restore the on-disk and in-core label for sd0 from information in mylabel. DIAGNOSTICS
The kernel device drivers will not allow the size of a disk partition to be decreased or the offset of a partition to be changed while it is open. Some device drivers create a label containing only a single large partition if a disk is unlabeled; thus, the label must be written to the ``a'' partition of the disk while it is open. This sometimes requires the desired label to be set in two steps, the first one creating at least one other partition, and the second setting the label on the new partition while shrinking the ``a'' partition. SEE ALSO
opendisk(3), disklabel(5), disktab(5), dkctl(8), fdisk(8), gpt(8), installboot(8), mbrlabel(8), mscdlabel(8) BUGS
The disklabel structure stored on disk cannot support partitions/disks greater than 2TB. Please use gpt(8) and dkctl(8) to manage partitions and disks larger than 2TB. If the disk partition is not specified in the disk name (i.e., xy0 instead of /dev/rxy0c), disklabel will construct the full pathname of the disk and use the ``d'' partition on i386, hpcmips, or arc, and the ``c'' partition on all others. On the sparc, sparc64, sun2, and sun3 NetBSD systems, the size of each partition must be a multiple of the number of sectors per cylinder (i.e., each partition must be an integer number of cylinders), or the boot ROMs will declare the label invalid and fail to boot the system. In addition, the -r option should never be used on a sparc, sparc64, sun2, or sun3 system boot disk - the NetBSD kernel translates the NetBSD disk label into a SunOS compatible format (which is required by the boot PROMs) when it writes the label. Using the -r flag causes disklabel to write directly to disk, and bypass the format translation. This will result in a disk label that the PROMs will not recognize, and that therefore cannot be booted from. BSD
July 25, 2011 BSD
All times are GMT -4. The time now is 11:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy