Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 25 Sep 2018, 01:33
All times are UTC - 4
 Forum index » House Training » Beginners Help ( Start Here)
installing "irridium browser" in puppylinux
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 2 [29 Posts]   Goto page: Previous 1, 2
Author Message
rufwoof

Joined: 24 Feb 2014
Posts: 2557

PostPosted: Mon 06 Aug 2018, 06:27    Post subject:  

As a long term FireFox user, I moved over to Iridium some weeks back now and love it. Predominately my daily boot is now just OpenBSD + iridium. I've also moved to a more minimalist desktop, run cwm that is a integral part of OpenBSD where you launch a exec prompt with a key combination, type the first two or thee letters of the program you want to run and press Enter. Maximise all windows and flip between them using alt-tab works for me, I also however have a hot corner that shows all windows when you mouse into that corner so you can left mouse to switch to a particular window or middle mouse to close a window. I run X under userid user, and use root to store personal data/docs - that I switch console to (Ctrl-Alt-Fn) and have that set to run tmux (along with mc). Nice colourful consoles that I can scroll, cut/paste and have multiple 'windows' (and panes within windows that you can zoom/unzoom if desired - but which personally I don't use). Leaves pretty much just a blank desktop, so I run iridium with multiple tabs (X/user) maximised, along with cli/root/tmux and multiple 'tabs' (windows) on two separate console sessions and just ctrl-alt-fn flip between them. As I like a visible desktop clock and as iridium is maximised I added a single tab that shows the date/time as its title (I store bookmarks in that tab so if I activate it I also have a list of links). The attached full screen snapshot is pretty much my X desktop i.e. iridium. Iridium's multi-media support seems very good, plays mp4's, views PDF's ...etc. very well.

Iridium is good at improving privacy whilst it works great. OpenBSD add additional security on top of that (Pledge and soon Unveil) https://marc.info/?l=openbsd-misc&m=152872551609819&w=2 With OpenBSD's simple/quick installation (9MB file if you use the http based install) the cli based install takes less than 5 minutes. Their man based documentation is great, specific to the install and any errors in text are considered as a bug comparable to any software bug. And the base OBSD includes the likes of X (more secure version), web server, mail server ...etc.etc. that's all security audited as a whole. Downside is that it does run slower (higher security and doing things properly), but still acceptable on my 10 year old system. They're also sticklers for doing things properly and visibility, so Blobs are out (less broad hardware support). Once bitten however the tendency seems to be that future hardware acquisitions are selected with the target OS in mind (at least it is for me i.e. any hardware I will add in future must work with OBSD for me to even contemplate buying it).
s.png
 Description   
 Filesize   77.65 KB
 Viewed   196 Time(s)

s.png


_________________
( ͡° ͜ʖ ͡°) :wq
Back to top
View user's profile Send private message 
d_vineet


Joined: 06 Aug 2018
Posts: 74
Location: Bharat

PostPosted: Tue 07 Aug 2018, 01:25    Post subject:  

foxpup wrote:
d_vineet wrote:
foxpup wrote:
Code:
ldd /usr/bin/iridium-browser

wrong place
"bin" and not "lib": it is a binary, not a lib Wink


tried it with the following result.
Code:

root# ldd /usr/bin/iridium-browser
   not a dynamic executable

It is a bash script!
I think the binary is in /usr/lib/iridium-browser/
So, try
Code:
ldd /usr/lib/iridium-browser/iridium-brower


Did it.
Below is the result.
Code:

