Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Bug#251489: noclobber broken as non-root for devices

X-seq: zsh-workers 19995
From: Clint Adams <schizo@xxxxxxxxxx>
To: zsh-workers@xxxxxxxxxx
Subject: Re: Bug#251489: noclobber broken as non-root for devices
Date: Fri, 28 May 2004 15:41:26 -0400
Cc: Joey Hess <joeyh@xxxxxxxxxx>, 251489-forwarded@xxxxxxxxxxxxxxx
In-reply-to: <20040528183657.GA28155@xxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <20040528183657.GA28155@xxxxxxxxxxx>

> 
> joey:~/src/d-i/installer/build/dest/hd-media/2.6>sudo zcat boot.img.gz >/dev/sda 
> zsh: file exists: /dev/sda
> zsh: exit 1     sudo zcat boot.img.gz > /dev/sda
> joey:~/src/d-i/installer/build/dest/hd-media/2.6>su
> root:/home/joey/src/d-i/installer/build/dest/hd-media/2.6>zcat boot.img.gz >/dev/sda
> 
> This is very annoying, it seems to think that because I'm not root,
> I cannot write to devices. I can, and I'm using sudo anyway..

Well, the sudo is irrelevant.  The question is how NO_CLOBBER should
behave with devices nodes.

Messages sorted by: Reverse Date, Date, Thread, Author