You are not logged in.
Hello
I have Fedora 16 partition (called /F16)
I would do certain action by chrooting to F16 partition via systemd-nspawn.
My bluetooth service is by default off.
Some script would require bluetooth connectiviy inside chroot environment.
So I normally do this. (I had tried about 1 month back and it had worked that time)
Here are steps:
1) systemctl start bluetooth
2) cd /F16
3) systemd-nspawn (system hangs)
If I change steps like this:
1) cd /F16
2) systemd-nspawn (system does not hang yet)
3) switch to another console i.e. non-chroot (arch) environment
4) systemctl start bluetooth (system hangs)
As it can be seen, no sooner the bluetooth is started system hangs. If bluetooth is not started then it does not hang.
Can anyone try the same in their machine? It is just 2 commands.
Thank you.
Last edited by amish (2014-07-07 03:57:22)
Offline
I have a Fedora rawhide nspawn container running on one of my machines. This machine also has bluetooth with the bluetooth.service enabled and running.
Maybe you should try with something newer than Fedora 16? That seems a bit old...
Offline
I did not get it. What is relation of F16 and systemd-nspawn?
Isnt it just shortcut way to do chroot?
Does systemd-nspawn depend on systemd of chroot environment? (Fedora in this case)
And why only when bluetooth is on? (That too after recent systemd updates)
Offline
systemd-nspawn is like a chroot, but does a lot more. I would guess that since (I think) fedora 16 is pre-systemd, this just might cause some problems.
Edit: This is entirely a guess though... since I have no non-systemd environments with which to test.
Last edited by WonderWoofy (2014-07-07 04:05:16)
Offline
No Fedora 16 is not pre-systemd.
As I said it worked earlier, I have been using that method from 2-3 months now. Last I tried was 1month back and it had worked.
Offline
No Fedora 16 is not pre-systemd.
As I said it worked earlier, I have been using that method from 2-3 months now. Last I tried was 1month back and it had worked.
Okay, then find yourself some real info to debug the situation and share it with this thread.
Offline
Well system hangs instantly and after booting I did:
journalctl --since=HH:MM
but nothing was shown in logs (for time when it hanged)
Unless I missed something to be passed (new to journalctl)
Offline