root# ldd /usr/lib/iridium-browser/iridium-browser
   linux-vdso.so.1 =>  (0x00007fff7b9f2000)
   libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fab409a8000)
   libffmpeg.so => /usr/lib/iridium-browser/./libffmpeg.so (0x00007fab4053e000)
   libatomic.so.1 => /usr/lib64/libatomic.so.1 (0x00007fab40336000)
   libdl.so.2 => /lib64/libdl.so.2 (0x00007fab40132000)
   librt.so.1 => /lib64/librt.so.1 (0x00007fab3ff2a000)
   libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007fab3fbf0000)
   libX11-xcb.so.1 => /usr/lib64/libX11-xcb.so.1 (0x00007fab3f9ee000)
   libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007fab3f7cc000)
   libXcomposite.so.1 => /usr/lib64/libXcomposite.so.1 (0x00007fab3f5c9000)
   libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007fab3f3bf000)
   libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007fab3f1bc000)
   libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007fab3efaa000)
   libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007fab3eda4000)
   libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007fab3eb94000)
   libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007fab3e98a000)
   libXtst.so.6 => /usr/lib64/libXtst.so.6 (0x00007fab3e784000)
   libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007fab3e531000)
   libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007fab3e220000)
   libnss3.so => /usr/lib64/libnss3.so (0x00007fab3ded9000)
   libnssutil3.so => /usr/lib64/libnssutil3.so (0x00007fab3dcac000)
   libsmime3.so => /usr/lib64/libsmime3.so (0x00007fab3da80000)
   libnspr4.so => /usr/lib64/libnspr4.so (0x00007fab3d841000)
   libcups.so.2 => /usr/lib64/libcups.so.2 (0x00007fab3d5c1000)
   libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007fab3d239000)
   libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fab3d010000)
   libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007fab3cdcd000)
   libdbus-1.so.3 => /lib64/libdbus-1.so.3 (0x00007fab3cb81000)
   libXss.so.1 => /usr/lib64/libXss.so.1 (0x00007fab3c97d000)
   libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007fab3c772000)
   libatk-1.0.so.0 => /usr/lib64/libatk-1.0.so.0 (0x00007fab3c54d000)
   libatk-bridge-2.0.so.0 => /usr/lib64/libatk-bridge-2.0.so.0 (0x00007fab3c31e000)
   libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007fab3c111000)
   libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007fab3bec5000)
   libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007fab3bbb1000)
   libasound.so.2 => /usr/lib64/libasound.so.2 (0x00007fab3b8b1000)
   libm.so.6 => /lib64/libm.so.6 (0x00007fab3b5a8000)
   libgtk-3.so.0 => /usr/lib64/libgtk-3.so.0 (0x00007fab3ac79000)
   libgdk-3.so.0 => /usr/lib64/libgdk-3.so.0 (0x00007fab3a99e000)
   libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007fab3a77c000)
   libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fab3a3fa000)
   libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fab3a1e4000)
   libc.so.6 => /lib64/libc.so.6 (0x00007fab39e1a000)
   /lib64/ld-linux-x86-64.so.2 (0x00007fab49db3000)
   libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fab39c16000)
   libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007fab39a10000)
   libffi.so.6 => /usr/lib64/libffi.so.6 (0x00007fab39808000)
   libpcre.so.3 => /lib64/libpcre.so.3 (0x00007fab39598000)
   libplc4.so => /usr/lib64/libplc4.so (0x00007fab39393000)
   libplds4.so => /usr/lib64/libplds4.so (0x00007fab3918f000)
   libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007fab38f45000)
   libgnutls.so.30 => /usr/lib64/libgnutls.so.30 (0x00007fab38c15000)
   libavahi-common.so.3 => /usr/lib64/libavahi-common.so.3 (0x00007fab38a09000)
   libavahi-client.so.3 => /usr/lib64/libavahi-client.so.3 (0x00007fab387f8000)
   libz.so.1 => /lib64/libz.so.1 (0x00007fab385de000)
   libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007fab383da000)
   libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fab381b8000)
   libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fab37f9d000)
   libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007fab37cf3000)
   libsystemd.so.0 => /lib64/libsystemd.so.0 (0x00007fab49f3d000)
   libatspi.so.0 => /usr/lib64/libatspi.so.0 (0x00007fab37ac4000)
   libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007fab378ae000)
   libthai.so.0 => /usr/lib64/libthai.so.0 (0x00007fab376a5000)
   libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007fab373fd000)
   libpng12.so.0 => /lib64/libpng12.so.0 (0x00007fab371d8000)
   libxcb-shm.so.0 => /usr/lib64/libxcb-shm.so.0 (0x00007fab36fd4000)
   libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x00007fab36dca000)
   libcairo-gobject.so.2 => /usr/lib64/libcairo-gobject.so.2 (0x00007fab36bc1000)
   libepoxy.so.0 => /usr/lib64/libepoxy.so.0 (0x00007fab368cc000)
   libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007fab366c9000)
   libxkbcommon.so.0 => /usr/lib64/libxkbcommon.so.0 (0x00007fab3648a000)
   libwayland-cursor.so.0 => /usr/lib64/libwayland-cursor.so.0 (0x00007fab36282000)
   libwayland-egl.so.1 => /usr/lib64/libwayland-egl.so.1 (0x00007fab36080000)
   libwayland-client.so.0 => /usr/lib64/libwayland-client.so.0 (0x00007fab35e71000)
   libmirclient.so.9 => /usr/lib64/libmirclient.so.9 (0x00007fab35bca000)
   libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007fab358f8000)
   libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007fab356c9000)
   libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007fab354c5000)
   libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007fab352ba000)
   libp11-kit.so.0 => /usr/lib64/libp11-kit.so.0 (0x00007fab35056000)
   libidn.so.11 => /usr/lib64/libidn.so.11 (0x00007fab34e23000)
   libtasn1.so.6 => /usr/lib64/libtasn1.so.6 (0x00007fab34c10000)
   libnettle.so.6 => /usr/lib64/libnettle.so.6 (0x00007fab349da000)
   libhogweed.so.4 => /usr/lib64/libhogweed.so.4 (0x00007fab347a7000)
   libgmp.so.10 => /usr/lib64/libgmp.so.10 (0x00007fab34527000)
   liblzma.so.5 => /lib64/liblzma.so.5 (0x00007fab34305000)
   libgcrypt.so.20 => /lib64/libgcrypt.so.20 (0x00007fab34024000)
   libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x00007fab33dc6000)
   libdatrie.so.1 => /usr/lib64/libdatrie.so.1 (0x00007fab33bbe000)
   libmircommon.so.7 => /usr/lib64/libmircommon.so.7 (0x00007fab33977000)
   libmirprotobuf.so.3 => /usr/lib64/libmirprotobuf.so.3 (0x00007fab33705000)
   libcapnp-0.5.3.so => /usr/lib64/libcapnp-0.5.3.so (0x00007fab3347d000)
   libmircore.so.1 => /usr/lib64/libmircore.so.1 (0x00007fab33274000)
   libboost_system.so.1.58.0 => /usr/lib64/libboost_system.so.1.58.0 (0x00007fab33070000)
   libprotobuf-lite.so.9 => /usr/lib64/libprotobuf-lite.so.9 (0x00007fab32e3f000)
   libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007fab32c3b000)
   libgpg-error.so.0 => /lib64/libgpg-error.so.0 (0x00007fab32a27000)
   libgraphite2.so.3 => /usr/lib64/libgraphite2.so.3 (0x00007fab32801000)
   libboost_filesystem.so.1.58.0 => /usr/lib64/libboost_filesystem.so.1.58.0 (0x00007fab325e9000)
   libkj-0.5.3.so => /usr/lib64/libkj-0.5.3.so (0x00007fab323c0000)
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 4152
Location: King's Lynn, UK.

PostPosted: Tue 07 Aug 2018, 16:06    Post subject:  

@ d_vineet:-

Sorry to be a while getting back to you. Family 'stuff', I'm afraid; real life's always getting in the way of the Forum!

As promised, here's a MenuEntry .pet for Iridium. If you've installed it from the .deb package, this will definitely work; it does for me.

You'll find it attached to the bottom of this post. I'll do this for you this once; I don't mind doing that. What I suggest you do is to extract the contents of the MenuEntry, and study the structure. If you ever need to make your own in future, just substitute the appropriate bits for whatever package you're making it for. Icons can be found quite easily by doing a Google or DuckDuckGo search for 'PNG icons for xxxxxx'. PNG have a transparent overlay, and look a lot more professional on the desktop.

Once you have your contents inside a suitably-named directory, simply go into the terminal and create a .pet package with the 'dir2pet' command. Others can explain all about this nearer the time if you need help with it.

BTW, that read-out from your last post looks A-OK to me. All dependencies are satisfied; nothing is listed as missing. It's exactly what you would expect to see from running

Code:
ldd


...on a working package.


Mike. Wink
Iridium_browser-MenuEntry.pet
Description  Menu entry for the Iridium browser .deb package
pet

 Download 
Filename  Iridium_browser-MenuEntry.pet 
Filesize  3.43 KB 
Downloaded  16 Time(s) 

