Re: ^c broken in latest potato
In message [EMAIL PROTECTED] Todd Suess [EMAIL PROTECTED] wrote: At 01:00 PM 1/11/00 -0500, Ben Collins wrote: Well, if you are still having a problem with ^C (note, you must restart your su shell), then it isn't caused by the login package. I tested it thoroughly, and it worked in bash and tcsh. Yup, I rebooted the machine, etc, and even if I am on the console and SU'd to root in a kvt window under KDE, if I do tail -f /var/log/syslog or any kind of command, ctrl-c will not exit the task. Have to ctrl-z and then kill %1 to actually kill the job. My experience agrees with what Ben is saying - upgrading to the latest login package fixed it on the machine I tried it on. (I've not tried to see if the same problem occurring when logging in via ssh has also stopped now, though). Thanks for the fix Ben. bfn, Joseph -- Joseph Heenan, Coventry, UK http://www.ping.demon.co.uk/
Re: apt-get upgrade
In message [EMAIL PROTECTED] Nathan York [EMAIL PROTECTED] wrote: i just did an apt-get upgrade today and got this The following packages have been kept back bash cdrecord dpkg less libncurses4 libreadlineg2 ncurses-bin procps psmisc sniffit tkdesk xpdf why are these packages being kept back, i didn't place any of them on hold except for the cdrecord.is anyone else experiencing this problem.. You'll probably find that the new versions depend on a new version of a library that you have something depending on a old version, or depend on a new library that's not get in the distribution. You should find apt-get will give you a clue as to why they're been held back if you do apt-get install bash (for example). bfn, Joseph -- Joseph Heenan, Coventry, UK http://www.ping.demon.co.uk/
Re: poff not working... ???
In message [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Well, I figured it out after much puttering about... There is no function kill on my system AFAICT. I presume it's a builtin for the shell?? I replaced the line in poff KILL=/bin/kill with KILL=kill and it works fine. Am I shooting myself security-wise with this? If kill IS somewhere, I can't find it.. yet. /bin/kill is part of the procps package. I guess that means the ppp package should really depend on the procps one... bfn, Joseph -- Joseph Heenan, Coventry, UK http://www.ping.demon.co.uk/
Re: How to recover from crash (urgent for me)
In message [EMAIL PROTECTED] Fam. Engelen [EMAIL PROTECTED] wrote: After having crashed my slink-with-a-bit-potato, the following appears on boot: --- /dev/hda5 contains a fs with errors, check forced. /dev/hda5: Inode 87941 has illegal block(s). UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) fsck failed. Please repair manually and reboot. Please note that the root filesystem is currently mounted read-only. To remount it read-write: mount -n -o remount,rw / --- At this point you should find you have a shell, or a request to enter the root password so you can get a shell. Type 'fsck -c /dev/hda5', and sit back and watch. Enter 'y' if fsck asks if you want to fix something. When it finished, run it again to check everything is still ok - it shouldn't fix anything this time - if it does, you probably have bigger problems (such as imminent hardware failure). Once you're happy, hit ctrl-D and the system should bootup normally. bfn, Joseph -- Joseph Heenan, Coventry, UK http://www.ping.demon.co.uk/
Re: bind: how to *not bind* to interfaces?
In message [EMAIL PROTECTED]
hypnos [EMAIL PROTECTED] wrote:
I have Bind running on my one of my machines here,
and when it starts, it binds to port 53 of each
interface (lo, eth0, ppp0). How can I change this
so that the interface it listens on is eth0?
lemnos:/var/named/pz# named -v
named 8.2.2-P5-NOESW Fri Nov 19 12:28:17 CST 1999
[EMAIL PROTECTED]:/debian/home/bdale/slink/bind-8.2.2p5/src/bin/named
lemnos:/var/named/pz# netstat -nta
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp0 0 209.43.67.86:53 0.0.0.0:* LISTEN
tcp0 0 192.168.1.1:53 0.0.0.0:* LISTEN
tcp0 0 127.0.0.1:530.0.0.0:* LISTEN
Use the listen-on directive in the options section of
/etc/bind/named.conf. eg:
listen-on { 127.0.0.1; 192.168.1.1; };
(You can find that out by doing man named.conf and searching for
'interface', btw.)
bfn,
Joseph
--
Joseph Heenan, Coventry, UK http://www.ping.demon.co.uk/
exports(5) manpage
None of my systems (all running unstable) have a man page for /etc/exports - am I missing a package somewhere, or is this a bug? I expected it to be in nfs-server or nfs-common, both of which I have installed, and there's no sign of it in either. bfn, Joseph -- Joseph Heenan, Coventry, UK http://www.ping.demon.co.uk/
Re: NIS and shadow all over the place
In message [EMAIL PROTECTED] Carel Fellinger [EMAIL PROTECTED] wrote: in return of installing Debian GNU/Linux I got my father's old 486, so now I've this problem connecting my machines:) I've installed NIS, but I can't prevent the shadow file of being public now:( Anybody on my machine can do ypcat shadow.byname and start cracking those passwords. I thought the hole point of shadow was to let nobody but root see it. It's not a problem yet, I trust my wife and kids, but I would be happier if it were hidden. Or maybe I should consider switching to something else like Kerberos or PAM? I'm still running mainly Ham (eagerly waiting for potato to become stable:) but have upgraded things, e.g libc I'm running the latest potato, and it behaves correctly for me. ypcat shadow.byname shows the file when run as root, but not when run as a normal user. For lack of a better suggestion, perhaps try upgrading to the potato nis package? bfn, Joseph -- Joseph Heenan, Coventry, UK http://www.ping.demon.co.uk/
Re: ^c broken in latest potato
In message [EMAIL PROTECTED] George Bonser [EMAIL PROTECTED] wrote: Cant seem to kill a running process with ^C anymore. Noticed the problem last night but do not know when the problem crept in. I can suspend the process with ^Z and then kill it manually with kill but ^C does not seem to work anymore. I've noticed this after 'su'ing, and filed a bug report (#54496) against login. I've also noticed it after sshing in, which happens on two of three identical boxes but strangely not on the third, which I've reported to Ben Collins, but I'm not sure what it's down to. bfn, Joseph -- Joseph Heenan, Coventry, UK http://www.ping.demon.co.uk/
