anyone have libc6_2.0.7pre1-4.deb (for intel) ?

1998-06-29 Thread Richard Kilgore
I'm trying to figure out what broke my rsh and rlogin to user
root.  If I do rsh -l root localhost cmd I get

   rcmd: localhost: Success

as output, the cmd never happens, and there's nothing useful in
the log files.  I just recently upgraded to libc6_2.0.7r-2, so
I'm suspecting the code in rcmd() code to start.

   - rick

-- 
Richard Kilgore |  [EMAIL PROTECTED]
Electrical  Computer Engineering   |  http://lore.ece.utexas.edu/~rkilgore/
The University of Texas at Austin   |  (512) 471-8011


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Re: modconf and whiptail

1998-02-05 Thread Richard Kilgore
On Thu, Feb 05, 1998 at 11:21:25AM +0100, Frere Roy wrote:
 I am trying to install modconf_0.2.15.deb but I get the message 
 whiptail is not installed 
 
 I have, however, installed newt0.21_0.21-3.deb which has installed 
 whiptail.
 
 Have I missed something?
 
 Thanks, Roy

There's a new package whiptail-xxx.deb.  You can find it in
/debian/Incoming on llug.sep.bnl.gov.

   later,

   - rick

-- 
Richard Kilgore |  [EMAIL PROTECTED]
Electrical  Computer Engineering   |  http://lore.ece.utexas.edu/~rkilgore/
The University of Texas at Austin   |  (512) 471-8011


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: Problems with dual boot NT/linux

1998-02-04 Thread Richard Kilgore
On Wed, Feb 04, 1998 at 11:36:00AM -0500, Richardson,Anthony wrote:
 I suspect that the NT boot sector was somehow corrupted.  This
 code reads   the NT boot.ini file and allows you to dual boot
 between DOS/NT. You can restore the NT boot   sector.  You'll
 need to make a set of (three) NT installation disks off of the
 NT CD.  Boot to   disk one, and insert disk two when prompted.
 Eventually you'll reach a menu asking if you want to   install
 NT or fix a previously installed NT setup.  Take the fix or
 repair option.  I don't remember   the exact set of menu
 options, but when I did it all of the directions seemed to be
 pretty clear.  The   whole process takes about 10 minutes tops.

Another alternative for fixing the NT boot sector is to get
BootPart at http://ourworld.compuserve.com/homepages/gvollant/bootpart.htm.
This is a handy utility to have anyway.

   - rick

-- 
Richard Kilgore |  [EMAIL PROTECTED]
Electrical  Computer Engineering   |  http://lore.ece.utexas.edu/~rkilgore/
The University of Texas at Austin   |  (512) 471-8011


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: procmail and folders

1998-02-02 Thread Richard Kilgore
On Mon, Feb 02, 1998 at 05:13:36PM +0200, Catalin Popescu wrote:
 Thank you to everybody answering my question on procmail and smail. I've
 put the files .forward and .procmailrc, modified the USERNAME to my
 usernaname (ie cpopescu), but it still does not work. Do I have to create
 the files where procmail is supposed to save the incoming messages? Is
 there something wrong with permissions?

Don't know if you're interested in this input, but if you use
sendmail instead of smail, it can just automatically use procmail
to deliver mail.  Thus, you don't need a .forward file at all.
You just have to make sure that procmail is installed and deliver
is not when you install sendmail.  Then sendmail will configure
itself to use procmail for all local mail delivery.

Configuring sendmail can be a bit of a bitch, but I found it to
be quite manageable this last time around, because
/usr/sbin/sendmailconfig, which is run automatically when
sendmail is first installed, asks relatively intelligible
questions, explaining each as it goes, and creates sendmail.cf
for you.  Even better, it actually first creates a file called
/etc/mail/sendmail.mc, which is a handful of m4 commands that are
used to create sendmail.cf.  But the sendmail.mc is a much more
human readable (and WAY shorter) file.  So if you want, you can
easily quickly modify stuff in the sendmail.mc file to try stuff
out.

   good luck!

   - rick

-- 
Richard Kilgore |  [EMAIL PROTECTED]
Electrical  Computer Engineering   |  http://lore.ece.utexas.edu/~rkilgore/
The University of Texas at Austin   |  (512) 471-8011


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


dhcpcd broke?

1998-01-29 Thread Richard Kilgore
I just upgraded all my systems to the latest hamm stuff, and
everything seems to work fine except for dhcpcd on the host
connected to my cable modem.  Here's my current software:

   Linux version 2.0.29 ([EMAIL PROTECTED]) (gcc version 2.7.2.3)
   ii  dhcpcd  0.70-2 a DHCP client
   ii  netbase 3.03-1 Basic TCP/IP networking binaries
   ii  netstd  3.02-1 Networking binaries and daemons for Linux

and pretty much everything else is a mirror of the latest stuff
on ftp.debian.org.

When I try to start up dhcpcd, it dies, leaves an eth0 configured
to IP address 0.0.0.0, and I get the following messages in
/var/log/syslog:

Jan 29 07:32:24 206-cdm-091 kernel: 7ARP: arp called for own IP address 
Jan 29 07:32:31 206-cdm-091 dhcpcd[716]: sendto (init): Operation not permitted 
Jan 29 07:33:16 206-cdm-091 kernel: 7ARP: arp called for own IP address 