_________________
MY PUPPY PACKAGES | 'Thanks' are always appreciated!
--------------------------------------

Back to top
View user's profile Send private message Visit poster's website 
d_vineet


Joined: 06 Aug 2018
Posts: 74
Location: Bharat

PostPosted: Wed 08 Aug 2018, 02:18    Post subject:  

@Mike Walsh,
Thank you very much for your detailed reply and .pet file.
It was initially not working.
When I double-clicked it, Xarchiver could not open it.
Tried to install through dpkg -i <filename>.
But my dpkg seems to be broken.
Code:

dpkg: error: failed to open package info file '/var/lib/dpkg/status' for reading: No such file or directory

Then I fiddled with reinstalling dpkg through PPM. But same issue.
All folders within dpkg are blank.

But now when I double-clicked it, the same .pet file got installed through PPM.
There is now a menu item for iridium and it works.

Don't know what happened.

I will try to prepare a different .pet for another program and learn more about pet files.

Thanks again.
Back to top
View user's profile Send private message 
foxpup


Joined: 29 Jul 2016
Posts: 556
Location: europa near northsea

PostPosted: Wed 08 Aug 2018, 04:12    Post subject:  

dpkg is not something in Puppy. It will not work properly in Puppy.
Puppy has its own package manager: PPM Puppy Package Manager. Clicking a .pet file should have the pet-package installed by PPM.
I don't know why it did not work in the first place.
BTW, I think dpkg is in the Dogs Smile It is even the preferred package manager in the Dogs.
You should know there are Puppy-like Dogs Smile, builds that look like Puppy but are more like the big distro they are based upon (debian, ubuntu ... ).
You will find threads about them in this forum. In time try them out and see if you like them.
BTW, you know that most Puppies (and Dogs) are based on a big distro?

To extract, not to install, a pet you better use Uextract. It is a very usefull swiss knife tool, but not installed in all Puppies.
If it is not in your Puppy (look in the menu or in /usr/share/applications/ ) you can install it with a pet. Google for it to find the topic with download link in this forum.

I will explain a little more about the menu-entries. Otherwise I find it hard to understand what Mike is saying, if I may Mike.
To be in the Menu, there has to be a .desktop file in /usr/share/applications/
You can look there for examples. You can open .destop files as text.
There has to be some lines in it: Exec, Icon, Categories... It can be quite elaborate.
The Categories line determines where the entry will come in the structure of the Menu.
Back to top
View user's profile Send private message 
d_vineet


Joined: 06 Aug 2018
Posts: 74
Location: Bharat

PostPosted: Wed 08 Aug 2018, 04:31    Post subject:  

@foxpup,
OK. I now understand that in puppylinux, any package (not listed in PPM) has to be installed through "unpack utility + .PET" and NOT through "dpkg -i *".
After downloading a .deb file, double-click on it to decompress (maybe Xarchive or Uextract) and then prepare a .PET, dbl-click o it to take care of other things such as menu item.
Pl. correct me if I got it wrong somewhere.
Thanks.
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 4152
Location: King's Lynn, UK.

