Re: Debian Pains, Ping Pong support
Posted: 2019-01-12 20:44
so you're not using logind, and complaining that you can't get to a login?# cat /proc/1/comm
init
so you're not using logind, and complaining that you can't get to a login?# cat /proc/1/comm
init
How have you configured your system to boot without systemd?zimbodel wrote:Code: Select all
# cat /proc/1/comm init
Code: Select all
empty@shinken:~ $ cat /proc/1/comm
systemd
empty@shinken:~ $ systemctl status getty@tty2.service --no-p
● getty@tty2.service - Getty on tty2
Loaded: loaded (/lib/systemd/system/getty@.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2019-01-12 20:58:48 GMT; 35min ago
Docs: man:agetty(8)
man:systemd-getty-generator(8)
http://0pointer.de/blog/projects/serial-console.html
Main PID: 8613 (agetty)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/system-getty.slice/getty@tty2.service
└─8613 /sbin/agetty --noclear tty2 linux
empty@shinken:~ $
just click YESzimbodel wrote:Then dont give a crap and ignore the post.
As to your reequeest.Head_on_a_Stick wrote:You do know there are no Debian developers here, right?zimbodel wrote:Not acceptable
I know that I couldn't give a flying crap about what you consider to be acceptable, nor do I care which operating system you use
$ sudo systemctl status getty@tty2.service --no-p
Failed to get properties: No such interface ''
Yea, right, look at what running it the way you want has gotten you, it is broken and you don't know what to do.zimbodel:>>I will run my systems any way I want. I have been doing so for more than 20 years with no issue.
Maybe some children should not be allowed in the sandbox and needs a safe space.
So the advice really applies to you.
Enjoy your deserved safespace. (try sudo first)
There aren't many left in this forum running init.zimbodel wrote:The last few debian versions started ping-ponging with very serious basic services that I relied on for decade+
1) It seems that control Alt F1-9 is now abolished.
All of them I cant even get one terminal.
Sheesh !!! now if I have an X problem and get a hung login screen I cant even control+alt+F1 to a terminal and quickly fix the mess. I guess now I have to boot into rescue mode and have no realtime problem resolution anymore.
This is really braindead not to support this anymore. In stretch it is not working and neither did it on some previous Debian versions during vanilla install.
Really painful...it is like silently abolishing Cron (which would be irresponsible).
Are you guys going to abolish it now finally or what is the plan ?
2) rc.local doesnt work anymore although it is included in /etc. It has been pingponging working/notworking between distributions.
The previous distribution started to leave out chmod +x on default which made it not execute. Even that now doesnt help anymore.
Are you guys going to at least have an executable rc.local in future versions or does boring but brick-stable BSD become more attractive to me again.
3) There is also on/off support for @reboot in cron.
I write cron scripts and then they dont work when upgrading to a newer debion version.
Why the backwards compatibilty issues with such a mission critical application?
Are you guys going to abolish it now finally or what is the plan ? as I now have to keep different scripts for different Debian versions.