BionicPup32 (UPupBB) (27 June 2020)
- Max Headroom
- Posts: 421
- Joined: Wed 28 Jun 2006, 07:17
- Location: GodZone Kiwi
- Contact:
thanx for reply, will try.Max Headroom wrote:popfan, Use isobooter...
http://murga-linux.com/puppy/viewtopic. ... 46&t=67235
;-)K
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Going back to the problem of lifeograph refusing to run,
While experimenting a bit with Gnome MPV which is also GTK3, I discovered that the issue seems to be that icon resources are missing.
The default icon theme for GTK3 is adwaita-icon-theme
If I install this in Bionic32 via PPM, lifeograph from PPM will then run.
There is a cut-down version of this icon theme in Ubuntu, but it drags in other icon theme stuff as "dependencies" and ends up quite large.
We seem to get away with just having libgtk-3 on board to get the browsers running, but if we want Puppy to be able to run other GTK3 stuff in future I think someone will need to take a look at the issue of themes and icons for it. Even with the browsers there are missing icons in the chooser dialogs. Maybe I will start another thread about this, but it will be in the hope that others with better understanding than me can suggest what could be included without adding too much unnecessary bloat.
While experimenting a bit with Gnome MPV which is also GTK3, I discovered that the issue seems to be that icon resources are missing.
The default icon theme for GTK3 is adwaita-icon-theme
If I install this in Bionic32 via PPM, lifeograph from PPM will then run.
There is a cut-down version of this icon theme in Ubuntu, but it drags in other icon theme stuff as "dependencies" and ends up quite large.
We seem to get away with just having libgtk-3 on board to get the browsers running, but if we want Puppy to be able to run other GTK3 stuff in future I think someone will need to take a look at the issue of themes and icons for it. Even with the browsers there are missing icons in the chooser dialogs. Maybe I will start another thread about this, but it will be in the hope that others with better understanding than me can suggest what could be included without adding too much unnecessary bloat.
Oscar in England
Internet Connection Wizard & Wifi [SOLVED]
G'day,
I'm now having to manually run the wizard in this Pup and some other Pups that I felt sure I did not have to do not long ago.
I am changing from an ethernet connection on the home network to wifi.
This does slow down the connecting process a bit so could it be a timing issue - the wizard gives up too soon.
The Simple Network Setup (SNS) wizard is definitely affected, and I'm now trying Frisbee (haven't restarted yet). I think Dougals wizard is also in the 'now won't start at boot-up' camp.
SOLUTION (Cause): I had made links of the wizard config files residing in /etc to my data partition to share the profiles between Pups.
Alas, I now see that the wifi connection process starts up before the data partition is mounted by the script in /root/Startup .
So there is effectively no profile for the wizard to use during booting.
I have to find a way to do this perhaps in one of the Pup's sfs drv files, or create just one for these links to include with each Pup - a l-drv (links drive)
maybe?
David s.
I'm now having to manually run the wizard in this Pup and some other Pups that I felt sure I did not have to do not long ago.
I am changing from an ethernet connection on the home network to wifi.
This does slow down the connecting process a bit so could it be a timing issue - the wizard gives up too soon.
The Simple Network Setup (SNS) wizard is definitely affected, and I'm now trying Frisbee (haven't restarted yet). I think Dougals wizard is also in the 'now won't start at boot-up' camp.
SOLUTION (Cause): I had made links of the wizard config files residing in /etc to my data partition to share the profiles between Pups.
Alas, I now see that the wifi connection process starts up before the data partition is mounted by the script in /root/Startup .
So there is effectively no profile for the wizard to use during booting.
I have to find a way to do this perhaps in one of the Pup's sfs drv files, or create just one for these links to include with each Pup - a l-drv (links drive)
maybe?
David s.
Re: Internet Connection Wizard & Wifi [SOLVED]
David, try putting your data partition mounting script in /etc/init.d instead of /root/Startup. It will start earlier. You can put it to the head of the queue by naming it with a 0 at the beginning, eg: 0_mntmydrv.davids45 wrote:G'day,
I'm now having to manually run the wizard in this Pup and some other Pups that I felt sure I did not have to do not long ago.
I am changing from an ethernet connection on the home network to wifi.
This does slow down the connecting process a bit so could it be a timing issue - the wizard gives up too soon.
The Simple Network Setup (SNS) wizard is definitely affected, and I'm now trying Frisbee (haven't restarted yet). I think Dougals wizard is also in the 'now won't start at boot-up' camp.
SOLUTION (Cause): I had made links of the wizard config files residing in /etc to my data partition to share the profiles between Pups.
Alas, I now see that the wifi connection process starts up before the data partition is mounted by the script in /root/Startup .
So there is effectively no profile for the wizard to use during booting.
I have to find a way to do this perhaps in one of the Pup's sfs drv files, or create just one for these links to include with each Pup - a l-drv (links drive)
maybe?
David s.
Re: Internet Connection Wizard & Wifi [SOLVED]
If you do, remember that scripts in /etc/init.d get called during startup with a parameter of "start" and again at shutdown with a parameter of "stop".jrb wrote:David, try putting your data partition mounting script in /etc/init.d instead of /root/Startup. It will start earlier. You can put it to the head of the queue by naming it with a 0 at the beginning, eg: 0_mntmydrv.
gyro
Start-up items
G'day jrb and gyro,
I had already seen the name "0_" prefix idea and use it with my mount script in Startup for all my Pups.
I've now tried your tip with /etc/init.d in today's first Pup (LxPupSc-19.04 with the 64-bit 5.0.5 kernel) and it is looking fine. I also added to /etc/init.d a script to load a temperature module now that Boot manager is broken in quite a few Pups (most Bionics I think, Sc (Slackos) are still OK, but this is simpler than running Boot manager anyway).
So I'll slowly work through my Pups with this init.d refinement, and add to new Pups as they come along.
David S.
Thanks for the advice.David, try putting your data partition mounting script in /etc/init.d instead of /root/Startup. It will start earlier. You can put it to the head of the queue by naming it with a 0 at the beginning, eg: 0_mntmydrv.
I had already seen the name "0_" prefix idea and use it with my mount script in Startup for all my Pups.
I've now tried your tip with /etc/init.d in today's first Pup (LxPupSc-19.04 with the 64-bit 5.0.5 kernel) and it is looking fine. I also added to /etc/init.d a script to load a temperature module now that Boot manager is broken in quite a few Pups (most Bionics I think, Sc (Slackos) are still OK, but this is simpler than running Boot manager anyway).
So I'll slowly work through my Pups with this init.d refinement, and add to new Pups as they come along.
David S.
Sounds like you're trying to update the BionicPup while you're running BionicPup. You can't do that; it's like sawing off the branch of a tree you're sitting on.
Boot your BionicPup with "pfix=ram" and then copy over the new SFS. Or boot into any Puppy from a LiveCD/LiveDVD/LiveUSB and then copy over the new SFS.
Boot your BionicPup with "pfix=ram" and then copy over the new SFS. Or boot into any Puppy from a LiveCD/LiveDVD/LiveUSB and then copy over the new SFS.
Hi loot.loot wrote:Actually I'm using a fresh iso and delta.
Also, I tried to delete the adrv file, wouldn't let me do that either.
loot.
That's the other branch you'd be sitting on!
All PuppyLinux's have a main puppy_xyz.sfs and a zdrv. The zdrv contains the
kernel modules. So that's two branches you can't cut.
Counting your pupsave file or folder, that makes three.
The more recent Puppies can also have an adrv, an fdrv, and / or a ydrv. So, in total,
in a Puppy, you may have as many as six branches you're not supposed to "cut".
You were considering a career in pruning, I suppose?!
IHTH.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Um....You need EITHER the latest ISO, OR the ORIGINAL ISO plus the latest delta. If you have the latest ISO, you do not need the delta. If you only have the ORIGINAL ISO and the latest delta, you have to apply the delta to the ISO to produce the latest ISO.loot wrote:Actually I'm using a fresh iso and delta.
Also, I tried to delete the adrv file, wouldn't let me do that either.
11-may-2019
iso md5 = 1d3401a56b750cb8589b88015f098fd4 bionicpup32-8.0+5-uefi.iso
see post #1
iso md5 = 1d3401a56b750cb8589b88015f098fd4 bionicpup32-8.0+5-uefi.iso
see post #1
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
-
- Posts: 902
- Joined: Mon 22 Jun 2009, 01:36
- Location: Philadelphia, PA
Got it. Many thanks.peebee wrote:11-may-2019
iso md5 = 1d3401a56b750cb8589b88015f098fd4 bionicpup32-8.0+5-uefi.iso
see post #1
> ls -lt /mnt/home/upup32/
total 230424
drwxr-xr-x 9 root root 4096 May 11 09:39 upupbbsave-may11
-rw-r--r-- 1 root root 203497472 May 11 07:38 puppy_upupbb_19.03.sfs
-rw-r--r-- 1 root root 2585690 May 11 07:32 initrd.gz
-rw-r--r-- 1 root root 24334336 Mar 14 12:43 zdrv_upupbb_19.03.sfs
-rw-r--r-- 1 root root 5528448 Mar 14 11:46 vmlinuz
Dell E6410: BusterPup, BionicPup64, Xenial, etc
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
Intel DQ35JOE, Dell Vostro 430
Dell Inspiron, Acer Aspire One, EeePC 1018P
This is what I followed. But I didn't check of the md5 sum of the new .iso; would that make a difference?Howto:
- download .delta and put into same directory as base .iso
- click on .delta to generate new .iso
- check md5 sumcheck of new .iso against *.iso.md5.txt file contents
- click on new .iso to open it
- copy updated files (usually just puppy*.sfs) to frugal install directory
- close new .iso by clicking on it
- reboot
Source: README.txt, updated 2019-04-15
I read the adrv contains the web browser and can be replaced. Why couldn't I just delete it?
loot.
This all works out-of-the-box for me so far as I can tell, but my needs are fairly simple, except ...
I've gotten used to having to reinstall & reconfigure all my applications every time I want to move to a later Puppy, but JWM config setup seems to have changed out of all recognition, and I can't seem to just copy over the .~/.jwm* files & directory plus the PuppyPin and have my working environment look the same.
Is there a quick/easy way to dump that fcking menu-bar-thing at the top and revert to an old-style icons-on-the-desktop setup?
Or even a slow/painful way?
thanknx
I've gotten used to having to reinstall & reconfigure all my applications every time I want to move to a later Puppy, but JWM config setup seems to have changed out of all recognition, and I can't seem to just copy over the .~/.jwm* files & directory plus the PuppyPin and have my working environment look the same.
Is there a quick/easy way to dump that fcking menu-bar-thing at the top and revert to an old-style icons-on-the-desktop setup?
Or even a slow/painful way?
thanknx
Desktop -> Puppy theme manager -> Original Pup -> Applypaulh177 wrote:Is there a quick/easy way to dump that ..... menu-bar-thing at the top and revert to an old-style icons-on-the-desktop setup?
Or even a slow/painful way?
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64