02-12-2014
Boot a rescue CD. With Redhat the install CD can be used. I assume must distros are the same.
10 More Discussions You Might Find Interesting
1. Linux
hello
i just uninstall fedora core 4 and would like to remove the GRUB from my system. i try to use windows xp startup disk and tryout the fixmbr command. however the system warn me that my computer do not have a proper mbr and performing this action may make all partition in my harddisk... (5 Replies)
Discussion started by: wsc
5 Replies
2. Red Hat
hai,
i have a problem. i installed RHEL 4. The system got hanged during installation.so now i want to install Windows XP. when i boot from cd i am getting grub> prompt. so i want to remove grub from MBR.
And i am having 128MB RAM.whether it is recommended for installation for RHEL4.
Give me... (7 Replies)
Discussion started by: chinnappa
7 Replies
3. Linux
in dual os grub will ask like this (linux 9 (red hat))
linux(bigmem)
linux(smallmem)
dos
so i want that grub will ask like this
dos
linux(bigmem)
linux(smallmem)
how to do this (8 Replies)
Discussion started by: seshumohan
8 Replies
4. UNIX for Dummies Questions & Answers
Hi, I installed solaris 10 a few weeks ago. It was working fine during the past two weeks. However, now when I start to load to the drive, I get this problem:
The BIOS screen comes up like normal, then screen goes blank and a message "Grub loading stage 2" flashes real quick then the computer... (1 Reply)
Discussion started by: moesays
1 Replies
5. Shell Programming and Scripting
Hi Friends.
I am new to scripting now i want to change the root password using the script with standard password.
which is the easy scripting to learn for the beginner, Thanks in advance. (2 Replies)
Discussion started by: kurva
2 Replies
6. Red Hat
i have installed rhel5 quite many times.......
when i see grub.conf after installation, somtimes "kernel /boot/vmlinuz-2.6.18-8.el5 ro=LABEL=/ rhgb quiet" will be there or "kernel /boot/vmlinuz-2.6.18-8.el5 ro=LABEL=/1 rhgb quiet" will be there................
what is the significance of label=/... (1 Reply)
Discussion started by: sagar_md
1 Replies
7. UNIX for Dummies Questions & Answers
Hi
We send *.csv with sensitive data to our customers. Our customers open those files with Excel.
A new requirement is that we password protect those CSV files.
I thought to pack them with ZIP and assign a password to the archive.
But Solaris 10 can't encrypt ZIP files.
$ zip -P... (12 Replies)
Discussion started by: slashdotweenie
12 Replies
8. Red Hat
Hi,
Can we specify which grub.conf to use while installing grub on RHEL.
We are working on application which requires different grub configurations needed, depending on certain criteria we need to update grub with correct grub.conf.
Can we use grub-install for this purpose? (4 Replies)
Discussion started by: successlin
4 Replies
9. UNIX for Dummies Questions & Answers
can someone please explain me the difference between these two files:
"/boot/grub/grub.conf" and "/etc/grub.conf" .. (7 Replies)
Discussion started by: stunn3r
7 Replies
10. Forum Support Area for Unregistered Users & Account Problems
I was unable to login and so used the "Forgotten Password' process. I was sent a NEWLY-PROVIDED password and a link through which my password could be changed. The NEWLY-PROVIDED password allowed me to login.
Following the provided link I attempted to update my password to one of my own... (1 Reply)
Discussion started by: Rich Marton
1 Replies
LEARN ABOUT FREEBSD
rescue
RESCUE(8) BSD System Manager's Manual RESCUE(8)
NAME
rescue -- rescue utilities in /rescue
DESCRIPTION
The /rescue directory contains a collection of common utilities intended for use in recovering a badly damaged system. With the transition
to a dynamically-linked root beginning with FreeBSD 5.2, there is a real possibility that the standard tools in /bin and /sbin may become
non-functional due to a failed upgrade or a disk error. The tools in /rescue are statically linked and should therefore be more resistant to
damage. However, being statically linked, the tools in /rescue are also less functional than the standard utilities. In particular, they do
not have full use of the locale, pam(3), and nsswitch libraries.
If your system fails to boot, and it shows a prompt similar to:
Enter full pathname of shell or RETURN for /bin/sh:
the first thing to try running is the standard shell, /bin/sh. If that fails, try running /rescue/sh, which is the rescue shell. To repair
the system, the root partition must first be remounted read-write. This can be done with the following mount(8) command:
/rescue/mount -uw /
The next step is to double-check the contents of /bin, /sbin, and /usr/lib, possibly mounting a FreeBSD rescue or ``live file system'' CD-ROM
(e.g., disc2 of the officially released FreeBSD ISO images) and copying files from there. Once it is possible to successfully run /bin/sh,
/bin/ls, and other standard utilities, try rebooting back into the standard system.
The /rescue tools are compiled using crunchgen(1), which makes them considerably more compact than the standard utilities. To build a
FreeBSD system where space is critical, /rescue can be used as a replacement for the standard /bin and /sbin directories; simply change /bin
and /sbin to be symbolic links pointing to /rescue. Since /rescue is statically linked, it should also be possible to dispense with much of
/usr/lib in such an environment.
In contrast to its predecessor /stand, /rescue is updated during normal FreeBSD source and binary upgrades.
FILES
/rescue Root of the rescue hierarchy.
SEE ALSO
crunchgen(1), crash(8)
HISTORY
The rescue utilities first appeared in FreeBSD 5.2.
AUTHORS
The rescue system was written by Tim Kientzle <kientzle@FreeBSD.org>, based on ideas taken from NetBSD. This manual page was written by
Simon L. Nielsen <simon@FreeBSD.org>, based on text by Tim Kientzle <kientzle@FreeBSD.org>.
BUGS
Most of the rescue tools work even in a fairly crippled system. The most egregious exception is the rescue version of vi(1), which currently
requires that /usr be mounted so that it can access the termcap(5) files. Hopefully, a failsafe termcap(3) entry will eventually be added
into the ncurses(3) library, so that /rescue/vi can be used even in a system where /usr cannot immediately be mounted. In the meantime, the
rescue version of the ed(1) editor can be used from /rescue/ed if you need to edit files, but cannot mount /usr.
BSD
July 23, 2003 BSD