Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Jan 30 23:49:58 <ikey> - Wait for flickery-cursor-of-death
- Jan 30 23:50:08 <ikey> - Repeatedly mash CTRL+ALT+F2 until you see a login prompt (text)
- Jan 30 23:50:12 <ikey> - Login as your user
- Jan 30 23:50:17 <ikey> - Run: sudo usysconf run -f
- Jan 30 23:50:20 <ikey> - Run: sudo eopkg rdb
- Jan 30 23:50:27 <ikey> Damn I missed up my space formatting there
- Jan 30 23:50:35 <ikey> And if you have networking at all: sudo eopkg up
- Jan 30 23:50:46 <ikey> If those steps don't magically fix it I'll be shocked
- Jan 30 23:51:19 <pan__> And can you tell me in "destination linux" terms, what that does?
- Jan 30 23:51:36 <pan__> ( meaning layman's terms)
- Jan 30 23:51:40 <ikey> the mashing one is to tell X11 to feck off so you're able to get to the tty
- Jan 30 23:51:52 <ikey> the usysconf one runs all system triggers (-f forces them all to run)
- Jan 30 23:51:58 <ikey> eopkg rdb forces a rebuild of the eopkg database
- Jan 30 23:52:07 <ikey> and sudo eopkg up performs a full system upgrade, applying any missing updates
- Jan 30 23:52:09 <ikey> and pending triggers
- Jan 30 23:52:23 <Catiua> I'll make a note of all of this
- Jan 30 23:52:23 <ikey> X11 = display server thingy
- Jan 30 23:52:32 <Catiua> Sounds useful in a bind
- Jan 30 23:52:37 <ikey> Nowadays its the de facto "repair my solus" steps
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement