Booting lonely Linux

From: Manthorp28 Jan 2016 18:27
To: Drew (X3N0PH0N) 54 of 101
 (hug)

Unfortunately, Raspbian no longer uses Inittab

Ironically, up to September it seems the Raspbian configuration utility (raspi-config) had four login options: GUI requiring login, GUI automatically logged in as 'pi', Console requiring login, Console automatically logged in as 'pi'.  My current raspi-config has only three.  Guess which option's been chopped?

If I don't need systemd, can I uninstall it without borking what I have got working so far?  Is it doing any harm?
From: Manthorp28 Jan 2016 18:28
To: ANT_THOMAS 55 of 101
Brill, gotta go out to defend conceptual art on local radio (sigh), but when I get back I'll try installing it.  Will it matter that I can't yet autologin to the Raspbian console?
From: Drew (X3N0PH0N)28 Jan 2016 19:14
To: Manthorp 56 of 101
Yours *must* be using inittab (Sysvinit is the name of the actual init system, inittab is one of its configuration files).

The only two possibilities are Sysvinit or Systemd. When you tried the Systemd way it told you it wasn't installed.

It might be that that documentation is for a newer version of Raspbian than you are using?

>If I don't need systemd, can I uninstall it without borking what I have got working so far?  Is it doing any harm?

I'm not entirely sure how you managed to install it without completely breaking everything. Replacing the init system is not the kind of thing you do if you can possibly avoid it, it's a massive thing.

It *may* be that you've arrived at some sort of half-way house with bits of each floating around but I think that's unlikely since I'm pretty sure you wouldn't be able to boot if that were the case. What I think is more likely is that you've installed Systemd but it's not being used. Which is fine, I'd leave it like that (because I'm scared that if you touch it everything is going to come falling down).

I'm *fairly sure* you're using Sysvinit. I'd try the inittab approach and see if that works.

Ok, just checked the Raspbian page and there's a choice of images available. The Jessie ones will be using Systemd while the Wheezy ones will be using Sysvinit.

Assuming they've not backported the kernel (unlikely with Debian) you can check which you're on with:
 
Code: 
uname -r

If the returned number is lower than 4 then you're on Wheezy and thus Sysvinit/inittab. If it's higher than 4 then you're on Jessie with Systemd.

It *might* be that your installation is just fucked somehow. The fact that you couldn't edit that file the other day is kinda worrying in that regard.

But yeah, find out which version you're on. If it's <4 then edit inittab as above. If it's >4 then ... we'll work out what to do with your clearly broken Systemd.
From: CHYRON (DSMITHHFX)28 Jan 2016 19:54
To: Drew (X3N0PH0N) 57 of 101
 :-((  :-((  :-((
From: graphitone28 Jan 2016 21:36
To: Manthorp 58 of 101
Where/when are you on? I'm local!
From: Peter (BOUGHTONP)28 Jan 2016 23:52
To: Drew (X3N0PH0N) 59 of 101
Step 2. :'(
From: Manthorp29 Jan 2016 00:15
To: graphitone 60 of 101
Soz Graphitone, I was at Chapel FM in Seacroft, banging on about artfaggery
From: koswix29 Jan 2016 01:07
To: Peter (BOUGHTONP) 61 of 101
:'D
From: koswix29 Jan 2016 01:08
To: Drew (X3N0PH0N) 62 of 101
Bastard. No need for that. Apologise to him.
From: Drew (X3N0PH0N)29 Jan 2016 05:59
To: Peter (BOUGHTONP) 63 of 101
Ahahah. Y'know, I noticed that when I made the post then completely forgot about it :D

I'mSoRRyBP (hug)
From: Manthorp29 Jan 2016 09:49
To: Drew (X3N0PH0N) 64 of 101
I completely erased the card and reinstalled everything from scratch so everything's tickety-boo.

Yes, it does have inittab after all.  After a bit of mucking about I made this change to it and it worked, so thank you very much.  I've created an image of the installation with everything working, just in case of disaster.

Now I just have to install Ant's code and (maybe) it's done!
From: ANT_THOMAS29 Jan 2016 10:14
To: Manthorp 65 of 101
I'm sure there must have been an easier way to do this, I might see if there's a method without using a window manager at all.

I would have hoped it would be boot to prompt, autologin, run lonely script.
From: Drew (X3N0PH0N)29 Jan 2016 10:30
To: Manthorp 66 of 101
Glad it's working.

You *should* now be able to just add the script you want to run to /etc/profile and it should run. That is if you're logging in automatically to a virtual terminal and not using a window manager. Ant's talk of window managers has me confused.

Edit: Although Ant's approach of running it as a daemon will make sure it comes back up if it crashes, which adding it to /etc/profile won't. So it's a better solution.
EDITED: 29 Jan 2016 10:32 by X3N0PH0N
From: ANT_THOMAS29 Jan 2016 10:36
To: Drew (X3N0PH0N) 67 of 101
You may not have used a window manager, I must admit I stopped reading a while back :$
From: Drew (X3N0PH0N)29 Jan 2016 10:38
To: ANT_THOMAS 68 of 101
////////// :O //////////
From: ANT_THOMAS29 Jan 2016 10:44
To: Drew (X3N0PH0N) 69 of 101
One of my RPis has decided to stop working at 7:15 this morning. No light, pressure, outdoor temp or box room temp data for me today :((
From: Drew (X3N0PH0N)29 Jan 2016 10:55
To: ANT_THOMAS 70 of 101
:|

How will you manage?
From: ANT_THOMAS29 Jan 2016 10:56
To: Drew (X3N0PH0N) 71 of 101
It is stressing me out :'(
From: ANT_THOMAS29 Jan 2016 10:58
To: Drew (X3N0PH0N) 72 of 101
Look at the missing data!!!

Attachments:
From: Drew (X3N0PH0N)29 Jan 2016 11:10
To: ANT_THOMAS 73 of 101
I need to know the temperature of your box :((