TechnicalBooting lonely Linux

 

Press Ctrl+Enter to quickly submit your post
Quick Reply  
 
 
  
 From:  Drew (X3N0PH0N)  
 To:  Peter (BOUGHTONP)     
41672.49 In reply to 41672.48 
Sup G?
0/0
 Reply   Quote More 

 From:  Manthorp   
 To:  Drew (X3N0PH0N)     
41672.50 In reply to 41672.47 
Sorry, I was really frustrated.  I have finally managed to sort it, though.  

The standard solution is to edit /etc/kbd/config and set BLANK_TIME=0  That didn't work because there's an old bug in /etc/init.d/kbd.  Once I had amended kbd, the instruction worked.

Now I'm struggling with autologin to the console.  After trying half a dozen different solutions, all to no effect, I'm working on jozy's, HERE, which looked promising at first.  I created autlogin.conf
 
Quote: 
/etc/systemd/system/getty@tty1.service.d/autologin.conf
and filled it with the code
 
Quote: 
[Service]
ExecStart=
ExecStart=-/sbin/agetty --autologin pi --noclear %I 38400 linux
Where pi is my login.

But that's where I get lost.  The  next instruction is:

 
Quote: 
sudo systemctl enable getty@tty1.service

First I had to install systemd.  But when I run that code now I get an error message "no such file or directory". Yet if I navigate to /etc/systemd/system/getty.target.wants/ in the GUI I can see, open and read getty@tty1.service.  For good measure I tried:
 
Quote: 
sudo systemctl enable /etc/systemd/system/getty.target.wants/getty@tty1.service
But I get an error message "Too many levels of symbolic links".

If I try to navigate to:
 
Quote: 
cd /etc/systemd/system/getty.target.wants/
It says "No such file or directory".

Is there any other way to 'enable' getty@tty1.service and will it make any odds if I do?  And can you point me in any other direction for autologging into the console?

"We all have flaws, and mine is being wicked."
James Thurber, The Thirteen Clocks 1951
 
0/0
 Reply   Quote More 

 From:  Manthorp   
 To:  ANT_THOMAS     
41672.51 In reply to 41672.8 
Ant, I've got rid of the screen blanking but I still can't autologin to console (see my other recent post).  However I thought I'd try your autostart for Lonely anyway. One question before I try it: what does the instruction:
 
Quote: 
sleep 5
 do?

"We all have flaws, and mine is being wicked."
James Thurber, The Thirteen Clocks 1951
 
0/0
 Reply   Quote More 

 From:  ANT_THOMAS  
 To:  Manthorp      
41672.52 In reply to 41672.51 
My script is a loop so if the lonely program dies for some reason it restarts automatically. The sleep 5 bit is to give it a 5 second break before restarting, just in case there's a fuckup and it goes into a massive loop.

sleep 1

would also be suitable.
0/0
 Reply   Quote More 

 From:  Drew (X3N0PH0N)  
 To:  Manthorp      
41672.53 In reply to 41672.50 
>Sorry, I was really frustrated

I could tell (hug)

Yeah, you shouldn't install Systemd. There were two solutions earlier, one for systems with Systemd and one for those without. I don't know Raspbian and online documentation is poor so I'm guessing.

The non-Systemd solution should be this. But before you do it, check that /etc/inittab exists. If not, post here and we'll take it from there.

(Systemd is a new init system which is a fundamental part of the OS. Some distros have moved to it, some haven't yet. Debian moved to it a while back but it seems Raspbian hasn't caught up yet).

Edit: The root of the problem here is that automatically logging in involves manipulating the init system. And I have no idea what init system Raspbian uses.

Another edit: Ok, found something explicit. Follow this. Just the login bit, don't start LXDE. (It's the same solution as the previous link but this is specific to Raspbian
 
0/0
 Reply   Quote More 

 From:  Manthorp   
 To:  Drew (X3N0PH0N)     
