Re: [trinity-users] KSysV missfire

Am Samstag, 19. Dezember 2015 schrieb Gene Heskett: Hi Gene! There are no side effects in setting a root password. In fact, there is already a root password, but it's useless for the user. If you want to try: $ sudo bash # cp /etc/shadow /root/ # passwd

If you have sideffects using sudo, you can always do: $ su # cp /root/shadow /etc/ Nik > > Am Samstag, 19. Dezember 2015 schrieb Gene Heskett: > > > On Saturday 19 December 2015 01:52:46 Michele Calgaro wrote: > > > > On 12/17/2015 03:06 PM, Gene Heskett wrote: > > > > > Greetings; > > > > > > > > > > Out of curiosity, I tried to run ksysv from the tde menu. > > > > > Can't. If insists on a root pw that does not exist on this > > > > > debian wheezy install. A sudo -i in a konsole for me, and it > > > > > runs just fine. > > > > > > > > > > This really ought to be fixed. No biggie for me, but... > > > > > > > > > > Cheers, Gene Heskett > > > > > > > > No issues here (Debian/Stretch) with ksysv. Just typed in the > > > > root password and it worked flawlessly. The fact that ksysv > > > > requires root password is not surprising since you are playing > > > > with the system config. Cheers > > > > Michele > > > > > > You missed the point, it demands a root pw, that on this wheezy > > > system, does not exist, so it cannot be launched from the menu > > > entry by any pw entered. The pw used for doing a sudo is not > > > accepted. That was my point. > > > > > > Don't put it in the menu's at all if the user cannot use his > > > sudo to get the root rights it needs. > > > > > > I am used to defeating petty attempts to mold linux networking > > > to someones idea of consistency, but which is an abject failure > > > where one's home network, all behind a good router, is all based > > > on the common to all machines /etc/hosts file, with a locally > > > carved in granite hostname per machine. Turning network-mangler > > > loose in that environment is a no networking disaster, so the > > > first thing you have to do on the install reboot, is sudo -i, > > > make the entry's for that machine > > > in /etc/network/interfaces, chmod +i that file, then nuke the > > > link and make a real /etc/resolv.conf, and chmod +i that. If > > > udev hasn't played with things and moved eth0 to something else, > > > thats it. Your networking Just Works(TM) Then at your leasure > > > you can uninstall network-mangler. No use of its burning cpu > > > cycles trying to tear down what you just made immutible. > > > > > > Network-mangler might be of use in the situation where the > > > machine is connected directly to the access modem. Thats for > > > folks who do not understand the need for an isolating, natting, > > > 20 hungry pit-bull guard dogs for a firewall, router. Without > > > that, a windows box is owned 30 seconds after the cat5 is > > > plugged in. The linux box is at risk but its lower. I haven't > > > worried about that since I discovered dd-wrt, which can be > > > reflashed into the better routers. To me, its a transparent > > > gateway to the net. To the net, if no port forwarding is being > > > done, its a cable with an address with nothing on the other end > > > of it. > > > > > > > -------------------------------------------------------------- > > > >---- --- To unsubscribe, e-mail: > > > > trinity-users-unsubscribe(a)lists.pearsoncomputing.net For > > > > additional commands, e-mail: > > > > trinity-users-help(a)lists.pearsoncomputing.net Read list > > > > messages on the web archive: > > > > http://trinity-users.pearsoncomputing.net/ Please remember not > > > > to top-post: > > > > http://trinity.pearsoncomputing.net/mailing_lists/#top-posting > > > > > > Cheers, Gene Heskett > > Cheers, Gene Heskett