02-03-2010
Quote:
Originally Posted by
DukeNuke2
boot from dvd and change the permissions back...
My guess is he does not have the boot disks. I certainly don't have my OSX boot disks or DVD.
If not, another option might be to grab the required binaries from the Apple Darwin Open Source download site.
I would upload some of what he needs, but I use an older PowerPC iMac, not an Intel box.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I just set up an ftp server with Red Hat 5.2. I am doing the work, I'm baby stepping, but it seems like every step I get stuck. Currently, I'm trying to set up a crontab job, but I'm getting the following message: /bin/sh: /usr/bin/vi: No such file or directory. I see that vi exists in /bin/vi,... (3 Replies)
Discussion started by: kwalter
3 Replies
2. Solaris
Hi All,
I have changed the shell of the root accidentally to /sbin/bash :mad:
How do I change that? :(
To change that I need to go to ok prompt I think, and there I need to mount the root file system in order to make changes to the respective file.
Can any one please suggest how do I do... (4 Replies)
Discussion started by: pintu_asim
4 Replies
3. UNIX for Dummies Questions & Answers
Hi All,
Can somebody tell me the difference between /bin, /usr/bin, /sbin ?
Thanx in advance,
Saneesh Joseph (3 Replies)
Discussion started by: saneeshjose
3 Replies
4. Solaris
Hello Guruz,
Relay bad condition :mad:
Some has changed the permission to 777 recursively for /usr/bin directory by mistake. Now all the permission looks to be 777 on /usr/bin
Hence I am so many system related errors as 1 show below.
When I am trying to change the password, I am getting... (5 Replies)
Discussion started by: bullz26
5 Replies
5. Solaris
Hi all,
below is the problem details:
ora10g@CNORACLE1>which ld
/usr/ucb/ld
ora10g@CNORACLE1>cd /usr/ccs/bin
ora10g@CNORACLE1>ln -s /usr/ucb/ld ld
ln: cannot create ld: File exists
ora10g@CNORACLE1>
how to link it to /usr/ccs/bin? (6 Replies)
Discussion started by: SmartAntz
6 Replies
6. OS X (Apple)
Q1. I understand that /usr/local/bin means I can install/uninstall stuff in here and have any chance of messing up my original system files or effecting any other users. I created this directory myself.
But what about the directory I didn't create, namely /Users/m/bin? How is that directory... (1 Reply)
Discussion started by: michellepace
1 Replies
7. Shell Programming and Scripting
Hi All,
I have to work in the late nights some times for server maintenance and in a hurry to complete I am accidentally changing ownership or permission of directories :(
which have similar names ( /var in root and var of some other directory ).:confused:
Can some one suggest me with the... (1 Reply)
Discussion started by: shiek.kaleem
1 Replies
8. Red Hat
Hi All,
Accidentally changed ownership of /var directory as root :eek: thinking that I am changing ownership of var directory in other location in the file system:D.Now unable to SSH into the server:(.
By gods grace I was able to regain the access again as server was in control of me at that... (5 Replies)
Discussion started by: shiek.kaleem
5 Replies
9. BSD
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
LEARN ABOUT HPUX
bootconf
bootconf(4) Kernel Interfaces Manual bootconf(4)
NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)