Date: Fri, 26 Oct 2001 20:02:35 +0200 (SAT) From: John Hay <jhay@icomtek.csir.co.za> To: mark@grondar.za (Mark Murray) Cc: jhb@FreeBSD.org (John Baldwin), cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: cu(1) (Was: Re: cvs commit: src/etc/mtree BSD.var.dist) Message-ID: <200110261802.f9QI2Zk25435@zibbi.icomtek.csir.co.za> In-Reply-To: <200110261659.f9QGxXY47978@grimreaper.grondar.org> from Mark Murray at "Oct 26, 2001 05:59:33 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > > If we are keeping uucp junk around for cu(1), why is cu(1) not a port? > > > Alternatively, what are the desirable features of cu(1) that tip(1) really > > > needs to be able to do? > > > > I can just type 'cu -l /dev/cuaa0 -s 115200' w/o needing to setup an entry in > > /etc/remote. i.e., laziness. :) > > Aaaaah! The thot plickens :-) > > Do you have a problem with cu being a port and not in the base system? Well in my environment I use cu very often and I would really prefer it if it stayed in the base system. :-) ... That is except if someone volunteers to "fix" tip to do the two things I like most in cu: The first being the same example given above "cu -l /dev/cuaa0 -s 19200" The second being able to do "~+ command" which will run command with its stdin and stdout connected to the serial port. John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110261802.f9QI2Zk25435>