Welcome Guest ( Log In | Click here to Register a free account now! )
Welcome to Bleeping Computer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.| Important Announcement: We have two terrific contests running on the site that I wanted all our members and guests to know about. The first contest is the HP Magic Giveaway, which is underway as of November 28th. More information can be found at this topic, which will be updated very soon with further information. The second contests, is for the chance to win two Seagate FreeAgent external hard drives. More information about this contest can be found here. These are both amazing contests and I suggest everyone submit an entry for them. - BleepingComputer Management |
![]() ![]() |
Jun 18 2008, 03:54 AM
Post
#1
|
|
|
New Member ![]() Group: Members Posts: 1 Joined: 18-June 08 Member No.: 216,976 |
Also looking for the best way to boot from another system's drive over ethernet...those machines "lan devices" are listed as bootable devices but won't boot. Basically I have an old HP9000 750/66 tower that has a corrupted /etc/passwd file...hpux hell. This makes it impossible to even boot to a single user mode. I don't know of any other way to selectively replace that file or edit that file with the options I have available booting to the "scsi.6.0 isl" level. I guess an option I will try is to build a system recovery tape from another system and boot from that tape, attempt to get to single user, and then attempt to mount the offending disk with the corrupted /etc/passwd file. I would like to use one of the other systems I have on the "lan" instead (I have a HP720, another PA7000 based system thats has virtually the same processor and unix configuration) . A convenience factor. What shows on the list of bootable devices is simply the "lan" device IP address. I need to figure out how to get one of the other systems drives....ie. instead of something like the scsi.6.0 entry on the problem systems list, a unique name for those drives on one of the other working systems on my little network, with a bootable image. I wait your opinions on: support @ infobitedesign.com support @ dizib.com This post has been edited by Matthew1977: Jun 18 2008, 03:54 AM |
|
|
|
![]() ![]() |
| Lo-Fi Version | Time is now: 4th December 2008 - 02:13 AM |