PostPosted: Wed 08 Aug 2018, 05:09    Post subject:  

@ d_vineet:-

Quote:
@Mike Walsh,
Thank you very much for your detailed reply and .pet file.
It was initially not working.
When I double-clicked it, Xarchiver could not open it.


Huh??! With a .pet package, a single click on the .pet file, and it will install...

Quote:
Tried to install through dpkg -i <filename>.
But my dpkg seems to be broken.

Code:
dpkg: error: failed to open package info file '/var/lib/dpkg/status' for reading: No such file or directory


Then I fiddled with reinstalling dpkg through PPM. But same issue.
All folders within dpkg are blank.


(Oh, boy. Here we go again....) Uh-uh. Nope. You're trying to do things the Ubuntu way, 'cos that's what you've been used to.

As foxpup says, Xenialpup64 is based on Ubuntu 16.04 LTS.....but it's very definitely not Ubuntu. Puppy has its own, very unique way of doing a lot of things.....many of which are because of the fact that Puppy runs as root. (At which everybody else who uses Linux throws up their hands in horror....'Ooh! BIG no-no...')

---------------------------------------

In many cases, .deb packages will install OK in Puppy. Just a single left-click to install, and off it goes. If they won't, try converting the .deb to a .pet, first. If that doesn't work, then it's time to either run

Code:
ldd


...on the binary/executable, or you can do it graphically, through Menu->Setup->Check dependencies installed pkg, in order to find out if anything's missing. If there is.....then it's 'lib-chase' time. (*Joy!*) Rolling Eyes

---------------------------------------

The other main thing you need to know is that rather than standard, 'full' Bash, Puppy uses Busybox. It's what's known as a 'multi-call' binary, meaning that a lot of commands are all sym-linked into a single executable. It comprises a number of 'stripped-down' commands; fr'instance, you won't find certain commands that you may be used to in Ubuntu.

tallboy gives a good answer to this one here.


Mike. Wink

_________________
MY PUPPY PACKAGES | 'Thanks' are always appreciated!
--------------------------------------

Back to top
View user's profile Send private message Visit poster's website 
foxpup


Joined: 29 Jul 2016
Posts: 556
Location: europa near northsea

PostPosted: Wed 08 Aug 2018, 05:16    Post subject:  

d_vineet wrote:
@foxpup,
OK. I now understand that in puppylinux, any package (not listed in PPM) has to be installed through "unpack utility + .PET" and NOT through "dpkg -i *".
After downloading a .deb file, double-click on it to decompress (maybe Xarchive or Uextract) and then prepare a .PET, dbl-click o it to take care of other things such as menu item.
Pl. correct me if I got it wrong somewhere.
Thanks.

No, a .deb should install by just clicking it. The PPM can install .pet, .deb, .txz ... .

If you (have to) do it like that, there may be missing dependencies. Check with ldd.
(The preferred way to install is from within PPM from the lists there because PPM can resolve the deps for you that way.)

If you want to make changes, you can do it manually after install.
For example:
you install irridium browser with .deb by clicking
you go to /usr/share/applications/ and open iridium-browser.desktop as text
in the Exec lines you change 'iridium-browser' to 'run-as-spot iridium-browser' and save
OR...
You can also make a pet, like Mike has done, to make the changes available/known/registered to others or for another time.
Like this:
you install irridium browser with .deb by clicking
you make a directory /mnt/home/menu-iridium
in /mnt/home/menu-iridium you make usr/share/applications/, result: /mnt/home/menu-iridium/usr/share/applications/
you copy the iridium-browser.desktop you find in /usr/share/applications/ into /mnt/home/menu-iridium/usr/share/applications/
you make your changes to it
you go to /mnt/home, rightclick and open a terminal there
you do: dir2pet menu-iridium
you get a pet, menu-iridium.pet
you click menu-iridium.pet, it gets installed
you go look in /usr/share/applications : iridium-browser.desktop is overwritten
you go look in PPM: menu-iridium is installed
OR
you could unpack the deb without installing and make your changes, use dir2pet to make a pet and install the new pet
OR ... ?

