Re: ITP: lirc, devfsd
On Sun, Apr 02, 2000 at 10:16:42PM +0100, Tom Lees wrote: > LIRC is Linux Infra-red Remote Control support, see > http://fsinfo.cs.uni-sb.de/~columbus/lirc/index.html Ist it compiled for only one certain receiver type + port? Or were you able to make it configurable? Rainer -- KeyID=58341901 fingerprint=A5 57 04 B3 69 88 A1 FB 78 1D B5 64 E0 BF 72 EB
Re: NMU of debianutils (was: Re: (Bug horizon) Problem bugs)
On Sun, Apr 02, 2000 at 02:13:42PM -0500, Steve Greenland wrote: > http://www.debian.org/~stevegr/debutils/debianutils_1.13.3_i386.deb > Raphael and Ingo, if you get a chance, can you confirm I didn't screw > this up? Rainer, I think this fixes your bug too (#57464). Guy, if you > don't object by ~22:00 Tuesday, April 4th (CDT), I'm going to go ahead > and upload it to Incoming. I've installed it. Lets see how it behaves. More to come tommorow. Rainer -- KeyID=58341901 fingerprint=A5 57 04 B3 69 88 A1 FB 78 1D B5 64 E0 BF 72 EB
Re: Bug#21726 (tar: doesn't dump files to /dev/null)
Hi! Bdale Garbee <[EMAIL PROTECTED]>: > The behaviour you are reportin in tar is not a bug. It is an optimization > that allows backup tools like Amanda to use a tar to /dev/null to quickly > estimate the size of a prospective backup when doing tape space planning. > > This is well-documented in the tar info document, and is the way that tar-1.12 > works on all platforms: I really appologize for bothering you by not RTFM. But I don't like tar to try to be intelligent. Watch WinBlows and see the result of "intelligent" progs. Why the hell isn't there an explicit option for size-estimation? When I instruct tar to dump files to devnull I expect it to do so (eg. for readability-tests). Yes, I know it may be too late to be changed, but are there any hints whom to contact to get this "fixed"? Am I the only one who dislikes this behavior? Regards Rainer -- KeyID=58341901 fingerprint=A5 57 04 B3 69 88 A1 FB 78 1D B5 64 E0 BF 72 EB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: why not mingetty??
Hallo erstmal! Hi! Hamish Moffatt ([EMAIL PROTECTED]): > Is agetty used much for serial? I always use mgetty here, although usually > because I want something more exotic like AutoPPP or fax reception. I use it for a null-modem link to another machine. In combination with putting lilo on the same link (and maybe with 2.1.x's serial console feature) this is a REALLY nice way to save a monitor, graphics card, keyboard and to keep a way to connect to the box if the network is hosed. I don't like the idea to switch to a getty without serial support. Maybe we'll once enhance our setup to run over a serial line (as it's possible with FreeBSD). Regards Rainer -- KeyID=58341901 fingerprint=A5 57 04 B3 69 88 A1 FB 78 1D B5 64 E0 BF 72 EB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Test Report (was: Re: boot-floppies_2.0.4 (source i386) uploaded)
Hi! Enrique Zanardi ([EMAIL PROTECTED]): > On Mon, Apr 13, 1998 at 05:16:54AM +0200, Marcus Brinkmann wrote: > > >2) irritating: When installing from a (not yet mounted) hard disk partition > > > and entering the path to the main distribution, the > > > following > > > message appeared: > > > " /usr/lib/dpk//methods/disk/setup: line 8: 200 Broken Pipe > > > find "$mountpoint$2" -follow -name '*.deb' -print 2> > > > /dev/null > > > 201 Done | head -1 > > > 201 Done | grep . > /dev/null" > > > But all worked fine. This occurs, because 'head' simply closes it's input pipe. It can be suppressed by putting find in a subshell, which's stderr >/dev/null. This workaoround is also included in my patch in bugreport #21000 - I hope it becomes applied :-) Regards Rainer -- KeyID=58341901 fingerprint=A5 57 04 B3 69 88 A1 FB 78 1D B5 64 E0 BF 72 EB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