41672.54 In reply to 41672.53 
 (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?

"We all have flaws, and mine is being wicked."
James Thurber, The Thirteen Clocks 1951
 
0/0
 Reply   Quote More 

 From:  Manthorp   
 To:  ANT_THOMAS     
41672.55 In reply to 41672.52 
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?

"We all have flaws, and mine is being wicked."
James Thurber, The Thirteen Clocks 1951
 
0/0
 Reply   Quote More 

 From:  Drew (X3N0PH0N)  
 To:  Manthorp      
41672.56 In reply to 41672.54 
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.
0/0
 Reply   Quote More 

 From:  CHYRON (DSMITHHFX)  
 To:  Drew (X3N0PH0N)     
41672.57 In reply to 41672.56 
 :-((  :-((  :-((

----
"I could stand in the middle of Fifth Avenue and shoot somebody and I wouldn’t lose any voters"
0/0
 Reply   Quote More 

 From:  graphitone  
 To:  Manthorp      
41672.58 In reply to 41672.55 
Where/when are you on? I'm local!
0/0
 Reply   Quote More 

 From:  Peter (BOUGHTONP)  
 To:  Drew (X3N0PH0N)     
41672.59 In reply to 41672.49 
Step 2. :'(
0/0
 Reply   Quote More 

 From:  Manthorp   
 To:  graphitone     
41672.60 In reply to 41672.58 
Soz Graphitone, I was at Chapel FM in Seacroft, banging on about artfaggery

"We all have flaws, and mine is being wicked."
James Thurber, The Thirteen Clocks 1951
 
0/0
 Reply   Quote More 

 From:  koswix  
 To:  Peter (BOUGHTONP)     
41672.61 In reply to 41672.48 
:'D

 ▪                    
             ┌────┐    ┌────┐                      
          │    │    │    │ ▪                    
          │    └────┘    │                      
          │   ──┐  ┌──   │ ▪                    
   ┌──────┤    ▪    ▪    │                      
  ┌┘      │              │ ▪                    
┌─┤       └──┐  │  │  ┌──┘                      
│ │          │ ││  ││ │   ┌─┐                   
│ │          └─┼┤  └┴─┴───┘ │                   
│ │           ─┘│           │                   
│ │   ┌──────┐  └┬──────────┘                   
  │   │      │   │                              
  │   │      │   │                              
  └───┘      └───┘                              
If Feds call you and say something bad on me, it may prove what I said are truth, they are afraid of it.

0/0
 Reply   Quote More 

 From:  koswix  
 To:  Drew (X3N0PH0N)     
41672.62 In reply to 41672.49 
Bastard. No need for that. Apologise to him.

 ▪                    
             ┌────┐    ┌────┐                      
          │    │    │    │ ▪                    
          │    └────┘    │                      
          │   ──┐  ┌──   │ ▪                    
   ┌──────┤    ▪    ▪    │                      
  ┌┘      │              │ ▪                    
┌─┤       └──┐  │  │  ┌──┘                      
│ │          │ ││  ││ │   ┌─┐                   
│ │          └─┼┤  └┴─┴───┘ │                   
│ │           ─┘│           │                   
│ │   ┌──────┐  └┬──────────┘                   
  │   │      │   │                              
  │   │      │   │                              
  └───┘      └───┘                              
If Feds call you and say something bad on me, it may prove what I said are truth, they are afraid of it.

0/0
 Reply   Quote More 

 From:  Drew (X3N0PH0N)  
 To:  Peter (BOUGHTONP)     
41672.63 In reply to 41672.59 
Ahahah. Y'know, I noticed that when I made the post then completely forgot about it :D

I'mSoRRyBP (hug)
0/0
 Reply   Quote More 

 From:  Manthorp   
 To:  Drew (X3N0PH0N)     
41672.64 In reply to 41672.56 
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!

"We all have flaws, and mine is being wicked."
James Thurber, The Thirteen Clocks 1951
 
0/0
 Reply   Quote More 

 From:  ANT_THOMAS  
 To:  Manthorp      
41672.65 In reply to 41672.64 
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.
0/0
 Reply   Quote More 

 From:  Drew (X3N0PH0N)  
 To:  Manthorp      
41672.66 In reply to 41672.64 
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.
0/0
 Reply   Quote More 

 From:  ANT_THOMAS  
 To:  Drew (X3N0PH0N)     
41672.67 In reply to 41672.66 
You may not have used a window manager, I must admit I stopped reading a while back :$
0/0
 Reply   Quote More 

 From:  Drew (X3N0PH0N)  
 To:  ANT_THOMAS     
41672.68 In reply to 41672.67 
////////// :O //////////
0/0
 Reply   Quote More 

Reply to All  
 

1–20  21–40  41–60  61–80  …  101

Rate my interest:

Adjust text size : Smaller 10 Larger

Beehive Forum 1.5.2 |  FAQ |  Docs |  Support |  Donate! ©2002 - 2024 Project Beehive Forum

Forum Stats