| View previous topic :: View next topic |
| Author |
Message |
Mardok45
n00b
Joined: 21 Jun 2008
Posts: 69
Location: Right behind you
|
 Posted: Thu Jun 21, 2012 3:04 am Post subject: systemd-185 : The horror! |
 |
|
I just ventured into the wild and made the jump to systemd-185, and that was a painful, PAINFUL experience.
LVM2 and Pulseaudio (with udev enabled) will not compile. Pulseaudio has a patch in the gentoo-zh overlay that fixes it, but I can't find one for LVM2. I'm just leaving udev disabled for now.
Bluez is irrecoverably broken. I cannot find a working overlay for it anywhere, and Gnome depends on it.
Xorg, VLC, gvfs, and consolekit will break, but can be rebuilt.
If anyone else made the foolish jump, post whatever broke for you here.
EDIT: Yay, now my machine won't even boot anymore! |
|
| Back to top |
|
 |
The Doctor
Moderator
Joined: 27 Jul 2010
Posts: 2678
|
| Posted: Thu Jun 21, 2012 3:37 am Post subject: |
|
|
| Quote: | | Yay, now my machine won't even boot anymore! |
Ok, first thing is that all you need to do is remove the /init/systemd line from your kernel parameters. That should restore your working init system. I recommend setting up a rescue kernel that boots the same as your normal kernel but using the standard init system if you want to keep experimenting with systemd. If you removed it, then use a rescue cd and put it back.
I tried systemd, but I found that it didn't do much differently. Nothing broke, but still. A slightly faster boot up isn't worth it in my opinion. Its got a few quirks and I like my startup scripts.
I think you can forcibly remove the blue tooth from gnome (I think I did it once) but I can't give directions because I don't remember how I did it. probably a use flag somewhere. If all else fails there is package.provided. Tacky, but effective. (If you don't use Bluetooth)
_________________
First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
| Back to top |
|
|
Mardok45
n00b
Joined: 21 Jun 2008
Posts: 69
Location: Right behind you
|
| Posted: Thu Jun 21, 2012 4:16 am Post subject: |
|
|
The reason my machine isn't booting anymore is because I removed udev from LVM. It can't find my volumes anymore. Once that's fixed, everything should be fine.
EDIT: I installed gnome-base/gnome, which has a hard dependency on gnome-core-apps with bluetooth enabled. I made my own ebuild, removing bluetooth, and that got rid of bluez. |
|
| Back to top |
|
|
Mardok45
n00b
Joined: 21 Jun 2008
Posts: 69
Location: Right behind you
|
| Posted: Thu Jun 21, 2012 4:39 am Post subject: |
|
|
Well, I created a LVM-2.02.96 ebuild with udev enabled. It compiled fine, but it still doesn't show the volumes.
When I do vgchange -a y, it says '2 logical volume(s) in volume group "system" now active'.
lvdisplay shows
| Code: |
--- Logical volume ---
LV Path /dev/system/home
LV Name home
VG Name system
LV UUID 4QVScd-N3EM-H5ou-0XtS-G51c-Kw8A-ssqckE
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 0
LV Size 25.00 GiB
Current LE 800
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
--- Logical volume ---
LV Path /dev/system/gentoo
LV Name gentoo
VG Name system
LV UUID 51PSOI-AObX-D5eC-WsJK-fqiR-j97b-Lsy0ms
LV Write Access read/write
LV Creation host, time mardok-pc, 2012-05-13 17:09:04 -0400
LV Status available
# open 1
LV Size 20.00 GiB
Current LE 640
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
|
All the volumes are there, but /dev/system doesn't exist and /dev/mapper is empty. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Unsupported Software