I prefer the first way. It is the fastest way, and often these little changes have to be customised to the Puppy version.

BTW, in the PPM:
Update the PPM if you download/install from the lists. The referred repos change/update from time to time.
Choose the old/classic interface to see the pets, debs, txz... you have installed.
BTW, PPM uses what is in directory /root/.packages
Back to top
View user's profile Send private message 
foxpup


Joined: 29 Jul 2016
Posts: 556
Location: europa near northsea

PostPosted: Wed 08 Aug 2018, 05:20    Post subject:  

cross fire with Mike! LOL

Quote:
then it's 'lib-chase' time. (*Joy!*) Rolling Eyes
or depency hell! LOL
Back to top
View user's profile Send private message 
d_vineet


Joined: 06 Aug 2018
Posts: 74
Location: Bharat

PostPosted: Wed 08 Aug 2018, 06:01    Post subject:  

Thank you very much @Mike and @foxpup.
Things are clearer to me now.
Let me try out installing some other packages so that I can get a handle on it.
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 4152
Location: King's Lynn, UK.

PostPosted: Wed 08 Aug 2018, 06:38    Post subject:  

@ d_vineet:-

That's OK, mate. What ya gotta remember is that Puppy is designed to be as simple as possible. It was originally intended for Windows 'refugees', and to keep old hardware useful.

Ex-Windows users are used to everything being simple on the install front. Preferably with GUIs; most of 'em don't even know what a terminal is, never mind how to use one. Puppy's actually a mine-field for Linux 'power-users', who are used to the way the mainstream distros do things. They come to Puppy, very sure of themselves, try to do things the way they expect they should work.....and fall flat on their faces. Because in Puppy, many things just don't work like that.

And then they often start getting snotty, and start complaining & moaning.....

Stick with it. Pup's not hard to get the hang of.


Mike. Wink

_________________
MY PUPPY PACKAGES | 'Thanks' are always appreciated!
--------------------------------------


Last edited by Mike Walsh on Thu 09 Aug 2018, 05:00; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
mikeslr


Joined: 16 Jun 2008
Posts: 2632
Location: 500 seconds from Sol

PostPosted: Wed 08 Aug 2018, 11:10    Post subject:  

Hi d_vineet,

As Mike Walsh and foxpup have mentioned, Puppies can install .debs, txz, tgz, and even rpms just by left-clicking them. But, they may not work "out of the box". You're running Xenialpup64, so installing debs should work most of the time.

And those you can install via Puppy Package Manager mostly do. Open Menu>Setup>Puppy Package Manager. Click the config icon at the top-right (hovering give you a tool-tip as to what's what) and update it. Binary compatible with Ubuntu Xenial Xerus, PPM in Xenialpups access the repos of Ubuntu Xenial Xerus. Type the name of an application you want, or scroll thru the categories. After selecting a package choose Auto install, Or better still, learn about using SFSes and PaDS to create them. SFSes are portables -- don't install and so can't interfere with installed applications. Xenialpup64 can also use AppImages which also don't install.

Even though Xenialpup is binary compatible with Ubuntu Xenial Xerus, it is not identical. For one thing --the easiest to solve-- the Menu categories Puppies use are different than Ubuntu. So after installing a deb the first place to look if it hasn't shown up on the Menu is /usr/share/applications. You can open desktop files in a text editor. You'll see "Categories=" followed by arguments. Ubuntus may start arguments with junk like "Application", "GTK", "KDE". Puppies will start arguments with something like "X-Internet". Easiest solution is to open an application which already appears in the Menu Category where you want your application to appear and cut & paste an argument which worked. Each of multiple arguments must have a ";" at its end, including the last.

Ubuntu often leave off the suffix of an icon. Puppies require them; i.e. iridium_logo must be iridium_logo.png (or jpg, or whatever).

Puppies run as root/administrator. Why should you --the only person using your computer-- have to enter a password in order to do anything? Lately, Chrome-based browsers (and as far a I know only VLC Media Player) can't be run as Root. So naturally, you chose as your first exposure to Puppy Iridium, a Chrome-based browser which you can't install via Puppy Package Manager. Cool Laughing

Just a word of advice -- whenever possible in 'fleshing out' any Puppy, first see what's available on the Addition Software Section for 'your Puppy'. Puppy is really a 'family' of operating systems; the applications built for one may not run in another. As a 2nd choice, use Puppy Package Manager. After editing the /usr/share/applications desktop file (if the application didn't appear on the menu) use Menu>Filesystem>pfind to look for the executable named in the desktop file. It will always be in a 'bin' file, i.e. /bin, /usr/bin, /usr/sbin etc. If it's a script, open the script/wrapper in a text file to see where the actual executable is located and browse to it. If it's a symbolic link, Right-Click and select "Show Target". Right-click the actual executable >select ldd and then choose "missing" from the bottom panel. PPM should/may locate any missing dependency. If not, you may be able to find it on Ubuntu's repos or pkgs.org

But as mentioned before, I recommend PaDS. You can find the latest version, 1.1.3, here: http://murga-linux.com/puppy/viewtopic.php?p=998922#998922. See this post for general instructions. http://murga-linux.com/puppy/viewtopic.php?p=998966#998966. AFAIK, any application which will run as installed can also run as an SFS loaded with the exception of applications which depend on python. Puppies employ a "merge file system" in which the files in the Puppy_yourversion_number.sfs [e.g. puppy_xenialpup64_7.5.sfs] and in your SaveFile/Folder [e.g. Xenialpup64save...] have priority over any other SFS so the python files in an application.sfs aren't used.

To use PaDS with Puppy Package Manager, set PPM to download (not install) the desired application AND all dependencies to download into a folder. That setting is on the Top, Far Right. You can also use your web-browser to download a package into that folder. Name the folder to reflect the application, e.g. iridium_xenial64-1. Right-click the folder and select combine to SFS. Or, see above about using PaDS with its GUI from the Menu. Load the application.sfs. If it doesn't appear on the menu examine /usr/share/applications/xxx,desktop and edit if necessary. To produce an SFS without a menu problem, unload the SFS, Left-click it, copy all the files from the window which opens into another, appropriately named folder, edit the desktop file in that folder then enter IN THE PARENT OF THAT FOLDER the command "dir2sfs EXACT_NAME_OF_FOLDER. A new SFS will be created.

If ldd shows that dependencies are missing, place the initial SFS in an appropriately named folder, BUT change the name of the SFS --any name will do other than that of the folder it's in. Locate any dependencies and place them in that folder. Rerun PaDS.

I used PaDS to create an SFS of the iridium package dancyton found and Mike Walsh's menu pet. Placed both in an appropriately named "sources" folder. Ran PaDS. Ended up with two /usr/share/applications/iridium.desktop files [and two menu entries]. One worked (Mike's), one didn't*. Unloaded the SFS. Removed Mike's pet from the folder. Reran PaDS. Mounted the resulting SFS and copied its files into a folder. Deleted the /usr/.../applications/iridium.desktop file. Ran dir2sfs on that folder. Deleted everything from the "sources" folder. Added the newly built SFS and Mike's pet to that folder and re-ran PaDS. Took about 5 minutes. total.

mikesLr

* If I had guessed that would happen, I could have right-clicked the deb and selected UExtract, deleted the desktop file, created an SFS as above, and added it to the Source folder with Mike's pet, saving a step.
Back to top
View user's profile Send private message 
rufwoof

Joined: 24 Feb 2014
Posts: 2557

PostPosted: Wed 08 Aug 2018, 13:30    Post subject:  

