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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 07 2001 - 21:00:19 EST