From: Michael Prokop <news@michael-prokop.at>
To: Zsh Users <zsh-users@sunsite.dk>
Subject: Re: setopt noclobber in /proc-filesystem
Date: Wed, 17 Aug 2005 12:08:49 +0200 [thread overview]
Message-ID: <2005-08-17T12-04-01@devnull.michael-prokop.at> (raw)
In-Reply-To: <20050815145854.GB46146@dan.emsphone.com>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
* Dan Nelson <dnelson@allantgroup.com> [20050815 17:15]:
> In the last episode (Aug 15), Michael Prokop said:
> > % setopt noclobber
> > % echo foo > /proc/sys/kernel/hotplug
> > zsh: file exists: /proc/sys/kernel/hotplug
> > Is there any chance to use option 'noclobber' but allow writing to
> > /proc-filesystem anyway? I do know that there exists 'setopt
> > clobber' ;-) and "echo ... >| /proc/..." as well but other users
> > might not know this.
> > I'd like to ship zsh on my live-cd-system with 'setopt noclobber'
> > enabled but would like to avoid that users think the behaviour in
> > /proc-fs is a bug. Any ideas?
> sysctl -w kernel.hotplug=foo
Hehe, I'd like to find a solution for the zsh-echo->/proc. ;)
*I* do know that I can use sysctl and 'echo >|...' but other users
do *not*. Therefore I need a solution where something like
echo 3 > /proc/acpi/sleep
works out-of-the-box.
regards,
-mika-
--
,'"`. http://www.michael-prokop.at/
( grml.org -» Linux for texttool-users and sysadmins
`._,' http://www.grml.org/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-17 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 11:14 Michael Prokop
2005-08-15 14:58 ` Dan Nelson
2005-08-15 21:54 ` Nikolai Weibull
2005-08-17 10:08 ` Michael Prokop [this message]
2005-08-17 10:19 ` Oliver Kiddle
2005-08-17 20:18 ` Michael Prokop
2005-08-17 20:51 ` Wayne Davison
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2005-08-17T12-04-01@devnull.michael-prokop.at \
--to=news@michael-prokop.at \
--cc=zsh-users@sunsite.dk \
--cc=zsh@michael-prokop.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).