BionicPup32 (UPupBB) (27 June 2020)

A home for all kinds of Puppy related projects
Message
Author
User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#76 Post by rcrsn51 »

petihar wrote:Bonjour, peebee, rcrsn51 and everyone... I can't get the bluetooth to work either ....
I have bluetooth working. But I'm running it on the platform for which the application was originally developed.

Trying to do otherwise is a waste of time.

tlchost
Posts: 2057
Joined: Sun 05 Aug 2007, 23:26
Location: Baltimore, Maryland USA
Contact:

#77 Post by tlchost »

petihar wrote:Bonjour, peebee, rcrsn51 and everyone...

I can't get the bluetooth to work either and, I think this functionality is sorely lacking in this UPupBB otherwise so successful.

tlchost wrote :
If I really need to use the bluetooth headphones and/or speaker, I'll simply use windows, where they work out of the box.
What a shame to have to go through windows to use a bluetooth accessory :x .
It's not a shame...one needs to realize that all of the OS available to use are simply tools...none of them do everything and everything well. It's akin to a carpenter shop or a blacksmith shop....those folks have numerous tools with the same name but different capabilities....While the smith may have his favorite hammer, his favorite tongs, you'd be hard pressed to find a smith that will only use one hammer or one set of tongs,,,he knows from experience that he needs multiple tools

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#78 Post by peebee »

Mike Walsh wrote:One small problem with pMount (yes, another one I'm afraid!). I've set the pMount window to have the tabs for categories, instead of all in one window. Strangely, the external USB HDD is not showing up under the 'usbdrv' tab.....it's showing-up under 'optical'? Which probably explains why it wasn't showing in the main, single window.....
Hi Mike

Can you post the outputs from the probedisk and probepart commands please?

Thanks
peebee

@ITSMERSH - get the new .iso .....
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

#79 Post by Mike Walsh »

Hi, peebee.
peebee wrote:Can you post the outputs from the probedisk and probepart commands please?
Here ya go:-

@probedisk:-

Code: Select all

# probedisk
/dev/sda|drive|ATA WDC WD5000AAKX-0
/dev/sdb|drive|ATA KingSpec KSD-PA2
/dev/sdc|usbdrv|Seagate Expansion Desk
/dev/sdd|usbdrv|Generic USB SD Reader
/dev/sde|usbdrv|Generic USB CF Reader
/dev/sdf|usbdrv|Generic USB SM Reader
/dev/sdg|usbdrv|Generic USB MS Reader
/dev/sr0|optical|ATAPI iHAS124   F
Probepart:-

Code: Select all

# probepart
/dev/sda1|ext3|251871232
/dev/sda10|ext3|313843712
/dev/sda11|swap|12580864
/dev/sda2|ext3|52430848
/dev/sda3|ext3|52428800
/dev/sda5|ext3|83886080
/dev/sda6|ext3|52428800
/dev/sda7|ext3|52428800
/dev/sda8|ext3|52428800
/dev/sda9|ext3|52428800
/dev/sdb1|ext4|41943040
/dev/sdb2|swap|6291456
/dev/sdc1|ext3|2147483648
/dev/sdc2|ext3|3221225472
/dev/sdc3|swap|25165824
/dev/sr0|none|2097150
I hope you know what you're looking for..!


Mike. :wink:

tlchost
Posts: 2057
Joined: Sun 05 Aug 2007, 23:26
Location: Baltimore, Maryland USA
Contact:

Remastering upupbb

#80 Post by tlchost »

I would like to remaster upupbb...but I don't know how to:
1. answer the question about compressing one file(fdriv?????)
2. what to do with the sfs files in the distro...do they get copied to the directory the remaster script creates?

Thanks in advance for pointing me in the right direction.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Re: Remastering upupbb

#81 Post by peebee »

tlchost wrote:I would like to remaster upupbb...but I don't know how to:
Thanks in advance for pointing me in the right direction.
Can anybody else help? I've never done a remaster....
@tlchost - why don't you try it and tell us all what happens :wink:
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
rockedge
Posts: 1864
Joined: Wed 11 Apr 2012, 13:32
Location: Connecticut, United States
Contact:

#82 Post by rockedge »

I have made many re-masters that require some files from /etc that the remaster scripts that are stock with Puppies seem to leave behind and not copy into the remaster file structure before iso creation. So I began to use this as a guide line and did mine manually. One tip is to reboot just before using a remaster script to ensure the save folder/file is complete. If in your case this is applicable, I also had to ensure that files like /etc/passwd are transferred complete with any users added (i.e. www-data or mysql to install stock Apache and Mysql or MariaDB)

this is what I use as a guide. http://www.smokey01.com/coolpup/remastering.html

User avatar
rockedge
Posts: 1864
Joined: Wed 11 Apr 2012, 13:32
Location: Connecticut, United States
Contact:

#83 Post by rockedge »

if anyone is interested I have compiled a kernel 4.16.9 PAE enabled 32 bit
using the kernel-kit and woof-CE to build a Bionic Pup 18.05 using this newly built 4.16.9 kernel.

I could make available just the kernel and sources,headers,etc..... or I could upload and make a link to get the ISO and devx for it.

may save some time for someone....it took about 8 hours to compile the kernel and run woof-CE to completion.

I am using it with palemoon installed to type this up. I think one could add the adrv.sfs with the Light browser to the frugal directory and have an instant browser from the peebee Bionic

Code: Select all

Linux Kernel: 4.16.9 (i686)
Kernel Version: #1 SMP Thu May 17 22:54:23 EDT 2018
Build GCC: 7.3.0
PAE Enabled: Yes

Kernel Command Line:
psubdir=BB-RE-4169 pmedia=atahd pfix=fsck

Distro: UPupBB 18.05
Window Manager: JWM v2.3.7
Desktop Start: xwin jwm

Development:
 Bash: 4.4.19
 Geany: 1.29
 Gtkdialog: 0.8.4
 Perl: 5.26.1
 Python: 2.7.15rc1
 Yad: 0.40.3 (GTK+ 2.24.32)
 --
 busybox: 1.28.3
 dhcpcd: 6.7.1
 Devx GCC: (Ubuntu 7.3.0-16ubuntu3) 7.3.0
 Glibc: 2.27
 OpenSSL: 1.1.0g  2 Nov 2017, built on: reproducible build, date unspecified
 wpa_supplicant: 2.6
Attachments
Bionic-Screenshot.png
(46.36 KiB) Downloaded 136 times
Last edited by rockedge on Sun 20 May 2018, 23:59, edited 1 time in total.

watchdog
Posts: 2021
Joined: Fri 28 Sep 2012, 18:04
Location: Italy

Re: Remastering upupbb

#84 Post by watchdog »

tlchost wrote:I would like to remaster upupbb...but I don't know how to:
1. answer the question about compressing one file(fdriv?????)
2. what to do with the sfs files in the distro...do they get copied to the directory the remaster script creates?

Thanks in advance for pointing me in the right direction.
I have remastered other puppies and I think it's a not so good deal. There is an authomated script in Menu-Setup with many choices: it depends on your needs what choices to choose. The main problem is a manual review of /etc and /root dirs for removing or adding many wanted or unwanted configuration files with attention to privacy (the remastered puppy can be privately used or reditributed...). You have to unload the used sfs before remastering because they are copied in main sfs file of the remastered pup which can become very heavy. You have alternatives to remastering. For example put in a dir all downloaded and installed packages and run in that dir the alien2puppy script to make a single sfs which you can load to use your software (you can copy it the adrv.sfs and build a new iso without changing the main sfs file).

tlchost
Posts: 2057
Joined: Sun 05 Aug 2007, 23:26
Location: Baltimore, Maryland USA
Contact:

Re: Remastering upupbb

#85 Post by tlchost »

tlchost wrote:I would like to remaster upupbb...but I don't know how to:
1. answer the question about compressing one file(fdriv?????)
2. what to do with the sfs files in the distro...do they get copied to the directory the remaster script creates?

Thanks in advance for pointing me in the right direction.
Thanks for all the suggestions...although none of them, as far as I can tell, answered the two questions I posed.

User avatar
rockedge
Posts: 1864
Joined: Wed 11 Apr 2012, 13:32
Location: Connecticut, United States
Contact:

#86 Post by rockedge »

2. what to do with the sfs files in the distro...do they get copied to the directory the remaster script creates?
If the SFS files are loaded at remaster time, they will be written in to the remastered version as part of the file structure. They will be in this way included in the new puppy.*.sfs

1. answer the question about compressing one file(fdriv?????)
do mean creating an sfs? or a query from the remaster script?

User avatar
recobayu
Posts: 387
Joined: Wed 15 Sep 2010, 22:48
Location: indonesia

#87 Post by recobayu »

rockedge wrote:if anyone is interested I have compiled a kernel 4.16.9 PAE enabled
using the kernel-kit and woof-CE to build a Bionic Pup 18.05 using this newly built 4.16.9 kernel.

I could make available just the kernel and sources,headers,etc..... or I could upload and make a link to get the ISO and devx for it.

may save some time for someone....it took about 8 hours to compile the kernel and run woof-CE to completion.

I am using it with palemoon installed to type this up. I think one could add the adrv.sfs with the Light browser to the frugal directory and have an instant browser from the peebee Bionic

Code: Select all

Linux Kernel: 4.16.9 (i686)
Kernel Version: #1 SMP Thu May 17 22:54:23 EDT 2018
Build GCC: 7.3.0
PAE Enabled: Yes

Kernel Command Line:
psubdir=BB-RE-4169 pmedia=atahd pfix=fsck

Distro: UPupBB 18.05
Window Manager: JWM v2.3.7
Desktop Start: xwin jwm

Development:
 Bash: 4.4.19
 Geany: 1.29
 Gtkdialog: 0.8.4
 Perl: 5.26.1
 Python: 2.7.15rc1
 Yad: 0.40.3 (GTK+ 2.24.32)
 --
 busybox: 1.28.3
 dhcpcd: 6.7.1
 Devx GCC: (Ubuntu 7.3.0-16ubuntu3) 7.3.0
 Glibc: 2.27
 OpenSSL: 1.1.0g  2 Nov 2017, built on: reproducible build, date unspecified
 wpa_supplicant: 2.6
Yes, please.. where is the download link?

User avatar
rockedge
Posts: 1864
Joined: Wed 11 Apr 2012, 13:32
Location: Connecticut, United States
Contact:

#88 Post by rockedge »

uploading the iso, devx, and a palemoon adrv-upupbb.sfs to add before booting right now!

When the uploads are finished I will post the links......

User avatar
rockedge
Posts: 1864
Joined: Wed 11 Apr 2012, 13:32
Location: Connecticut, United States
Contact:

#89 Post by rockedge »

here is the link for upupbb-18.05-k4169.iso 32 bit ->

MD5 : 32deba6072976243844b9ae34520c1c1 upupbb-18.05-k4169.iso

https://drive.google.com/open?id=15qCK3 ... alEYeWst0g

the link for the devx ->

MD5 : dbbe72129a31b4d58514d1a0ad6d233e devx_upupbb_18.05-k4169.sfs

https://drive.google.com/open?id=19Zy0q ... m_kxQMZwC1

this is an adrv_upupbb_18.05.sfs of the Palemoon browser v27.9.2 ->

https://drive.google.com/open?id=1l11QK ... YUYv9_Ko9g


the adrv for Mozilla Light browser one can retrieve from peebee's ISO, just
place the adrv sfs file in the directory with the main puppy OS files.
Last edited by rockedge on Mon 21 May 2018, 00:00, edited 1 time in total.

ITSMERSH

#90 Post by ITSMERSH »

Thanks for all the suggestions...although none of them, as far as I can tell, answered the two questions I posed.
Here's what will be copied into the build directory on a remaster:

Code: Select all

   for F in ${ZDRVSFS} vmlinuz initrd.gz  grldr *efi* *EFI* *.c32 *.sh *.lst *.xpm *.jpg *.png *.bin *.cfg *.msg *.16 *.HTM* *.ICO *.INF help
   do
     #130223 -n means do not override an existing file... 130304 hmmm, -n not supported, use -u ...
     [ -e "$F" ] && cp -a -u $F $WKGMNTPT/puppylivecdbuild/
     sync
   done
As one can see: .sfs is NOT listed. So, extra SFS apart from A-F-Y-Zdrv SFS Modules will not be copied.

This is what the remaster script will keep, if chosen to customize the new SFS:

Code: Select all

 cp -af /etc/codepage /tmp/etc/
 cp -af /etc/fontmap /tmp/etc/
 cp -af /etc/keymap /tmp/etc/
 cp -af /etc/mousedevice /tmp/etc/
 cp -af /etc/eth0mode /tmp/etc/
 cp -af /etc/eth1mode /tmp/etc/
 cp -af /etc/resolv.conf /tmp/etc/
 rm -f /tmp/etc/localtime #a symlink
 cp -af /etc/localtime /tmp/etc/
 cp -af /etc/TZ /tmp/etc/
 cp -af /etc/cdburnerdevice /tmp/etc/
 cp -af /etc/dvddevice /tmp/etc/
 cp -af /etc/modemdevice /tmp/etc/
 cp -af /etc/securetelnetrc /tmp/etc/
 cp -af /etc/modules.conf /tmp/etc/
 cp -af /etc/modprobe.d /tmp/etc/ #101020
 cp -af /etc/rdesktoprc /tmp/etc/
 cp -af /etc/windowmanager /tmp/etc/
 cp -af /etc/X11/xorg.conf /tmp/etc/X11
 cp -af /etc/network-wizard /tmp/etc/
 cp -af /etc/simple_network_setup/* /tmp/etc/simple_network_setup/

User avatar
davids45
Posts: 1326
Joined: Sun 26 Nov 2006, 23:33
Location: Chatswood, NSW

Bionic-18.04 with 64-bit 4.16.9 kernel

#91 Post by davids45 »

G'day rockedge,

I saw your post about putting a new kernel into BionicPup.

Is this new kernel 32-bit or 64-bit?

By coincidence, I've just replaced the kernel in a Bionic-18.04+6 with the 64-bit kernel peebee posted as a link in his LxPupSc thread, where - if I understand some of what he's doing - he's using a 64-bit slacko kernel in a 32-bit slacko-base Pup, with his choice of window manager and file manager.

I prefer the 'normal' JWM+Rox set-up which, luckily for me, peebee has retained in his Pups. So I can quickly set up his new Pups to my liking.

He posted simple steps to replace the kernel in a frugal Pup and recalling that I'd made several Pups with distributionally mixed kernels with software from forum member wiak, I thought I'd add the 64-bit Sc kernel to a 32-bit Bionic Pup.
A manual frugal seems to be running quite nicely (using it now).

The attached screenshot is of this 32+64 Bionic-Slack Pup which seems unaffected with its mixed-bit genesis. All my pinboard icons of sfs-links-apps work plus a couple of normal sfs or pets added that I haven't been able to linkify yet.

I haven't got as far as trying to turn this file collection into an iso nor have I tried to remaster it, but these would be on my 'bucket-list' for this exercise.

Any suggestions as to what I should do to thoroughly check this hybrid?

David S.
Attachments
bionic-with-64bit-slacko-kernel.jpg
replaced zdrv and vmlinuz in Bionic with those in the 64-bit kernel, made the new frugal, and added apps after booting; so far, so good.
(95.91 KiB) Downloaded 1500 times

User avatar
rockedge
Posts: 1864
Joined: Wed 11 Apr 2012, 13:32
Location: Connecticut, United States
Contact:

#92 Post by rockedge »

@davids45
Is this new kernel 32-bit or 64-bit?

Hello , Sorry I forgot to include that info! This a 32bit version.

I like what I see in the screenshot. That is a cool trick! I am going to compile a 64 bit kernel and try it out using this 32 bit iso as a base...........

stay tuned.....

User avatar
rockedge
Posts: 1864
Joined: Wed 11 Apr 2012, 13:32
Location: Connecticut, United States
Contact:

#93 Post by rockedge »

could anyone point me in the direction of tips to swap out kernels....I have compiled a 64 bit BIG 4.16.10 kernel and I am going to swap it into a Bionic 32 bit base ........

peebee and davids45 have gotten me interested in going in this direction for some experimentation.......
Last edited by rockedge on Mon 21 May 2018, 16:08, edited 1 time in total.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#94 Post by peebee »

rockedge wrote:could anyone point me in the direction of tips to swap out kernels
http://www.murga-linux.com/puppy/viewto ... 511#992511

My kernels have no firmware in zdrv - its in the fdrv.....depending on how you've built your kernel you may or may not need the fdrv.....

The only "problem" I know of in using a 64-bit kernel is that any kernel drivers have to be built on a 64-bit system with a compatible devx and kernel_sources

....and any such drivers provided as .sfs gets more complicated as the driver has to be 64-bit but any utilities have to be 32-bit (e.g. nvidia).
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
rockedge
Posts: 1864
Joined: Wed 11 Apr 2012, 13:32
Location: Connecticut, United States
Contact:

#95 Post by rockedge »

peebee wrote: My kernels have no firmware in zdrv - its in the fdrv.....depending on how you've built your kernel you may or may not need the fdrv.....

The only "problem" I know of in using a 64-bit kernel is that any kernel drivers have to be built on a 64-bit system with a compatible devx and kernel_sources
thank for the info! I seem to have successfully built a 64 bit kernel 4.16.10 on a 32 bit Bionic 18.05 kernel 4.16.9 PAE enabled.

I will try it out by swapping it in and I will also build a Puppy using woof-CE with this kernel.

Who knows if it will work at all....not sure what it will do..but I do have a 64 bit machine standing by....

Post Reply