Anyone have a clue?  Please?  Connecting to the net via modem
kinda sucks when I'm paying for a cable modem.

   thanks,

   - rick


-- 
Richard Kilgore |  [EMAIL PROTECTED]
Electrical  Computer Engineering   |  http://lore.ece.utexas.edu/~rkilgore/
The University of Texas at Austin   |  (512) 471-8011


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: Colors and Packages overview

1997-04-30 Thread Richard Kilgore
On Apr 30, Jim Smith wrote
alfred de Groot wrote:
 
 Recently I switched from Slackware to Debian. What I miss are the colors
 wich indicates directorys and other special files. How can I get those
 colors back?

Try alias ls=ls -color=auto in your .bashrc.


You may also need to fiddle with /usr/lib/X11/app-defaults/XTerm[-color]
to get colors in an xterm.  The color assignments are in
XTerm-color, and I've never figured out how this file ever gets
sourced.  I always just rename XTerm to XTerm-nocolor, create a
soft link from XTerm to XTerm-color, and change the #include
line in XTerm-color to include XTerm-nocolor.  Then, I think you
have to invoke the xterm command with the +cm options.

   later,

   - rick

-- 
Richard Kilgore |  [EMAIL PROTECTED]
Electrical  Computer Engineering   |  http://lore.ece.utexas.edu/~rkilgore/
The University of Texas at Austin   |  (512) 471-8011


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: vi

1997-04-15 Thread Richard Kilgore
On Apr 14, Rick Macdonald wrote
Ralph Winslow wrote:

I beg to differ the emacs case:

M- ; go to beginning of file
M-%; query-replace
129.168.1 RET  ; search for 192.168.1
129.168.200 RET; replace with 129.168.200
!  ; repeat for all occurrences

This is fewer keystrokes than vi.

Not exactly:

   :% s/129.168.1\./129.168.200/g

   later,

   - rick

-- 
Richard Kilgore |  [EMAIL PROTECTED]
Electrical  Computer Engineering   |  http://lore.ece.utexas.edu/~rkilgore/
The University of Texas at Austin   |  (512) 471-8011


Re: Will the real vi please stand up?

1997-04-15 Thread Richard Kilgore
On Apr 15, Robert D. Hilliard wrote
 It is generally agreed that any Unix user should be able to use
vi, regardless of which editor he prefers to use regularly.

 Apparently vi doesn't exist in Debian - vim, nvi, and elvis
(maybe others) all like to have a symlink named vi pointing to them.
A year ago when I was running Slackware, I thought I learned enough
about vi to use it, but not well.  Then I found I was learning elvis,
not vi.  When I first installed Debian I tried using 'vi' (I don't
remember which of the almost clones it really was) and found that
some of the commands I was familiar with caused the famous unexpected
results, so I gave up.

 Which of the vi semi-clones on Debian is most like the original
vi and most likely to work on a broad range of unices?

Bob

That's a pretty difficult question, since I'm not sure there are
many around who remember that much about what vi originally
looked like.  However, vim has an option for running in
vi-compatible mode.  Put the line set compatible in your
~/.vimrc file.  You're giving up an awful lot by doing so,
though.

   - rick

-- 
Richard Kilgore |  [EMAIL PROTECTED]
Electrical  Computer Engineering   |  http://lore.ece.utexas.edu/~rkilgore/
The University of Texas at Austin   |  (512) 471-8011


Re: shell problem after bo upgrade

1997-04-08 Thread Richard Kilgore
On Apr 7, John M. Rulnick wrote
Help needed.  After upgrading today to bo's base and devel (and a few
others), I'm receiving the following message:

sh: -c:line 1:missing closing ')' for arithmetic expression
sh: -c:line 1:syntax error near unexpected token ';'
sh: -c:line 1:'((gv /tmp/MO233499B410060202.ps); rm /tmp/MO233499B410060202.ps 
)'

when I try to view a PostScript file under Netscape.  For a long time
I have had 'gv %s' set up as a Helper under Netscape, with no
problems; clearly gv is being invoked, but is failing.  What's
happening?  Any pointers greatly appreciated.  (Please CC: me
directly if possible.)

I had to deal with the same problem, and decided to change my
/bin/sh to point to ash instead of bash.  This solves this
problem but can create others.  One problem I noticed already is
that ash doesn't seem to recognize ~usr or even ~.

   - rick

-- 
Richard Kilgore |  [EMAIL PROTECTED]
Electrical  Computer Engineering   |  http://lore.ece.utexas.edu/~rkilgore/
The University of Texas at Austin   |  (512) 471-8011


Re: rsh root priv

1997-04-03 Thread Richard Kilgore
On Apr 2, Nathan O. Siemers wrote
Hello all:

I'm having trouble telling linux to allow rsh's to work as root from
remote machines. Root's .rhosts, /etc/hosts.equiv, and
/etc/hosts.allow don't seem to affect the permission denied
result. Solution?

Change the command in.rshd in your /etc/inetd.conf file to read
in.rshd -h.  Same works for in.rlogind, if you want easier rlogin.
Someone changed this a few months ago and did not document it
well.

   later,

   - rick

-- 
Richard Kilgore |  [EMAIL PROTECTED]
Electrical  Computer Engineering   |  http://lore.ece.utexas.edu/~rkilgore/
The University of Texas at Austin   |  (512) 471-8011