Refracta Development, Scripts, etc.
Post a reply

Re: Going with the systemd flow . . . or not?

Mon Nov 24, 2014 3:15 am

Tried downgrading live-* packages to 4.0.0-1, but that didn't help. Did that on the original jessie-sysv, not on the unpinned installation.

Re: Going with the systemd flow . . . or not?

Mon Nov 24, 2014 11:23 am

Dropped back to previous version of refractasnapshot (9.1.2-2, Sept. 25) Did not help.

Re: Going with the systemd flow . . . or not?

Mon Nov 24, 2014 3:40 pm

Went back to the fully-updated jessie with libsystemd0 and sysvinit. Replaced sysvinit with systemd. Made a snapshot. It boots. This is bad.

I've also tried using refractasnapshot vs. refractasnapshot-gui, but that didn't make a difference.

Currently trying with a modified initrd: set NFSROOT to null in conf/initramfs.conf

Don't know if I'm even on the right track here...

Re: Going with the systemd flow . . . or not?

Mon Nov 24, 2014 3:46 pm

Appreciate your posting a log of your efforts to get everything working on Jessie. I have no doubt you'll figure it out eventually.

Re: Going with the systemd flow . . . or not?

Tue Nov 25, 2014 1:40 am

Changing "NFSROOT=" didn't help.

I installed live-build and built an iso. Standard system with sysvinit. Turns out that's not so easy to do - using '--initsystem sysvinit' didn't do it. Also had to edit config/package-lists/live.list.chroot to change live-config-systemd to live-config-sysvinit. It boots.

Re: Going with the systemd flow . . . or not?

Wed Nov 26, 2014 3:26 am

FYI, from the debianfork IRC earlier today. Your hard work is helping things move along:

<coagen> clefebvre: I don't have the links handy, but the refracta pkg list is a good place to start
<tmyklebu> shrug. nextime sounded like he was setting up some debianfork boxes on which he'd host a debianfork repo.
<coagen> clefebvre: in the link in the topic, look at the pkglist file, then search for "nosystemd" and you'll see all the packages they had to recompile and potentially pull older snapshots from snapshots.debian.org like cups
<coagen> err
<coagen> clefebvre: thats the exegnu pkglist sorry
<coagen> clefebvre: oh, the images are in that link you found on the refracta forum
<coagen> hah
<kelsoo> Both Refracta and Gnuexe are very similar. Both worked fsmithred and dzz worked on Refacta dzz made his own spin for trinity DE


debianfork has also set up crowdfunding but the mechanism didn't seem very secure to me. Any thoughts on how it's set up?

Re: Going with the systemd flow . . . or not?

Wed Nov 26, 2014 8:01 am

mechanism didn't seem very secure to me. Any thoughts on how it's set up?
I tested the webform submission by entering bogus card&ccv. All was secure (https). My "thoughts": I don't know why stripe payment processor chose this "web two point oh" in-page popup shite, but that (what debianfork/dyne has embedded) is based on the standard stripe API.

Re: Going with the systemd flow . . . or not?

Wed Nov 26, 2014 10:22 am

It helps to write this stuff down before I go to sleep. I've made so many snapshots lately, I got confused. Try again...

Also did not help:

- noacpi, noapic, nolapic or the full "no probe" choice in the boot menu.
- udev_log="err" in etc/udev/udev.conf (and why is it called systemd-udev in the boot messages?)
- older kernel, 3.16-3-686-pae

Should have re-read dzz's first mention of this problem more carefully before jumping in.

Dropped util-linux down from 2.25.2-3 to 2.20.1-5.11 and...

IT BOOTS!!!

Re: Going with the systemd flow . . . or not?

Wed Nov 26, 2014 1:15 pm

Here's the upstream changelog for util-linux.
http://git.kernel.org/cgit/utils/util-l ... g/?ofs=100

I'm not sure if the dates in the apt/archives are the date the deb was created or the date I downloaded it, but it looks like the relevant change(s) occurred between Oct. 4 and Oct. 24. Lotta stuff there.

Re: Going with the systemd flow . . . or not?

Wed Nov 26, 2014 2:55 pm

What I did note was an installation booted with newer util-linux but not a live system. I have looked already changelogs and bug reports (probably not well enough). At the moment I dont have a clue.. at least we ruled out a few other suspects. I suspect the problem might be in initramfs.

Here, got 2.20x version pinned for now but still investigating. Just recompiled 2.25.2-2 but all this takes time to test.

On another note (don't remember if I already mentioned it) I built consolekit2 debs.. Main reason was to get suspend back in Trinity DE menu (success) but also got shutdown back in xfce menu.
Post a reply