Thanks, I have put this into /usr/sbin/root2user. Will upload Woof soon.L18L wrote:Working on internationalization, see
http://murga-linux.com/puppy/viewtopic.php?p=583084
I have found a bug fix for permissions of /dev/console.
ApplyAnd fido may use /dev/console tooCode: Select all
chgrp users /dev/console chmod g+w /dev/console
Fixing Fido..
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Fixing Fido..
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Fixing Fido..
Thanks, /etc/sudoers fixed. Will upload Woof soon.L18L wrote:Think this can be reported here....
# sudo
sudo: >>> /etc/sudoers: syntax error near line 8 <<<
sudo: parse error in /etc/sudoers near line 8
sudo: no valid sudoers sources found, quitting
sudo: unable to initialize policy plugin
#
fix:
change line 8 of /etc/sudoers
from
#120110 added /usr/sbin/delayedrun to SYSTEM category. also, see sudo line added to script.
to
# 120110 added /usr/sbin/delayedrun to SYSTEM category. also, see sudo line added to script.
1 space after #
[url]https://bkhome.org/news/[/url]
I've done some work on this.
Big problems with tty's
Fido had no permission to do anything so urxvt wouldn't run, nor sakura or lxterminal.
Had to change /dev/[pt]ty to 666
/dev/pts/ to 777
change ownership of a few to to root:tty to get it working.
I have given fido a home too in /home/fido.
Barry had ownership of /dev/tty1 as fido:tty. This isn't necessary so we can convert to root and back and not break stuff in the one session.
Lots of stuff works but even more doesn't.
More to come.
Big problems with tty's
Fido had no permission to do anything so urxvt wouldn't run, nor sakura or lxterminal.
Had to change /dev/[pt]ty to 666
/dev/pts/ to 777
change ownership of a few to to root:tty to get it working.
I have given fido a home too in /home/fido.
Barry had ownership of /dev/tty1 as fido:tty. This isn't necessary so we can convert to root and back and not break stuff in the one session.
Lots of stuff works but even more doesn't.
More to come.
Puppy Linux Blog - contact me for access
-
- Posts: 1543
- Joined: Mon 22 Feb 2016, 19:43
This topic interests me. I do use run-as-spot sometimes also. Though I think Barry's idea of keeping fido in root makes more sense organization-wise and should be respected, as that's where root and spot also live, instead of creating a new (and boring!) /home directory just for fido. Puppy is wacky, puppy is different, puppy is NOT Ubuntu! Security through obscurity!
BarryK wrote:I don't see why having /root as fido's home is a problem. There is some opposition to it, but as far as I can see that is only due to ingrained learning about how things should be.
When fido is chosen at first shutdown, everything in /root is set to have the correct permissions as required for fido. So, everything in /root is just as it would be as in any other home for fido.
The fundamental understanding is that Puppy is not a multi-user system, at least not in the normal way. Multiple users are accommodated by separate save-files, so there is no conflict in committing /root to be used by fido.
Except however if you want to jump from fido to administrator, and then perform some operation as administrator, in which case files with root permissions could get written into /root.
It might seem perverse, but why not set the administrator's home directory to something other than /root -- say /root0, or /administrator?
Apart from it being weird, I can't see anything wrong with doing that.
The thing is, there is so much dependency on the home directory being /root. So many PET packages have /root hard-coded.
The above common situation being a great pity and really unnecessary since an easy matter to have used $HOME instead of a hard-coded /root. We have tested (and sometimes included) several traditional Puppy dotpets in DebianDog - those coded to use $HOME generally worked without modification, others needed the hard-coded /root altered to $HOME. I suppose some Puppy utility writers had no interest in their apps working in other distributions than Puppy, but why limit a program unnecessarily?Sailor Enceladus wrote:BarryK wrote:The thing is, there is so much dependency on the home directory being /root. So many PET packages have /root hard-coded.
William
Last edited by mcewanw on Fri 01 Apr 2016, 06:52, edited 1 time in total.
github mcewanw
In Puppy /root is $HOME
Try this in a console:
How Puppy works explains it all.
Try this in a console:
Code: Select all
echo $HOME
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Which is the limitation I referred to, which happens to also prevent some otherwise excellent Puppy apps run on other Linux systems.bigpup wrote:In Puppy /root is $HOME
Try this in a console:How Puppy works explains it all.Code: Select all
echo $HOME
And apparently, when it comes to user 'fido' there are moves to make $HOME something other than /root, which will, as I said, require mods to some Puppy gtkdialog-based apps:
01micko wrote:I've done some work on this.
...
I have given fido a home too in /home/fido.
...
Lots of stuff works but even more doesn't.
More to come.
github mcewanw
I can get fido to work without creating a $HOME and this will be the case in the next slacko point release (bugfix for 6.3.0) but going forward I think that Fido needs a home and that home will be in /home/.
Why?
Why?
- Well the current state of fido is a one way street. If you want to convert back to root then fido is left completely broken. That shouldn't happen.
- As William says, why spend time making great software when it only runs in Puppy? I can vouch for PMusic. I have tested and run it very successfully in Slackware proper, with the tray icon and all, in several DEs (including KDE).
- I believe Porteus used (maybe still using?) PBurn as the default burner software.
- The game is changing. Malware is rife. Unsuspecting users are cheap targets. Just because Fido is not running as 'root' does not really offer any protection when he is using the /root as $HOME.
Puppy Linux Blog - contact me for access
I agree with you. But why making an exception to /home/fido for the next slacko point release? No $HOME is going to be confusing while it isn't a complete proof of concept for /home/fido.01micko wrote:I can get fido to work without creating a $HOME and this will be the case in the next slacko point release (bugfix for 6.3.0) but going forward I think that Fido needs a home and that home will be in /home/.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
Well, if you want to make Puppy work like other versions of Linux, I guess you can.
Puppy is different, for reasons that may be getting lost, as people, that do not fully understand the Puppy inner workings, try to add to or delete from how it works.
I understood the way Puppy's file system was setup, had to do with the working of different Pup-modes and how Puppy used memory.
As for Puppy programs working in other Linux operating systems.
That should be up to the programs developer, if he/she wants to provide a version for non-Puppy systems.
How about just offering a program that will work in any Puppy version.
That is not even an easy thing to do.
Puppy is already suffering from code creep and starting to loose in how fast programs run.
Not Puppy specific programs, very much, but I have really seen a slowdown, in how fast a web browser, opens, and runs.
Those things are getting, code creep, big time.
But, they are not Puppy specific programs.
Puppy is different, for reasons that may be getting lost, as people, that do not fully understand the Puppy inner workings, try to add to or delete from how it works.
I understood the way Puppy's file system was setup, had to do with the working of different Pup-modes and how Puppy used memory.
As for Puppy programs working in other Linux operating systems.
That should be up to the programs developer, if he/she wants to provide a version for non-Puppy systems.
How about just offering a program that will work in any Puppy version.
That is not even an easy thing to do.
Puppy is already suffering from code creep and starting to loose in how fast programs run.
Not Puppy specific programs, very much, but I have really seen a slowdown, in how fast a web browser, opens, and runs.
Those things are getting, code creep, big time.
But, they are not Puppy specific programs.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
I assume we still want Fido to be this:
fido is another name for a dog, and is a full non-root login account, as you would get in any other Linux distro. With one peculiarity, it's home directory is /root (which may indeed seem very peculiar to you, but there is a reason for it!). As with other distros, you would use 'su' or 'sudo' to perform administrator activities.
fido always requires administrator password to perform administrator-level operations
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
That isn't the point. TBH, I could dispense with the /home part altoghether, just have fido live at /fido since he is the only user account supported. Actually, I might even do that.bigpup wrote:Well, if you want to make Puppy work like other versions of Linux, I guess you can.
OTOH, I could also make it a choice. "Do you want to have fido live in /root(default) or his own home? There are advantages either way and draw backs either way. Bla.. bla.."
I don't think that is getting lost at all. A user account has never been the goal of Puppy. It's goals are fast/user friendly which we are trying to maintain.bigpup wrote:Puppy is different, for reasons that may be getting lost, as people, that do not fully understand the Puppy inner workings, try to add to or delete from how it works.
I understood the way Puppy's file system was setup, had to do with the working of different Pup-modes and how Puppy used memory.
The point here is that people develop habits. Some good some not good. A lot of that is a matter of opinion too. Another thing, many programs are out there that simply do not run as root and know where their files are. (TOR for instance).bigpup wrote:As for Puppy programs working in other Linux operating systems.
That should be up to the programs developer, if he/she wants to provide a version for non-Puppy systems.
How about just offering a program that will work in any Puppy version.
That is not even an easy thing to do.
I agree. Things like firefox, since it changed UI to Australis have slowed considerably. I'm always on the lookout for something better. If netsurf javascript support improves to the stage where it can capably configure CUPS then that will be my default browser of choice.bigpup wrote:Puppy is already suffering from code creep and starting to loose in how fast programs run.
Not Puppy specific programs, very much, but I have really seen a slowdown, in how fast a web browser, opens, and runs.
Those things are getting, code creep, big time.
But, they are not Puppy specific programs.
Puppy Linux Blog - contact me for access
That is why you modify the program for Puppy, not modify Puppy for the program.Another thing, many programs are out there that simply do not run as root and know where their files are. (TOR for instance)
Tor Browser Package
http://www.murga-linux.com/puppy/viewtopic.php?t=91141
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Have you used Fido? Sounds like you haven't. I have done extensive testing with Fido and hence this topic exists.bigpup wrote:That is why you modify the program for Puppy, not modify Puppy for the program.Another thing, many programs are out there that simply do not run as root and know where their files are. (TOR for instance)
Tor Browser Package
http://www.murga-linux.com/puppy/viewtopic.php?t=91141
Nobody is proposing to change "How Puppy Works". The proposal is to fix fido who is a broken pup. TBH, I could care less because I run as root.
Puppy Linux Blog - contact me for access
request to put users under home in Puppy
Not sure if this is germane, but, over in the Other Distros thread, I've been singing the praises of a Fedora spin named Korora, and pipe-dreaming of a FedoraPup or FedoraDog, and today mcewanw chimed in to agree it would be a desireable thing. It is a Fedora convention that all users other than root go under /home. So, making it a Puppy convention as well might nudge the oven switch toward on. Just sayin'.01micko wrote:[...OTOH, I could also make it a choice. "Do you want to have fido live in /root(default) or his own home? There are advantages either way and draw backs either way. Bla.. bla.." ...
“A wise man can learn more from a foolish question than a fool can learn from a wise answer.†--Bruce Lee
Not Using Fido or Spot
I´ve not had any use for either spot or fido until now.
I´m trying to run a series of scripts collectively called webdl that can be used to download streamed Australian TV like iview.
Its from https://delx.net.au/git/webdl.
Webdl depends on a program called livestreamer.
I´ve downloaded the program livestreamer from the ppm but I can´t get it to run as root.
If I change the user to spot or fido, livestreamer now runs but I get this error:
OSError: [Errno 13] Permission denied: '/root/.cache/webdl'
I´ve changed the permissions to ¨anyone¨ but the program still fails.
Using Linux Mint 18 with a non-root account the program runs fine.
As a programming noob a non-root account in this instance would be useful.
I´m using Lspup_Xenial.
I´m trying to run a series of scripts collectively called webdl that can be used to download streamed Australian TV like iview.
Its from https://delx.net.au/git/webdl.
Webdl depends on a program called livestreamer.
I´ve downloaded the program livestreamer from the ppm but I can´t get it to run as root.
If I change the user to spot or fido, livestreamer now runs but I get this error:
OSError: [Errno 13] Permission denied: '/root/.cache/webdl'
I´ve changed the permissions to ¨anyone¨ but the program still fails.
Using Linux Mint 18 with a non-root account the program runs fine.
As a programming noob a non-root account in this instance would be useful.
I´m using Lspup_Xenial.