From: Tony Hoffmann <tony.hoffmann@nrc.ca>
To: linux-kernel@vger.kernel.org
Subject: mkinitrd and 2.4.x annoyances
Date: Fri, 06 Apr 2001 16:45:05 -0700 [thread overview]
Message-ID: <3ACE5501.F5F551E4@nrc.ca> (raw)
While trying to upgrade a redhat 6.2 I've come across the following
annoyance.
Changes states that you need mkinitrd 2.9 or better. No problem. Go to
redhat
site and grab source rpm. In my case 3.0.5 was the one available.
Build and
install the package. Run it. Curse. Turns out that mkinitrd relies on
mktemp
accepting the -d which under 6.2 isn't the case. And remakeing mktemp
isn't
an option as I'm not about to upgrade to glibc 2.2 just for that. It
was an
easy enough fix to patch mkinitrd to not rely on the -d flag but still
bloody
annoying. I can see why they use mktemp -d as they do all the work in
the /tmp
dir so want to avoid potential races in creating the temp directories
but why
use /tmp at all? It's possible to do everything in the current working,
No?
reply other threads:[~2001-04-06 23:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3ACE5501.F5F551E4@nrc.ca \
--to=tony.hoffmann@nrc.ca \
--cc=linux-kernel@vger.kernel.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