mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] /etc/issue (Was: [ANNOUNCE] PTXdist 2011.10.0 released)
Date: Thu, 24 Nov 2011 16:23:17 +0100	[thread overview]
Message-ID: <64a1ecfdbe22f4d19a1f8c23235c225b@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <20111124140136.GF31544@pengutronix.de>

Am 24.11.2011 15:01, schrieb Michael Olbrich:
>>  21         echo
>>  22         echo
>>  23     ) > /tmp/issue
>>  24
>>  25     sed -i -e 's/\\/\\\\/g' /tmp/issue
> 
> 23     ) | sed -e 's/\\/\\\\/g' > /tmp/issue
> 
> should work too. I'd also recommend against using '\'. It always broke
> something for me (that's why I use '`'). I think via ssh /etc/issue is
> shown, but '\' is no special character for security reasons or something
> like that.

You're right, saves some IO when directly piping it through sed.

Regarding backslashes: I have no problem replacing them like above and
didn't see problems yet in my terminals. However /etc/issue is not shown
when logging in to ssh (dropbear). Should it?

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2011-11-24 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05  8:55 [ptxdist] [ANNOUNCE] PTXdist 2011.10.0 released Michael Olbrich
2011-11-22 13:28 ` Alexander Dahl
2011-11-22 14:25   ` Michael Olbrich
2011-11-22 14:41     ` Jon Ringle
2011-11-24 12:51     ` Alexander Dahl
2011-11-24 14:01       ` Michael Olbrich
2011-11-24 15:23         ` Alexander Dahl [this message]

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=64a1ecfdbe22f4d19a1f8c23235c225b@idefix.lespocky.dyndns.org \
    --to=post@lespocky.de \
    --cc=ptxdist@pengutronix.de \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox