From: "Trevor Woerner" <twoerner@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [master-next][PATCH 2/3] psplash: work on first boot (sysvinit)
Date: Wed, 23 Dec 2020 17:41:29 -0500 [thread overview]
Message-ID: <20201223224129.GA1691@localhost> (raw)
In-Reply-To: <20201223215005.GA9542@localhost>
On Wed 2020-12-23 @ 04:50:05 PM, Trevor Woerner wrote:
> On Wed 2020-12-23 @ 06:00:21 PM, Richard Purdie wrote:
> > Personally, I don't really like the idea of having a top level
> > directory called .psplash,
>
> Neither do I, which is why I also added the code to remove the directory once
> the psplash program is done running. Whenever psplash is run the directory is
> created just before it starts and removed when psplash is done.
>
> > is there a reason it doesn't work in /mnt?
specifically…
mkdir: can't create directory '/mnt/.psplash': Read-only file system
mount: mounting tmpfs on /mnt/.psplash failed: No such file or directory
mkfifo: Read-only file system
then
umount: can't unmount /mnt/.psplash: No such file or directory
next prev parent reply other threads:[~2020-12-23 22:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 17:06 [master-next][PATCH 1/3] PSPLASH_FIFO_DIR: refactor Trevor Woerner
2020-12-23 17:06 ` [master-next][PATCH 2/3] psplash: work on first boot (sysvinit) Trevor Woerner
2020-12-23 18:00 ` [OE-core] " Richard Purdie
2020-12-23 21:50 ` Trevor Woerner
2020-12-23 22:06 ` Richard Purdie
2020-12-23 22:35 ` Trevor Woerner
2020-12-23 22:39 ` Richard Purdie
2020-12-23 22:41 ` Trevor Woerner [this message]
2020-12-23 22:43 ` Richard Purdie
2020-12-23 22:55 ` Trevor Woerner
2020-12-23 17:06 ` [master-next][PATCH 3/3] sysvinit/rc: improved progress messages Trevor Woerner
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=20201223224129.GA1691@localhost \
--to=twoerner@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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