Re: dselect
Hahaha...I know exactly what you mean. That's part of the problem I have now. I used the hold command to put a stop to that and now have to select file by file to upgrade since nobody seems to know how to clear the status in dselect. If you go on the line saying Updated packages (newer version is available) and type G, this should unhold all the packages that were updated. At least it works here. For some obscure reason, Hold and Unhold do not work if you are on the line saying All packages. Does someone know why ? -- Michel Beland [EMAIL PROTECTED] professionnel de recherchetel: (514)369-5223 fax: (514)369-3880 CERCA (CEntre de Recherche en Calcul Applique) 5160, boul. Decarie, bureau 400(423), Montreal (Quebec), Canada, H3X 2H9
Re: Problems working with bash.
Still, none of this even begins to compare with the ease of use of (horror! shock!) the DOS command interpreter 4DOS! Why use separate keys like M-p for this, when you've got the arrow keys? The principle is this: if you have an empty commandline and you type the up arrow, you get the previous command. If you've already typed something, you get whatever previous command starts with that. This combines the two functions that bash uses (and needs two keys for) into one. I wish I could convince bash to work like this! Gertjan. You can do this with tcsh and bash. In tcsh, write bindkey -k up history-search-backward bindkey -k down history-search-forward in your ~/.tcshrc file. In bash, write \e[A:history-search-backward \e[B:history-search-forward in your ~/.inputrc file. There are two problems with bash, though. First, if you log on your linux machine with a terminal that does not use ESC [ A for the up arrow, you will have to define another sequence. Second, if you have not already typed something on the command line, history-search-backward does not match any previous command in the history and just beeps. 4DOS and tcsh just match all the commands instead and show you the first match. I have read that this is fixed in bash 2.0, at last, but did not try it yet. -- Michel Beland [EMAIL PROTECTED] professionnel de recherchetel: (514)369-5223 fax: (514)369-3880 CERCA (CEntre de Recherche en Calcul Applique) 5160, boul. Decarie, bureau 400(423), Montreal (Quebec), Canada, H3X 2H9
Re: Problems working with bash.
Do you mean that they fixed libreadline so that you can now talk about the 'up' key instead of having to insert escape sequences? That's be great... IMHO, it's probably libreadline's biggest problem. I do not know about this. What I meant was that they fixed history-search-backward. -- Michel Beland [EMAIL PROTECTED] professionnel de recherchetel: (514)369-5223 fax: (514)369-3880 CERCA (CEntre de Recherche en Calcul Applique) 5160, boul. Decarie, bureau 400(423), Montreal (Quebec), Canada, H3X 2H9
Re: PPPproblem
This is very bad ! With the \q at the end, the password is shown in files /var/log/ppp.log and /var/log/messages, which are readable by everyone by default. You should only specify \qabcdefg so that the password is replaced by a string of question marks in log files. It would have seemed a little better it pppd/chat would make the passwords in the logfiles unreadable by default and require a special switch to make it readable, rather than the way it currently is. How is pppd/chat supposed to guess that what you pass to the ISP is a password ? This would not work unless you decide to not show anything in the log files. -- Michel Beland [EMAIL PROTECTED] professionnel de recherchetel: (514)369-5223 fax: (514)369-3880 CERCA (CEntre de Recherche en Calcul Applique) 5160, boul. Decarie, bureau 400(423), Montreal (Quebec), Canada, H3X 2H9
Re: PPPproblem
Following is an example of my ppp.chatscript. [ ... ] word \qabcdefg\q This is very bad ! With the \q at the end, the password is shown in files /var/log/ppp.log and /var/log/messages, which are readable by everyone by default. You should only specify \qabcdefg so that the password is replaced by a string of question marks in log files. I checked inside ppp_2.2.0f-19.deb, available on the stable tree, and the ppp.chatscript that comes with it shows two \q like above. It is declared as bug 7967 since March 19th, 1997, but it still is not corrected. Meanwhile, the Debian Web pages state that most security bugs get fixed in 48 hours... -- Michel Beland [EMAIL PROTECTED] professionnel de recherchetel: (514)369-5223 fax: (514)369-3880 CERCA (CEntre de Recherche en Calcul Applique) 5160, boul. Decarie, bureau 400(423), Montreal (Quebec), Canada, H3X 2H9
Re: cc compile error
Trying to make a simple hello.c program, I get this error message: bash$ cc -c hello.c In file included from /usr/include/stdlib.h:42, from hello.c:4: /usr/include/errno.h:27: linux/errno.h: No such file or directory Install the devel/libc5-dev corresponding to your installed version of base/libc5 and your problem will be solved. -- Michel Beland [EMAIL PROTECTED] professionnel de recherchetel: (514)369-5223 fax: (514)369-3880 CERCA (CEntre de Recherche en Calcul Applique) 5160, boul. Decarie, bureau 400(423), Montreal (Quebec), Canada, H3X 2H9
Re: rsh don' t work?!?
I want to use rsh, but I found: $ rsh localhost ls Permission denied. What I must change (for example in hosts.allow) to run it? Add your hostname to the file /etc/hosts.equiv and this will work. -- Michel Beland [EMAIL PROTECTED] professionnel de recherchetel: (514)369-5223 fax: (514)369-3880 CERCA (CEntre de Recherche en Calcul Applique) 5160, boul. Decarie, bureau 400(423), Montreal (Quebec), Canada, H3X 2H9
Re: Script Files
I have installed just base of Debian. I have not added any extra software. But I have added Envy 1.0 which is a type of mud. I'm trying to run it and to start it, I have to run the startup script. I'm getting all kinds of errors when I running it. Just to make sure I'm doing it right, I type '. startup' right? Also if someone could take a look at the startup file I have attached and maybe tell me whats is wrong, it would really make my day. You can run a script with '. startup' if the shell you are using is a Bourne shell derivative (sh, bash, ksh, ash) and the script is also written in a Bourne shell derivative. But this runs the script in the current environment, which might no be what you want. Your script, though is written in csh and can only be run by csh or tcsh, which are not in base, but in the section called 'shells'. Get either the csh or tcsh debian package and install it on your system with dpkg -i csh_5.26-8.deb or dpkg -i tcsh_6.06-10.deb Then, you can just run the script by typing its name on the command line. -- Michel Beland [EMAIL PROTECTED] professionnel de recherchetel: (514)369-5223 fax: (514)369-3880 CERCA (CEntre de Recherche en Calcul Applique) 5160, boul. Decarie, bureau 400(423), Montreal (Quebec), Canada, H3X 2H9
