Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Current state of development #42

Open
ghost opened this issue Dec 12, 2014 · 12 comments
Open

Current state of development #42

ghost opened this issue Dec 12, 2014 · 12 comments

Comments

@ghost
Copy link

ghost commented Dec 12, 2014

Hi,

Have been messing with runit for a while and was thinking of bringing it too ArchBang as an alternative init system. Wondering what current state of development ignite is in and how much works. Basically need base + X and openbox window manager. Do you use systemds own udev or something else?

Mr Green

@leahneukirchen
Copy link
Owner

mrgreen3 notifications@github.com writes:

Wondering what current
state of development ignite is in and how much works. Basically need
base + X and openbox window manager. Do you use systemds own udev or
something else?

Everything works for me. I use ignite on all (half a dozen) of my own
Arch installs. I use systemd-udevd, yes.

On Void Linux we run similar scripts using eudev, that works as well.

Christian Neukirchen chneukirchen@gmail.com http://chneukirchen.org

@ghost
Copy link
Author

ghost commented Dec 12, 2014

I am going to give ignite a try under arch, would like to use eudev if
possible. Do I need to make any changes to get it too work. Am I right in
saying that Void uses your scripts?

MrG

On 12 December 2014 at 09:21, Christian Neukirchen <notifications@github.com

wrote:

mrgreen3 notifications@github.com writes:

Wondering what current
state of development ignite is in and how much works. Basically need
base + X and openbox window manager. Do you use systemds own udev or
something else?

Everything works for me. I use ignite on all (half a dozen) of my own
Arch installs. I use systemd-udevd, yes.

On Void Linux we run similar scripts using eudev, that works as well.

Christian Neukirchen chneukirchen@gmail.com http://chneukirchen.org


Reply to this email directly or view it on GitHub
#42 (comment).

@ghost
Copy link
Author

ghost commented Dec 13, 2014

This is not a criticism, but I would adding rc.conf to install be possible?
Package installs and boots fine but you get dropped to a reduced shell as
rc.conf is missing. Do know that you have stated rc.conf should be created
consider having at least ttys running post install.

Everything else works fine even X, did try to install eudev but of course
you cannot remove systemd.

If I get time I will modify pkgbuild to install rc.conf.sample too /etc

Kev

On 12 December 2014 at 09:21, Christian Neukirchen <notifications@github.com

wrote:

mrgreen3 notifications@github.com writes:

Wondering what current
state of development ignite is in and how much works. Basically need
base + X and openbox window manager. Do you use systemds own udev or
something else?

Everything works for me. I use ignite on all (half a dozen) of my own
Arch installs. I use systemd-udevd, yes.

On Void Linux we run similar scripts using eudev, that works as well.

Christian Neukirchen chneukirchen@gmail.com http://chneukirchen.org


Reply to this email directly or view it on GitHub
#42 (comment).

@jonlap
Copy link

jonlap commented Dec 13, 2014

mrgreen3, what do you mean when you say you cannot remove systemd? Just being curious, been running openrc and eudev for quite some time now, had no trouble removing systemd.

@ghost
Copy link
Author

ghost commented Dec 13, 2014

Am using runit not openrc. Sure eudev would work but Arch compiles a lot of
packages with systemd support. Currently looking at runit-init in aur
(keyboard does not work at the moment under it)

On 13 December 2014 at 11:07, Joni Lapilainen notifications@github.com
wrote:

mrgreen3, what do you mean when you say you cannot remove systemd? Just
being curious, been running openrc and eudev for quite some time now, had
no trouble removing systemd.


Reply to this email directly or view it on GitHub
#42 (comment).

@leahneukirchen
Copy link
Owner

Did not add rc.conf because the file was owned by the old initscripts back then, probably could be done now.

I just keep systemd installed and don't run it.

@ghost
Copy link
Author

ghost commented Dec 14, 2014

I cleaned out most of systemd and just left systemd-udev. You can run busybox (mdev) but I could never get keyboard working under X. I think adding rc.conf with ttys just makes sense to me. I like to be able to boot into runit.

Not had any other problems, need to work on eth0 (renaming might be udev rule thing)

Would be nice to have :: Starting rather than output of init script.

To reduce confusing why not call it ignite.conf ;-)

@leahneukirchen
Copy link
Owner

I disabled the rename rule here.

@apayne
Copy link

apayne commented Jan 1, 2015

I'm currently bootstrapping a project for supervision scripts. I might be interested in incorporating some of your work. What license is the project under?

@ghost
Copy link
Author

ghost commented Jan 1, 2015

Check out readme states license

@apayne
Copy link

apayne commented Jan 1, 2015

Ok, found it. Thanks. Sorry about the question but browsing things on a mobile phone isn't always as easy/useful as a full browser and desktop.

For anyone else that reads this thread, the license is public domain.

Because of the license I will go ahead and incorporate any useful bits into the project. Attribution will still be given where applicable. Thank you for pointing that out.

@ghost
Copy link
Author

ghost commented Jan 1, 2015

No problem good luck :-)

On Thursday, January 1, 2015, Avery Payne notifications@github.com wrote:

Ok, found it. Thanks. Sorry about the question but browsing things on a
mobile phone isn't always as easy/useful as a full browser and desktop.

For anyone else that reads this thread, the license is public domain.

Because of the license I will go ahead and incorporate any useful bits
into the project. Attribution will still be given where applicable. Thank
you for pointing that out.


Reply to this email directly or view it on GitHub
#42 (comment).

Kev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants