Sponsored Content
Full Discussion: this helps me out big time
Top Forums UNIX for Dummies Questions & Answers this helps me out big time Post 7240 by djatwork on Friday 21st of September 2001 02:48:56 PM
Old 09-21-2001
thanks, thats some good stuff. Smilie
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to view a big file(143M big)

1 . Thanks everyone who read the post first. 2 . I have a log file which size is 143M , I can not use vi open it .I can not use xedit open it too. How to view it ? If I want to view 200-300 ,how can I implement it 3 . Thanks (3 Replies)
Discussion started by: chenhao_no1
3 Replies

2. Shell Programming and Scripting

need help big time

solved (1 Reply)
Discussion started by: rockbike
1 Replies

3. UNIX for Dummies Questions & Answers

How big is too big a config.log file?

I have a 5000 line config.log file with several "maybe" errors. Any reccomendations on finding solvable problems? (2 Replies)
Discussion started by: NeedLotsofHelp
2 Replies

4. UNIX for Dummies Questions & Answers

gref -f taking long time for big file

grep -f taking long time to compare for big files, any alternate for fast check I am using grep -f file1 file2 to check - to ckeck dups/common rows prsents. But my files contains file1 contains 5gb and file 2 contains 50 mb and its taking such a long time to compare the files. Do we have any... (10 Replies)
Discussion started by: gkskumar
10 Replies

5. Red Hat

Du -sh command taking time to calculate the big size files

Hi , My linux server is taking more time to calculate big size from long time. * i am accessing server through ssh * commands # - du -sh * #du -sh * | sort -n | grep G Please guide me for fast way to find big size directories under to / partition Thanks (8 Replies)
Discussion started by: Nats
8 Replies

6. Homework & Coursework Questions

Makefile helps

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: The code in project2 is for a program that formats C++ code into HTML for presentation in a webpage. For example,... (1 Reply)
Discussion started by: dhnguyen0708
1 Replies
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
All times are GMT -4. The time now is 11:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy