EasyOS version 2.3.2, June 22, 2020
- Cu Chulinux
- Posts: 59
- Joined: Sun 28 Jan 2018, 18:49
- Location: About 180 degrees from Australia
I have a suspicion that the container is trying to use the HDMI sound output instead of the PCI sound output. I do remember having to specify that on inital setting up something but I can't remember if it was Easy or one of the puppies or maybe something else entirely. When back home I will see what I can do in container (which is all still pretty new to me).
I can also try from a USB and see if sound works right off.
I can also try from a USB and see if sound works right off.
There is a dog in Greek Mythology called 'Cerberus'BarryK wrote:I was thinking of naming this super-root "xeus", who was the king of the Greek gods. Unless there is a suitable doggy name...
http://monster.wikia.com/wiki/Cerberus
_________________________________________
Berryboot has converted Barry's Quirky Arm7 to its format.
I was able to install it on my new raspberry pi3.
Quirky Xerus 8.1.4 for Raspberry Pi 2 & 3 (397.7 MiB, 906 downloads) December 27, 2016
https://sourceforge.net/projects/berryb ... z/download
___________________________________________
- Attachments
-
- Cerberus.png
- (247.8 KiB) Downloaded 547 times
- Cu Chulinux
- Posts: 59
- Joined: Sun 28 Jan 2018, 18:49
- Location: About 180 degrees from Australia
I installed to a 32gb usb-3.0 flash drive.
video-info-glx 1.5.3 Sat 9 Jun 2018 on Easy Pyro64 0.9.4 Linux 4.14.44 x86_64X Server: Xorg Driver: radeon
X.Org version: 1.19.1
dimensions: 1920x1080 pixels (508x285 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD REDWOOD (DRM 2.50.0 / 4.14.44, LLVM 3.9.1)
OpenGL version string: 2.1 Mesa 17.0.7
AMD Phenom(tm) II X6 1045T Processor
Core 0: @824 1: @850 2: @812 3: @1113 4: @799 5: @1056 MHz
I installed the usual pets, I'm playing a radio station from
the Seamonkey container.
Works well so far.
video-info-glx 1.5.3 Sat 9 Jun 2018 on Easy Pyro64 0.9.4 Linux 4.14.44 x86_64X Server: Xorg Driver: radeon
X.Org version: 1.19.1
dimensions: 1920x1080 pixels (508x285 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD REDWOOD (DRM 2.50.0 / 4.14.44, LLVM 3.9.1)
OpenGL version string: 2.1 Mesa 17.0.7
AMD Phenom(tm) II X6 1045T Processor
Core 0: @824 1: @850 2: @812 3: @1113 4: @799 5: @1056 MHz
I installed the usual pets, I'm playing a radio station from
the Seamonkey container.
Works well so far.
- Attachments
-
- screenshot.jpg
- (76.2 KiB) Downloaded 483 times
-
- Posts: 247
- Joined: Fri 31 Jan 2014, 14:12
To rufwoof
To rufwoof,
thanks for replying.
I followed your instructions;
"Near the top (first box) use the drop down to select which container you want the sfs active in.
Click the second box labeled 'Load Extra SFS File' and on the next dialog/window, tick your sfs and click 'commit
Now when you start/run that container the SFS should be loaded inside that container"
First, which container do I select, there are THREE
Seamonkey, sh0 and ssh0
Not knowing, I tried sh0, is this one ok?
I then ticked the commit box for my file.
Then, I am confused.
What explicitly do you mean by "start/run that container"
There is no start/run button that I can find.
Do you mean reboot the computer?
I tried rebooting the computer but my file that I loaded
if that's the right word doesn' t show up at all.
My file is still where you told me to put it.,
There's no sh0 container with my tor-browser program
inside showing on the desktop.
There must be a knack to this but I can't find the knack.
Please help me further I've been struggling with this
for many weeks and am climbing the walls here, thanks.
thanks for replying.
I followed your instructions;
"Near the top (first box) use the drop down to select which container you want the sfs active in.
Click the second box labeled 'Load Extra SFS File' and on the next dialog/window, tick your sfs and click 'commit
Now when you start/run that container the SFS should be loaded inside that container"
First, which container do I select, there are THREE
Seamonkey, sh0 and ssh0
Not knowing, I tried sh0, is this one ok?
I then ticked the commit box for my file.
Then, I am confused.
What explicitly do you mean by "start/run that container"
There is no start/run button that I can find.
Do you mean reboot the computer?
I tried rebooting the computer but my file that I loaded
if that's the right word doesn' t show up at all.
My file is still where you told me to put it.,
There's no sh0 container with my tor-browser program
inside showing on the desktop.
There must be a knack to this but I can't find the knack.
Please help me further I've been struggling with this
for many weeks and am climbing the walls here, thanks.
@Rodney
The default install has two icons at the top centre of the screen, one WWW (for seamonkey) the other for console (sh0). Sounds like you've added the sfs to the console (sh0) container, so clicking that top centre console desktop icon will bring up a terminal window and within that session the sfs you've set to load in that container should be loaded/available. I've never used a tor browser, but assuming you can launch it with a terminal command such as 'tor-browser' then entering/typing that command inside the console window and pressing Enter would (after a short delay) launch the tor browser???
The default install has two icons at the top centre of the screen, one WWW (for seamonkey) the other for console (sh0). Sounds like you've added the sfs to the console (sh0) container, so clicking that top centre console desktop icon will bring up a terminal window and within that session the sfs you've set to load in that container should be loaded/available. I've never used a tor browser, but assuming you can launch it with a terminal command such as 'tor-browser' then entering/typing that command inside the console window and pressing Enter would (after a short delay) launch the tor browser???
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
There are some issues with LibreOffice:
http://murga-linux.com/puppy/viewtopic.php?t=113514
ctrl-click to open a hyperlink in the default browser, and online help, both now work.
Note:
I discovered that Zeus is a favourite dog name.
See here:
https://pethelpful.com/dogs/16-Greek-Na ... -Male-Dogs
http://murga-linux.com/puppy/viewtopic.php?t=113514
ctrl-click to open a hyperlink in the default browser, and online help, both now work.
Note:
I discovered that Zeus is a favourite dog name.
See here:
https://pethelpful.com/dogs/16-Greek-Na ... -Male-Dogs
[url]https://bkhome.org/news/[/url]
-
- Posts: 247
- Joined: Fri 31 Jan 2014, 14:12
tor-browser
rufwoof,
All noted above thanks.
I did manage to container Firefox ok.
You should try to-browser, it's a useful program
to hide your ip source address and be incognito,
as you're bounced three times around the world.
I posted on this forum some time ago, that with
Easy you can have anonymity and security
with tor-browser inside a container.
But nobody took me up on the fact that you can't
import your own sfs files, because at present Barry
hasn't allowed this to happen.
If anyone bothered to read it, the caveat is buried
in a sea of words in the help section.
So if it's not listed in PetGet, you can't container it!
And Petget is almost empty anyway.
So my weeks of struggling were all wasted.
Barry take note please and include tor-browser
in the Package Manager for future releases.
Regards.
All noted above thanks.
I did manage to container Firefox ok.
You should try to-browser, it's a useful program
to hide your ip source address and be incognito,
as you're bounced three times around the world.
I posted on this forum some time ago, that with
Easy you can have anonymity and security
with tor-browser inside a container.
But nobody took me up on the fact that you can't
import your own sfs files, because at present Barry
hasn't allowed this to happen.
If anyone bothered to read it, the caveat is buried
in a sea of words in the help section.
So if it's not listed in PetGet, you can't container it!
And Petget is almost empty anyway.
So my weeks of struggling were all wasted.
Barry take note please and include tor-browser
in the Package Manager for future releases.
Regards.
-
- Posts: 247
- Joined: Fri 31 Jan 2014, 14:12
????
Rufwoof,
Further to try t-b, It should be possible to google
and download the sfs for
tor-browser-7.5.3-x86_64.sfs
and pet
tor-browser-6.5.1-i686.pet
Sorry I overlooked your ????
Well if eventually it becomes possible to containerize
tor-browser, as now with SM, you would just click
on the newly created container and t-b will launch.
No need to use terminal, but yes that command works.
If all else fails, there's always Menu/Internet and
usr/share/applications to drag a shortcut to desktop.
Regards.
Further to try t-b, It should be possible to google
and download the sfs for
tor-browser-7.5.3-x86_64.sfs
and pet
tor-browser-6.5.1-i686.pet
Sorry I overlooked your ????
Well if eventually it becomes possible to containerize
tor-browser, as now with SM, you would just click
on the newly created container and t-b will launch.
No need to use terminal, but yes that command works.
If all else fails, there's always Menu/Internet and
usr/share/applications to drag a shortcut to desktop.
Regards.
Just tried it for myself Rodney. Seems to load/work OK for me. Downloaded the 64 bit tor ...sfs file, saving it to /mnt/sdd2/repository/easy-0.9.4. Then used the Menu, Filesystem, Easy Container Management option to select the sh0 choice at the top, and click the SFS button (all this as described earlier), and the next screen showed the tor sfs file as being available, so I clicked to tick it and pressed commit.
Back at the main desktop, I clicked the 'console' icon at the top just right of centre and a terminal window opened. At the terminal
showed /usr/bin/tor-browser
and running
brought up the tor browser connect/configure window. Clicking connect and a browser window was displayed.
Closed the session and the console terminal window (closed the container). Re clicked the console icon again and ran tor-browser command again and it loaded OK again (went through a update before showing the browser window).
Back at the main desktop, I clicked the 'console' icon at the top just right of centre and a terminal window opened. At the terminal
Code: Select all
which tor-browser
and running
Code: Select all
/usr/bin/tor-browser
Closed the session and the console terminal window (closed the container). Re clicked the console icon again and ran tor-browser command again and it loaded OK again (went through a update before showing the browser window).
- Attachments
-
- capture10263.png
- (131.96 KiB) Downloaded 378 times
- Cu Chulinux
- Posts: 59
- Joined: Sun 28 Jan 2018, 18:49
- Location: About 180 degrees from Australia
I am currently using firefox in the shell container, which I used the network wizard to configure my sound card in. Now I have sound in both firefox and seamonkey within this container. Don't know yet how to configure it in the seamonkey container. Maybe try editing the container config file.
I installed the firefox pet in the container in order to run it.
Next step I'll install firefox as root and create a separate container. See if it remembers the sound card setup when I do.
Not sure about this "super root" (super duper user?) idea. It seems a bit contorted to cripple root and then create a new user to do what root is intended to do. I get that running as root is a puppy convention but with the containers and all we are getting away from a single-user single-userspace OS.
A super-root user sounds like something dreamed up for PID0 systemd. After all they need to have access to all things at all times.
BTW I have been checking memory usage between seamonkey and firefox and they are pretty close to the same. Nice job Barry, In windows I've checked this and firefox is easily triple the memory usage of seamonkey.
I installed the firefox pet in the container in order to run it.
Next step I'll install firefox as root and create a separate container. See if it remembers the sound card setup when I do.
Not sure about this "super root" (super duper user?) idea. It seems a bit contorted to cripple root and then create a new user to do what root is intended to do. I get that running as root is a puppy convention but with the containers and all we are getting away from a single-user single-userspace OS.
A super-root user sounds like something dreamed up for PID0 systemd. After all they need to have access to all things at all times.
BTW I have been checking memory usage between seamonkey and firefox and they are pretty close to the same. Nice job Barry, In windows I've checked this and firefox is easily triple the memory usage of seamonkey.
Last edited by Cu Chulinux on Sun 10 Jun 2018, 16:50, edited 1 time in total.
I like to create a sakura (terminal) container, as that way the container is like a separate system that you can log into at the command level and run commands etc.Now I have sound in both firefox and seamonkey within this container. Don't know yet how to configure it in the seamonkey container. Maybe try editing the container config file.
For firefox for instance, after having created a sakura container I run it so that its activated, and then download the firefox...bz2 using the main (non container) seamonkey, and then use the main system to copy that file into the container and then extract it (I use /usr/lib as the location to extract to, so I end up with a /usr/lib/firefox folder with the firefox binary inside that folder). I also copy across the three libpulse type files that Oscar's apulse (64 bit apulse-0.1.11-x86_64.pet) pet installs (I install it to the main system using pet, and copy the /usr/lib/libpul... files to the containers /usr/lib folder).
That (terminal container) way you can also run other things such as sound configuring ...etc. within the container.
Will have to come back and edit the path as not in Easy at present, something like /mnt/wkg/containers/sakura/.session is the root folder, so /usr/lib within that would be /mnt/wkg/containers/sakura/.session/usr/lib To repeat however the container must be running, otherwise that folder is just empty.
The other way for a container such as seamonkey might be to edit the ec-chroot file in that containers / folder (/mnt/wkg/containers/sakura/container ??? (again I'll have to check that path)) so that it just ran sakura instead of seamonkey. Hard code EXE=sakura variable for instance and then close that container session and restart it again so it ran sakura instead of seamonkey ... so you could edit things, and then after having made edits revert back again to running seamonkey.
The other route might be via /mnt/sdd2/containers/ and then the particular container such as sakura folder. I think that is where the current rw overlay files are stored.
- Attachments
-
- libpulse-simple.so.0.gz
- fake .gz /usr/lib apulse file
- (16.61 KiB) Downloaded 112 times
-
- libpulse-mainloop-glib.so.0.gz
- (4.32 KiB) Downloaded 103 times
-
- libpulse.so.0.gz
- (93.67 KiB) Downloaded 116 times
- Cu Chulinux
- Posts: 59
- Joined: Sun 28 Jan 2018, 18:49
- Location: About 180 degrees from Australia
I set up a container for firefox. I copied the etc/asound.conf file from the sakura container where sound works to the firefox container/ Now sound works in the firefox container. I made a snapshot of the container to revert back to initial state when required. Now I am surfing happily in a container.
I also copied the asound.conf file to the seamonkey folder. I could have just copied the asound.conf file from the main system /etc directory. It goes in the container's /mnt/wkg/containers/seamonkey/etc directory (for example, for seamonkey container). I figured this out by seeing what was different between the two container files.
I also copied the asound.conf file to the seamonkey folder. I could have just copied the asound.conf file from the main system /etc directory. It goes in the container's /mnt/wkg/containers/seamonkey/etc directory (for example, for seamonkey container). I figured this out by seeing what was different between the two container files.
Re dd'd the MMC/SD card and started up sh0 container - so a pure/clean version. Installed firefox and no sound. Tried copying across those libs (pulseaudio) I posted earlier and still no sound. Installed Oscar's apulse pet and sound works OK (after a reboot). Ended up installing the pet to both the main system and container, so I'm not really sure as to what actually needs to be installed where to get pulse/firefox working.
Oddly a graphics/screencapture fullscreen doesn't capture the firefox splash screen that shows the version, despite it being visible on screen.
Oddly a graphics/screencapture fullscreen doesn't capture the firefox splash screen that shows the version, despite it being visible on screen.
- Attachments
-
- capture5165.png
- (146.27 KiB) Downloaded 309 times
Not keen on it myself either. I opine that root should just be console/cli only as even running X as root isn't a good idea. Elevate a super-user to root like admin levels hides that behind a dual userid and password being needed to be broken/hacked (makes brute force password cracking more difficult). By all means login to the main desktop gui as that super-user, and where the same userid is below average privileges in containers, but standard root on the main system and a unshare/capsh'd root inside containers ... just ain't right IMO. A heavily capabilities limited root might seem safe, but there's always the chance some corner somewhere is overlooked ... a mknod, cron or file descriptor link etc. type hack for instance. General advice for unshare/capsh is still not to run as root.Cu Chulinux wrote:Not sure about this "super root" (super duper user?) idea. It seems a bit contorted to cripple root and then create a new user to do what root is intended to do. I get that running as root is a puppy convention but with the containers and all we are getting away from a single-user single-userspace OS.
A super-root user sounds like something dreamed up for PID0 systemd. After all they need to have access to all things at all times.
-
- Posts: 247
- Joined: Fri 31 Jan 2014, 14:12
tor-browser
rufwoof and Barry,
Well done, I followed all that you did and it worked for me too.
There is no tor-browser entry in Menu so my impression as
non-technical is that it's "sort of" in a container sh0 and at the
same time not quite in a container.
I can't explain this situation in words, but as the only way
to launch is via a terminal - it's clumsy at best and not
totally satisfactory.
Not at all as I want it to be, right INSIDE a container
and shown in Menu as such, but thank you anyway for all you
have done.
As said the only true way is to download from Package Manager
and do this properly, but whether Barry can arrange to put
tor-browser in PPM is in the lap of the gods.
Best regards.
Well done, I followed all that you did and it worked for me too.
There is no tor-browser entry in Menu so my impression as
non-technical is that it's "sort of" in a container sh0 and at the
same time not quite in a container.
I can't explain this situation in words, but as the only way
to launch is via a terminal - it's clumsy at best and not
totally satisfactory.
Not at all as I want it to be, right INSIDE a container
and shown in Menu as such, but thank you anyway for all you
have done.
As said the only true way is to download from Package Manager
and do this properly, but whether Barry can arrange to put
tor-browser in PPM is in the lap of the gods.
Best regards.
- Cu Chulinux
- Posts: 59
- Joined: Sun 28 Jan 2018, 18:49
- Location: About 180 degrees from Australia
Re: tor-browser
Great that you've got it working Rodney.Rodney Byne wrote:There is no tor-browser entry in Menu so my impression as
non-technical is that it's "sort of" in a container sh0 and at the
same time not quite in a container.
I can't explain this situation in words, but as the only way
to launch is via a terminal - it's clumsy at best and not
totally satisfactory.
Not at all as I want it to be, right INSIDE a container
and shown in Menu as such, but thank you anyway for all you
have done.
Next stage then, open rox filer and navigate to /mnt/sdd2/containers/sh0/.session (you'll have to click the rox eye icon to show hidden files such as .session). Edit the ec-run file and locate the ARGS='' value (7th line up from the bottom) and change it to look like
Code: Select all
ARGS='-c /usr/bin/tor-browser'
After that you could rebadge the desktop icon and name to use a tor icon and name .. and adjust the menu (desktop file) so it shows as a tor browser menu option - but that's more (relatively simple) editing so for now just see if you can get the above working.
A inconvenience is that if you close the terminal window, then the browser would also close as its a child process of that terminal. Also the terminal can't be used as its running the tor browser (perhaps the ARGS value could have a & command appended on the end to put the tor-browser running in the background so commands could be entered into the terminal window - I haven't tried that myself.)
EDIT - just tried adding the & ... doesn't work, container starts up and immediately exits/closes.
Also - don't forget that if you download any files, then in the main session to see those files you'll have to navigate rox to something like /mnt/sdd2/containers/sh0/.session/root/Downloads. I like to use rox bookmarks (usually the third from left menu icon at the top of a rox filer window) to bookmark the /mnt/sdd2/containers/sh0/.session/ folder which in effect opens the / (root) folder of the container.
Last edited by rufwoof on Mon 11 Jun 2018, 14:01, edited 1 time in total.
Re: tor-browser
Early days for that sort of thing yet Rodney. Easy Pyro is pretty much all locally (Barry) compiled, and even if a sfs were available it would only get loaded into the main session - and not being part of the main q.sfs, but a sfs loaded on top of that, it wouldn't be 'seen' inside containers. A tor browser inside a container sfs would need to be built differently (different paths/icons/desktop file content etc.) I believe.Rodney Byne wrote:As said the only true way is to download from Package Manager and do this properly, but whether Barry can arrange to put tor-browser in PPM is in the lap of the gods.
What might arise as Easy moves out of beta is perhaps a general provision of sfs's that add a ready to go container for a particular program such as a tor browser inside a container. All part of the story yet to be written/told. And things could all change i.e. Barry might decide on alternative implementations of containers that could invalidate any sfs's created up to that point.
Sounds like mc that runs script type actions when you click things (other than changing directory etc.) perhaps is looking at the wrong paths when it spawns such actions. i.e. probably needs some configuration changes work to get it working properly in a container environment.Cu Chulinux wrote:mc will not reliably run in the sh0 container. I installed the pet in the container and mc runs, then the terminal window dies as soon as I try to do anything other than change directory. Or alternately the terminal dies as soon as mc is run.
It runs fine non-containered.
Only ever used mc lightly myself. I either use command line (ssh, scp ...etc.) when I access remote boxes, or activate X forwarding and use sshfs to remote mount and use a conventional file manager ... as thought the remote box was just another folder/directory - whenever I want to have dual panes to compare or move multiple files around.