From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] [patch] nusb/ether followup to cs 8387
Date: Sat, 10 Apr 2021 14:12:03 +0200 [thread overview]
Message-ID: <62416E6D70D033EE0A46CC7354E92AD5@felloff.net> (raw)
In-Reply-To: <359EBD0C-5E86-4F5D-8271-40F007F5BDDC@cpan.org>
> Yes. I don't consider it an error to not have an ethernet interface at boot.
> If there's no ethernet interface, $ether will be '/net/ether*' because * won't expand.
> $ether/addr will not exist, because $ether is not a directory.
ah, i see. i think in that case, it is faster to just redirect stderr to /dev/null.
--
cinap
prev parent reply other threads:[~2021-04-10 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 19:27 Romano
2021-04-08 19:51 ` cinap_lenrek
2021-04-09 18:00 ` Romano
2021-04-10 12:12 ` cinap_lenrek [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=62416E6D70D033EE0A46CC7354E92AD5@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/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;
as well as URLs for NNTP newsgroup(s).