| Summary: | On upgrade from 2010.2, mkinitrd fails because of missing /tmp directory | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Reinout van Schouwen <reinout> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | marja11, pterjan |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | mkinitrd | CVE: | |
| Status comment: | |||
|
Description
Reinout van Schouwen
2011-05-31 00:03:47 CEST
Translation of Dutch error messages: kan geen map aanmaken via sjabloon => cannot create directory using template Bestand of map bestaat niet => File or directory not found
Ahmad Samir
2011-05-31 01:29:33 CEST
CC:
(none) =>
pterjan Hmm if something removed /tmp the bug is in what removed it We can create it in mkinitrd but many other apps would be annoyed too... The error message above was the only suspicious thing I noticed, but if you need more debug info I'll be happy to provide it. Some kind of sanity check would probably be nice after the upgrade process, if I hadn't noticed this my system would not have booted up again (at least not with the Mageia kernel). Yes mkinitrd is important so it would be nice to make it more robust, but after reboot I would expect some services to not start without /tmp, probably including X so it's important to find why it has happened Was this bug ever reproduced, and if so, was it reproduced with Mageia 1 official release, too? Keywords:
(none) =>
NEEDINFO I haven't reproduced it on a different system. (In reply to comment #6) > I haven't reproduced it on a different system. Well, if you reproduced it on the same system: that is interesting, too. Did you reïnstall MDV 2010.2 first? Did you upgrade to Mageia 1 official? No, I didn't do a re-upgrade from 2010.2 to Mageia 1 on the same machine. @ Reinout Thanks for replying :) Closing as old, because there are no reports about this being an issue in Mageia 1 or current cauldron Status:
NEW =>
RESOLVED |