FreeBSD Bugzilla – Attachment 21118 Details for
Bug 37073
Few new tips for FreeBSD-tips fortune
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
[patch]
file.diff
file.diff (text/plain), 4.24 KB, created by
Sean Chittenden
on 2002-04-14 21:50:01 UTC
(
hide
)
Description:
file.diff
Filename:
MIME Type:
Creator:
Sean Chittenden
Created:
2002-04-14 21:50:01 UTC
Size:
4.24 KB
patch
obsolete
>Index: games/fortune/datfiles/freebsd-tips >=================================================================== >RCS file: /home/ncvs/src/games/fortune/datfiles/freebsd-tips,v >retrieving revision 1.14.2.4 >diff -u -r1.14.2.4 freebsd-tips >--- games/fortune/datfiles/freebsd-tips 2002/03/24 03:28:46 1.14.2.4 >+++ games/fortune/datfiles/freebsd-tips 2002/04/14 20:35:30 >@@ -7,7 +7,7 @@ > By pressing "Scroll Lock" you can use the arrow keys to scroll backward > through the console output. Press "Scroll Lock" again to turn it off. > % >-Want colour in your directory listings? Use "ls -G". "ls -F" is also useful, >+Want color in your directory listings? Use "ls -G". "ls -F" is also useful, > and they can be combined as "ls -FG". > % > If you need to ask a question on the FreeBSD-questions mailing list then >@@ -128,12 +128,12 @@ > learned it, but somewhat user-unfriendly. To use ee (an easier but less > powerful editor) instead, set the environment variable EDITOR to /usr/bin/ee > % >-If you accidently end up inside vi, you can quit it by pressing Escape, colon >+If you accidentally end up inside vi, you can quit it by pressing Escape, colon > (:), q (q), bang (!) and pressing return. > % > You can use aliases to decrease the amount of typing you need to do to get > commands you commonly use. Examples of fairly popular aliases include (in >-bourne shell style, as in /bin/sh, bash, ksh, and zsh): >+Bourne shell style, as in /bin/sh, bash, ksh, and zsh): > > alias lf="ls -FA" > alias ll="ls -lA" >@@ -148,8 +148,8 @@ > To remove an alias, you can usually use 'unalias aliasname'. To list all > aliases, you can usually type just 'alias'. > % >-In order to support national characters for european languages in tools like >-less without creating other nationalisation aspects, set the environment >+In order to support national characters for European languages in tools like >+less without creating other nationalization aspects, set the environment > variable LC_ALL to 'en_US.ISO8859-1'. > % > You can search for documentation on a keyword by typing >@@ -460,7 +460,7 @@ > You can open up a new split-screen window in (n)vi with :N or :E and then > use ^w to switch between the two. > % >-sh (the default bourne shell in FreeBSD) supports command-line editing. Just >+sh (the default Bourne shell in FreeBSD) supports command-line editing. Just > ``set -o emacs'' or ``set -o vi'' to enable it. > % > When you've made modifications to a file in vi(1) and then find that >@@ -469,3 +469,46 @@ > > This won't work if you don't have write permissions to the directory > and probably won't be suitable if you're editing through a symbolic link. >+% >+The portupgrade package contains several useful programs that help >+with upgrading, installing, and comparing versions of software that >+has been installed via ports. >+ >+ # cd /usr/ports/sysutils/portupgrade/ >+ # make install && make clean >+% >+If you are updating your ports tree and have the portupgrade(1) >+utilities installed, run the following command to see what ports can >+be upgraded: >+ >+ # portversion -v -L= >+% >+The portupgrade(1) utility (ports/sysutils/portupgrade) provides a >+safe and easy way for upgrading ports. >+ >+ # portupgrade [portname] >+% >+The portsdb(1) command that comes with the portupgrade(1) suite of >+utilities (ports/sysutils/portupgrade) can be used to remake the ports >+master INDEX file. Try adding the following line to your >+/etc/weekly.local file so that periodic(8) will rebuild the ports >+INDEX: >+ >+/usr/bin/nice -20 /usr/local/sbin/portsdb -U -u >+% >+The pkgdb(1) command that comes with the portupgrade(1) suite of >+utilities (ports/sysutils/portupgrade) can be used to correct broken >+dependencies that can sometimes occur when upgrading ports with >+dependencies. After upgrading several ports, it is probably a good >+idea to run the following command to fix port dependencies. >+ >+ # pkgdb -F >+% >+Try combining portversion(1) with tee(1) and a periodic(8) job that >+follows after you update your ports tree. Use tee(1) that way you get >+a list of ports that can be upgraded in your nightly email along with >+an updated copy on the file system. portversion(1) is apart of the >+portupgrade port (ports/sysutils/portupgrade). Ex: place the >+following after cvsup commands in /etc/weekly.local: >+ >+/usr/local/sbin/portversion -O -v -L= | /usr/bin/tee /etc/upgradable_ports
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 37073
: 21118