You are not logged in.
And now my machine wont boot. It can't find fstab and inittab and all those wonderful things.
What exactly did I do to myself and what should I do once this liveCD is done being burned?
Offline
You should have a /etc/fstab.pacnew file. Merge that with your old file and remove these lines
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0edit: probably irrelevant (all I could think of), must have missed something, too early - need coffee
Last edited by stlarch (2011-08-19 14:00:11)
Offline
let's pretend that you read the two threads about this and chose to ignore Allan's post where he specifically mentioned NOT to force upgrade the filesystem.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
And now my machine wont boot. It can't find fstab and inittab and all those wonderful things.
What exactly did I do to myself and what should I do once this liveCD is done being burned?
You mean you did pacman -Sf filesystem? Then why you don't have {init,fs}tab? These files will be present, perhaps in their prestine form...
While LIveCD is burning, you should REALLY try to LOVE Ubuntu, because it is going to be your final destination ![]()
Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd
Offline
How terribly unpleasant some people are...
I checked the front page before doing the update, I did not go out of my way to check the forums. When I first installed Arch several years ago, the installation guide said nothing about scouring forums before updates.
Anyway, yeah. It was silly to force it. But thanks a bunch for the condescension.
I just got home and haven't fiddled with it yet. I'll see if it's just a matter of fixing fstab.
Offline
The installation guide also didn't specifically say anything about checking the front page, but you did anyway. You are responsible for your system. Don't blame the installation guide or anyone else for something that you should have researched before doing.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
I think those people who got screwed by this last filesystem update, did something strange to their systems, because for me it went completely smooth, despite including kernel, initscripts and filesystem. Otherwise I wonder, how did all these packages made it out of testing...
FWIW, fstab does not require fixing upon update, apart from removing /dev/{shm,pts}. But even if you forget to do this change, you'll get only non critical errors on boot regarding mkdir /dev/shm failing in rc.sysinit.
Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd
Offline