mikeslr wrote:
Puppies run as root/administrator. Why should you --the only person using your computer-- have to enter a password in order to do anything? Lately, Chrome-based browsers (and as far a I know only VLC Media Player) can't be run as Root.

A single program bug, such as in VLC or Chrome ...etc. could open remote access to the userid that the program was run under. Conventional wisdom is that programs that access the internet (external) should be run as user, as then any remote access has to typically find a further exploit to elevate to root - and under most systems that is difficult (otherwise any of the users in a multi-user system/setup could elevate to root). Once root access has been achieved its pretty much game over ... owned. Format/erase the disk, install firmware, see all of the system and local network ...etc. Chrome and VLC are aware that their programs could contain bugs ... pretty highly likely. Depending on the bug they could also be a security issue, ensuring therefore that their programs run as a restricted user and not root is a sensible stance.

A benefit of the nix's is that they prefer to use a central trusted repository, as typically root is used to install programs. Adding in third party repo's or installing software from other sources is yet another means for undesired remote root access to your system.

Its relatively easy to do things such as overwrite the bootloader with a dark hackers version once root access has been achieved. Which could encrypt or block access to the data on disk, or run a sub-layer spy type service ...etc. Maybe even just chaining to the normal system so it looks as though everything is as it should be, but where there's a sub system program running on behalf of the dark hat. It's also easy to "ping out" from within a system, as typically only external originated to internal traffic/access is firewalled/checked, returns from anything originating from the inside are typically let through unchecked. A common dark-hat program is to ask a remote (dark hat's) server what to run next, run that and request another action/command to run. It takes little time for such a program to go from trying actions that fail, to start running things that are refined for that particular OS/setup.

Strictly, running as root on a system that has external (internet) access is only viable if running from a read only device such as a CD/DVD, with no other rw disks attached, no other devices accessible (network/lan) and where local hardware firmware is ro. Very rare instances. Or where root is used only to access local trusted programs/data, no external access at all excepting direct access to a known trusted server such as a repository that serves as a means to install additional trusted software over a encrypted/secure link. If you add a third party repo' say Fred Bloggs repo (server), then you're in effect giving root access of your system to Fred. Debian classify that as creating a FrankenDebian https://wiki.debian.org/DebianSoftware#Footnotes. OpenBSD takes things even further and will not entertain Blobs, i.e. third party binaries where the source code cannot be security QA'd. Hence OpenBSD supports less hardware (such as not supporting Nvidia), nor does OBSD permit kernel modules to be loaded ....etc. OBSD goes to even further lengths to ensure that when remote access to user is achieved its as difficult as possible for a dark hat. They encrypt swap, randomise the kernel and libs, monitor for intrusions, validate that a program stays within the boundaries of what it is expected to do/user (Pledge), and as of the next release come October lock down the filesystem to access only regions the program is expected to access. Memory is wiped after usage, and partitioned into write xor execute (W^X) so a dark hat is restricted from loading (writing) to memory space and then executing what was written. Code compilation is validated for good practice to reduce the likes of buffer overflows/heap spraying ...etc. Whilst no system is truly secure, OBSD raises the bar considerably compared to many of the alternatives, making it more likely that a dark hat would be more inclined to just move on to other easier targets.

_________________
( ͡° ͜ʖ ͡°) :wq
Back to top
View user's profile Send private message 
d_vineet


Joined: 06 Aug 2018
Posts: 74
Location: Bharat

PostPosted: Thu 09 Aug 2018, 00:10    Post subject:  

Thank you for in-depth detailed instructions.
The more I use puppylinux, more I get fascinated about its flexibility yet simplicity.
Yes, it requires tweaking. But I like it because I can tailor what I wish (and don't wish) to have on my box.
I will tryout these instructions and seek help here if get stuck-up.

And again, feel great to be a part of helpful community of puppylinux.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 2 [29 Posts]   Goto page: Previous 1, 2
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Beginners Help ( Start Here)
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1317s ][ Queries: 13 (0.0097s) ][ GZIP on ]