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 Sat 14 Dec 2019, 16:06
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Fatdog64-802/801/800 Final [21 May 2019]
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 27 of 30 [448 Posts]   Goto page: Previous 1, 2, 3, ..., 25, 26, 27, 28, 29, 30 Next
Author Message
jamesbond

Joined: 26 Feb 2007
Posts: 3388
Location: The Blue Marble

PostPosted: Mon 11 Nov 2019, 07:51    Post subject:  

@don570:
- thanks, I've updated mtpain to 3.49.19 on the repo too.
- re: sfs loader, let me think about it. Changing text is easy, changing behaviours needs some thinking (and alot of tests)

@jake29:
- I think you solved something that was even a mystery for me - I could never get an M$ mouse to work. Eventually I learnt my lesson NOT to buy M$ products at all. So thanks for figuring this one out. This may be another item for the FAQ.
If you want to load uhid at every boot, you can edit /etc/modules and put a line containing "uhid" (without the quotes) there.

- I built gnome-keyring and push it to the repo. I have not tested it myself though, so I cannot say for sure if it will work. You're welcome to test it if you wish.

@belham2: I never use hidden-ssid because I don't see the point (it offers absolutely no security); so I haven't tested it myself. Does step's suggestion work?

@rufwoof: I presume in order to bring openssh and mc to the initramfs, you need to bring libc and ncurses as well (at the very least), right?

_________________
Fatdog64 forum links: Latest version | Contributed packages | ISO builder
Back to top
View user's profile Send private message 
belham2

Joined: 15 Aug 2016
Posts: 1707

PostPosted: Mon 11 Nov 2019, 08:45    Post subject:  

@step - nothing has worked (even your suggestion). Thank you for attempting to help.

@jamesbond - understand about a "hidden-ssid". Was not doing it for security purposes. Was doing it for self-interest and education (read: kids) purpose/exercise.


Anyway, thank you both for responding.

This weekend's exercise will soon be over (I put Bionicpup64 on their laptops & all is now good). We'll shortly be off the 'hidden-ssid" teaching moment and on to something else.
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3680

PostPosted: Mon 11 Nov 2019, 11:45    Post subject:  

jamesbond wrote:
@rufwoof: I presume in order to bring openssh and mc to the initramfs, you need to bring libc and ncurses as well (at the very least), right?

Yes James. I just copied over the ssh. sftp, scp ... etc files as is from the main fatdog, along with the libs (as indicated by ldd). With localyesconfig (i.e. machine specific modules built into the kernel) along with initramfs_data.cpio (initrd) also built into the kernel, and with all of those libs/bins ... it weighs in at a 11.7MB bzImage (vmlinuz) filesize for me. Pretty good for

automatic wifi net connect at bootup
screen (terminal multiplexing)
mc (file manager and text editor)
ccrypt (encryption)
kexec (directly booting main systems)
openssh (sshfs client or server, ssh client or server, sftp, scp ..etc.).

Quite a extensive set of libs in total, surprising that it all compacts down to such a small 11.7MB vmlinuz filesize.



Found that it was best to NOT use upx on the various bins, have the initramfs_data.cpio built into the kernel and set kernel compression to xz. I've also tweaked (removed) quite a bit out of the kernel build, things like btrfs support etc. I also removed out some/many of the binaries that fatdog adds in, such as dropbear ..etc. For kexec and ccrypt I compiled those using static/stripped musl.

The heavily reduced init (cut down Fatdog init) I'm using (again very specific i.e. for UK keyboard etc) ...
Code:
#!/bin/ash

### bail out unless we're PID 1
[ $$ -eq 1 ] || exit 1

### configuration parameters
DEFAULT_DEVICE_DELAY=0   # seconds - default delay time for devices (so that they are recognised by kernel)
WIFI_ENABLE_TIMEOUT=${WIFI_ENABLE_TIMEOUT:-100}   # unit of 1/10 seconds, max time to wait for wifi connection
KERNEL_POLL_MSECS=${KERNEL_POLL_MSECS:-5000}   # default kernel polling value if unset
BOOT_KEYMAPS=/lib/boot/keymaps

### utilities - decz
# decz - decrements counter, and return true when it is zero
# $1 - name of variable to be decremented
decz() {
   local curval
   eval "curval=\$$1"
   curval=$((curval-1))
   [ $curval -le 0 ] && return 0
   eval "$1=$curval"
   return 1
}

### cmdline processing - waitdev
# wait for devices: sleep a specified number of seconds
process_waitdev() {
   waitdev=${waitdev:-$DEFAULT_DEVICE_DELAY}
   if [ "$waitdev" ]; then
      OIFS="$IFS"; IFS=: ; set -- $waitdev; IFS="$OIFS"
      if [ "$1" ] && [ "$1" -gt 0 ]; then
         echo "Waiting $1 seconds for devices to be ready..."
         sleep "$1"
      fi      
   fi
}

### cmdline processing - net
process_net() {
   [ "$net" = "ask" ] && read -p "net=" net 2>&1
   [ -z "$net" ] && return;
   OIFS="$IFS"; IFS=":"; set -- $net; IFS="$OIFS"
   
   echo -n "Configure network "
   # network type
   case $1 in
      wired)
         # wired:dev:dhcp
         # wired:dev:ip:ip-address:netmask:gateway:dns
         echo -n "on $2 using "
         ifconfig $2 up         
         ;;
      wpa|wpa2)
         # wpa2:ssid:pass:dev:dhcp
         # wpa2:ssid:pass:dev:ip:ip-address:netmask:gateway:dns (gateway and dns is optional)
         echo -n "on $2 ($1) using "
         ifconfig $4 up
         wpa_supplicant -B -C/var/run/wpa_supplicant -Dwext -i$4
         wpa_cli ap_scan 1 > /dev/null
         wpa_cli add_net 0 > /dev/null
         wpa_cli set_net 0 ssid \"$2\" > /dev/null
         wpa_cli set_net 0 psk \"$3\" > /dev/null
         wpa_cli select_net 0 > /dev/null
         while [ "$(wpa_cli status | sed -ne '/wpa_state/ {s/wpa_state=//;p}')" != "COMPLETED" ];
         do
            sleep 0.1; decz WIFI_ENABLE_TIMEOUT && return
         done;
         iwconfig $4 power off # disable power management
         shift 2
         ;;
      adhoc)
         # adhoc:ssid:dev:ip
         # adhoc:ssid:channel:dev:ip:ip-address:netmask:gateway:dns
         ifconfig $4 down
         iwconfig $4 mode ad-hoc
         ifconfig $4 up
         iwconfig $4 essid "$2"
         iwconfig $4 channel $3
         iwconfig $4 power off # disable power management
         shift 2
         ;;
      *)  echo "- wrong types, ignored."
         ;;
   esac
   
   # connection type
   case $3 in
      ""|dhcp)
         echo "dhcp"
         udhcpc -i $2 > /dev/null
         ;;
      ip)
         echo "static ip $4/$5 gw $6 dns $7"
         ifconfig $2 $4 netmask $5
         [ "$6" ] && route add default gw $6
         [ "$7" ] && echo nameserver $7 > /etc/resolv.conf
         ;;
      *)
         echo "unknown method $3, ignored."
         ;;
   esac
   ifconfig lo up   # in any case bring loopback up also   
}

### enable kernel polling
enable_kernel_polling() {
   if ! grep -q block.events_dfl_poll_msecs /proc/cmdline; then # if not explicitly set
      echo $KERNEL_POLL_MSECS > /sys/module/block/parameters/events_dfl_poll_msecs
   fi
}

### cmdline processing - load keymaps and console fonts
process_pkeys() {
   [ -z "$pkeys" ] && [ -e /etc/keymap ] && read pkeys < /etc/keymap
   if [ "$pkeys" ]; then
      # defaults - empty fontmap, iso-8859-1 codepage
      rm -f /etc/fontmap
      echo ISO-8859-1 > /etc/codepage

      keymap=$(ls $BOOT_KEYMAPS/${pkeys}* | sed -ne '1 {s|^.*/||; s|.gz$||; p}')
      if [ "$keymap" ]; then
         echo Console keymap set to $keymap
         echo "$keymap" > /etc/keymap
         zcat "$BOOT_KEYMAPS/${keymap}.gz" | loadkmap
      fi
      echo 850 > /etc/codepage
   fi
}

######################   main   ##########################

# mount core filesystems
/bin/mount -t proc proc /proc # mount /proc first so /proc/self/exe works from now
mount -t sysfs sysfs /sys
if ! mount -t devtmpfs devtmpfs /dev 2> /null; then      # /dev/null may not exist yet
   # if no devtmpfs, use tmpfs and use mdev instead
   mount -t tmpfs tmpfs /dev -o mode=755 # mode 755 is what devtmpfs uses
   mdev -s
fi
[ -f /null ] && rm /null   # Clear up the null file created above
[ ! -e /dev/shm ] && mkdir -p /dev/shm
[ ! -e /dev/pts ] && mkdir -p /dev/pts
[ "$TZ" ] && hwclock -t # set kernel timezone

# debugging and error logging
# comment out next two lines for greater info during bootup
! grep -q showerr /proc/cmdline && exec 2> /dev/initrd.err
grep -q debuginitrd /proc/cmdline && set -x

# enable polling
enable_kernel_polling

# process pkeys (hard build kernel (uk laptop specific) so I created /etc/keymap
# with content of "uk" - so we don't have to specify pkeys=uk kernel boot parameter
process_pkeys

# waitdev and wait for usb disk
process_waitdev

# configure network - after load modules, before basesfs
process_net

export HOME=/root
mount -t devpts non /dev/pts -o ptmxmode=0666,newinstance # pseudo terminal for screen
while :; do
   setsid cttyhack /bin/sh
done

I've tested running both sshfs and ssh server with that and both work OK. sshfs and ssh client also work fine, as does scp copying. My ssh keys are hard stored within the initrd. I have also previously used overlayfs mounting and that worked fine, but I've since dropped overlayfs support out of the kernel config. As a mostly kernel and busybox + some others (mc, openssh ..etc.) it works (very) well IMO. But of course with the limitation of running with busybox level commands, not the full/usual command(s) functionality.

I boot that using grub4dos installed to a usb stick and a menu.lst entry of
Code:
title standard kernel/localyesconfig, cut down fatdog initrd
root (hd0,0)
kernel /bzImage net=wpa2:VMabcd1234-2G:abcd1234:wlan0:dhcp

Once booted, to boot my main fatdog desktop I use a script ...
Code:
#!/bin/ash

CMD="pkeys=uk waitdev=5 "
CMD="$CMD basesfs=ram:uuid:5df8f89e-33d5-4720-b3f2-9c9030a718bd:/fd64.sfs "
CMD="$CMD savefile=direct:multi:uuid:5df8f89e-33d5-4720-b3f2-9c9030a718bd::"
clear
echo Loading Fatdog kernel
kexec -l fatdog-vmlinuz \
      --initrd=fatdog-initrd.xz \
      --command-line="$CMD" >/dev/null 2>&1

clear
echo "Booting Fatdog (multi-session save)"
kexec -e

As far as Fatdog as-is goes, I think a useful extension would be to include kexec as part of the standard build. SFR kindly (thanks SFR) helped me with building that ...
http://murga-linux.com/puppy/viewtopic.php?p=1040675#1040675
That along with other pipelined changes Wink will enable the standard Fatdog's Bulldog to serve as a form of more generic/portable kexec based bootloader (albeit with a much larger initrd size due to having much more in the way of modules/supported hardware).

I built kexec using source from
https://mirrors.edge.kernel.org/pub/linux/utils/kernel/kexec/
./boostrap
./configure
export CC="musl-gcc -I/usr/musl/kernel/include -Dloff_t=off_t"
./configure && make -j

... along with kernel .config changes to activate otherwise deactivated
# CONFIG_KEXEC is not set
# CONFIG_KEXEC_FILE is not set

Yet another extension might be to incorporate a TUI menu Bulldog system. That worked OK when I tried it within the above cut down Bulldog http://murga-linux.com/puppy/viewtopic.php?p=1041340#1041340

EDIT: Noticed that I had two copies of libcrypto.so.1.1 .. removing one of them reduced vmlinuz down to 11.6MB

_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
jake29

Joined: 24 Jul 2015
Posts: 243

PostPosted: Mon 11 Nov 2019, 13:34    Post subject:  

jamesbond wrote:
@jake29:
- I think you solved something that was even a mystery for me - I could never get an M$ mouse to work. Eventually I learnt my lesson NOT to buy M$ products at all. So thanks for figuring this one out. This may be another item for the FAQ.
If you want to load uhid at every boot, you can edit /etc/modules and put a line containing "uhid" (without the quotes) there.

- I built gnome-keyring and push it to the repo. I have not tested it myself though, so I cannot say for sure if it will work. You're welcome to test it if you wish.

Thanks, I was actually going to suggest an FAQ entry for anyone else foolish enough to buy such a device. Ironically, this bluetooth mouse is more stable in Fatdog64 than it was in my testing with Windows. I already have uhid loading at boot, however one remaining issue exists. Putting Fatdog64 into standby and resuming all works fine, but a reboot results in a duplicate entry for the bluetooth mouse - listed under bluetoothctl devices. This causes a random periodic cycle of disconnecting and reconnecting, and is resolved buy removing the older entry - bluetootctl remove <mac> and restarting the bluetooth service.

It is not a big issue as I rarely need to reboot. I will research into it - unsure if it is a bluez bug and maybe already fixed in newer builds. Worst case scenario, it could possibly be resolved with a script running at boot. One last thing, there does not appear to be a Bluetooth settings GUI in Fatdog-802 - could that be implemented at some point in the future?

Thanks for making gnome-keyring, I will test it out and report back.

Last edited by jake29 on Mon 11 Nov 2019, 14:09; edited 2 times in total
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12812
Location: Stratford, Ontario

PostPosted: Mon 11 Nov 2019, 13:45    Post subject:  

@jake: Are you claiming that your problem is specific to MS bluetooth mice and other brands work OK?
Back to top
View user's profile Send private message 
jake29

Joined: 24 Jul 2015
Posts: 243

PostPosted: Mon 11 Nov 2019, 14:04    Post subject:  

rcrsn51 wrote:
@jake: Are you claiming that your problem is specific to MS bluetooth mice and other brands work OK?

From my research into the problem, it's not something exclusive to Microsoft bluetooth mice - it would have happened with any brand. But certainly the Microsoft bluetooth mobile mouse 3600 is often featured in issue reports, however I think that's just due it being one of the more popular bluetooth mice.
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 3388
Location: The Blue Marble

PostPosted: Mon 11 Nov 2019, 19:14    Post subject:  

@jake29: "Putting Fatdog64 into standby and resuming all works fine, but a reboot results in a duplicate entry for the bluetooth mouse - listed under bluetoothctl devices"

Really! Most people (me included) have issues the other way around ==> suspend=problems, reboot=ok. I guess you're the lucky one Smile

Seriously, if a new version fixes the problem then let me know, I'll upgrade bluez.

"One last thing, there does not appear to be a Bluetooth settings GUI in Fatdog-802 - could that be implemented at some point in the future?"

The issue is that nice applet we have in 700 series only works with bluez 4.x. It no longer works in 5.x. We can of course patch it to support bluez 5.x; or we can totally write a new applet using gtkdialog or something (the original applet was patched half-way through already anyway).

We didn't have time for this in 800, so the plan was to have it in 801. And then in 802. And then 810 ... Smile I guess among the rest of the Fatdog team, I'm the only one who use bluetooth; and even then, today I only use rarely (mainly because on my cheap laptop, it interferes with wifi). Thus it gets postponed indefinitely, but I hope to get around my sloth eventually Smile (hopefully before the technology gets replaced by another wireless technology ...)

---

EDIT: I spent one hour trying to build the updated version of the applet we use in 700. Two things:
a) it needs gtk3 (which is not too bad) and another Harry Poetter library (which is a wonder why an applet needs that?), and then
b) it totally DROPS the applet and only provides "bluetooth-sendto" function
Making the entire package totally worthless (I already have a GUI script that can perform "sendto" once the device is connected).

In other words - they killed the standalone applet altogether (they merge the code with Gnome Control Centre or something) back in version 3.8 or something, in 2013 Shocked

Oh well, time to put it back to the backburner for now.

_________________
Fatdog64 forum links: Latest version | Contributed packages | ISO builder
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3680

PostPosted: Mon 11 Nov 2019, 20:05    Post subject:  

Just a observation

Built 1.31.1 busybox (Fatdog currently using 1.27.0.git) as downloaded from busybox.net, using the default build (except setting make menuconfig to use static build).

make distclean defconfig
sed -i "s/.*CONFIG_STATIC.*/CONFIG_STATIC=y/" .config
make busybox

For Fatdog ...
# file ./busybox
./busybox: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, stripped
#

For 1.31.1 ...
# file ./busybox
./busybox: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.2.0, stripped
#

bin sizes ... 2,729,960 bytes (for 1.31.1) versus fatdog's 861,696 bytes

With initrd inside the kernel however the difference in kernel sizes ...

11.82MB versus 11.58MB

... that's with kernel .config set to use xz compression.

And that's with the default 1.31.1 build having more applets.

Seems to be working well, has both bc and dc and everything I've tested so far under kernel 4.14.153 appears to be working OK.

When first booted free -m indicates around half the memory being used for the 1.31.1. of the order 21MB versus 42MB when using Fatdog's busybox. That may however just be 1.31.1 having more cached (I only noticed that 21MB figure and recalled Fatdog's indicating 42MB, didn't really take any mental note of cache).

_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
jake29

Joined: 24 Jul 2015
Posts: 243

PostPosted: Tue 12 Nov 2019, 03:55    Post subject:  

@jamesbond - I can appreciate that a Bluetooth applet is hardly something essential. It would seem the general advice is to avoid bluetooth for mouse or keyboard as it is so open to being unreliable for a number of factors (not even including broadcom vs intel). Having said that, I have now gone for over 3 hours without a disconnection - restarting the bluetooth service seems so far to be key.

I will monitor how things go and maybe report back in a week or so.

I'm considering upgrading to an Intel Wi-Fi 6 AX200 laptop card which features BT 5.0 - currently using an Intel AC 7265 with BT 4.2. I've ordered some aptX BT earbuds and BT 5.0 has 4x the range.

EDIT: Bluez 5.52 has fixed the 'duplicate device entry after reboot' issue for me.
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 3388
Location: The Blue Marble

PostPosted: Wed 13 Nov 2019, 03:13    Post subject:  

jake29 wrote:

EDIT: Bluez 5.52 has fixed the 'duplicate device entry after reboot' issue for me.


Thanks Jake. I'm updating bluez to 5.52.

Quote:
I'm considering upgrading to an Intel Wi-Fi 6 AX200 laptop card which features BT 5.0 - currently using an Intel AC 7265 with BT 4.2. I've ordered some aptX BT earbuds and BT 5.0 has 4x the range.


The current build of bluez-alsa doesn't support aptx, because we don't have the underlying aptx library in it. In theory it would still work but it would fallback to using other codec.

I just updated bluez-alsa build to v 2.0.0 but I would withhold further update as it has a sudden growth spurts after being relatively dormant for months; so I will wait until it stabilises a bit.

@rufwoof: kexec as a standard build.

Thanks for the suggestion. I will keep this in mind, but at the time being I'm reluctant to do so.

@rufwoof: busybox bin sizes.

Thanks for the interesting size comparison. The huge static size comes because you're building a static binary with glibc. You will get a much smaller figure if you use uclibc or musl libc - but they present another set of problems (certain applets won't build etc).

In the usual Fatdog case, we don't compress the initrd at all, so the size difference does show up. The reason why we don't compress it is because we carry the initrd during uptime of the system (unlike standard Puppy, which removes its initrd once the main basesfs has been booted up); hence the entire uncompressed initrd will stay in memory. Thus, we have to make sure that the uncompressed initrd must remain the smallest size as possible - because it is an extra baggage.

_________________
Fatdog64 forum links: Latest version | Contributed packages | ISO builder
Back to top
View user's profile Send private message 
Sage

Joined: 04 Oct 2005
Posts: 5503
Location: GB

PostPosted: Wed 13 Nov 2019, 04:59    Post subject:  

re. above discussions of Bluetooth and, separately, wifi mice and k/b s, inter alia. Might seem like a good idea in certain circumstances, but the remote items all must have a battery inside and experience shows that those tend to peg-out at the most inconvenient times. Best advice may be to avoid?!
Last edited by Sage on Wed 13 Nov 2019, 08:21; edited 1 time in total
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3680

PostPosted: Wed 13 Nov 2019, 06:30    Post subject:  

jamesbond wrote:
@rufwoof: busybox bin sizes.

Thanks for the interesting size comparison. The huge static size comes because you're building a static binary with glibc. You will get a much smaller figure if you use uclibc or musl libc - but they present another set of problems (certain applets won't build etc).

In the usual Fatdog case, we don't compress the initrd at all, so the size difference does show up. The reason why we don't compress it is because we carry the initrd during uptime of the system (unlike standard Puppy, which removes its initrd once the main basesfs has been booted up); hence the entire uncompressed initrd will stay in memory. Thus, we have to make sure that the uncompressed initrd must remain the smallest size as possible - because it is an extra baggage.

Thanks James. Learning. Rebuilt the kernel with the default config and without libc inbuilt the vmlinuz is a much more comparable size.
Quote:
# uname -a
Linux bulldog64 4.14.153 #11 SMP Tue Nov 12 12:02:28 UTC 2019 x86_64 GNU/Linux
# free -m
total used
Mem: 3404 22
busybox 1.31.1 ... Fixes for dc and wget (+ others)
BusyBox v1.31.1 (2019-11-12 11:05:20 UTC) multi-call binary.

Opted to build for 'performance' rather than 'size' and used lz4 compression instead of xz ... yielding a <21MB vmlinuz (versus <12MB). Get's from BIOS to wifi net connected cli extremely quickly Smile

_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
SFR


Joined: 26 Oct 2011
Posts: 1749

PostPosted: Wed 13 Nov 2019, 07:40    Post subject:  

rufwoof wrote:
bin sizes ... 2,729,960 bytes (for 1.31.1) versus fatdog's 861,696 bytes

If it comes for the size and the max. amount of applets, I've got the best results with Buildroot, which uses uClibc-ng.
Code:
# ./busybox --list | wc -l
412
#
# du -k busybox
1128   busybox
#

It's a 32bit binary, though, 64bit one would be slightly bigger.

If you'd like to fiddle with it, here's a quick start:

0. Download and extract Buildroot https://buildroot.org/download.html (I used "Latest stable release: 2019.08.2")

1. Download the attached tarball and extract it to ./package/busybox/
It bumps the BB version from 1.31.0 to 1.31.1, adds a few Fatdog patches and contains a config file with practically everything enabled

2. unset LD_LIBRARY_PATH PKG_CONFIG_PATH CPLUS_INCLUDE_PATH

3. make menuconfig
(to choose the arch and optionally other things to build)

4. FORCE_UNSAFE_CONFIGURE=1 make
(if you're running as root)

It's gonna take a while, since it builds the toolchain first.
When it's finished, you'll find the BB binary in ./output/target/bin/.

Greetings!
busybox.tar.gz
Description 
gz

 Download 
Filename  busybox.tar.gz 
Filesize  32.47 KB 
Downloaded  27 Time(s) 

_________________
[O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource
Omnia mea mecum porto.
Back to top
View user's profile Send private message 
jake29

Joined: 24 Jul 2015
Posts: 243

PostPosted: Wed 13 Nov 2019, 13:30    Post subject:  

jamesbond wrote:
I'm updating bluez to 5.52.

The current build of bluez-alsa doesn't support aptx, because we don't have the underlying aptx library in it. In theory it would still work but it would fallback to using other codec.

I just updated bluez-alsa build to v 2.0.0 but I would withhold further update as it has a sudden growth spurts after being relatively dormant for months; so I will wait until it stabilises a bit.

Thanks James. I've already looked into bluez-alsa aptx support, and it does exist experimentally (and the impression I get is that it will be implemented officially sooner rather than later.) I have compiled this custom version and have it up and running - but have not tested it to date. Please see the 'Contributed Packages' thread post below:

http://murga-linux.com/puppy/viewtopic.php?p=1041032&search_id=1689710725#1041032

Also, regarding gnome-keyring - I've had no success with it so far. Please note, the specific app is launched using --no-sandbox. Is that a contributing factor?

/var/log/messages: (after reboot)
Code:
Nov 12 21:39:22 fatdog64-ccb user.notice kernel: Initialise system trusted keyrings

/var/log/messages: (after running the gnome-keyring shortcuts in /etc/xdg/autostart)
Code:
Nov 13 17:19:47 fatdog64-ccb auth.notice gnome-keyring-daemon[4822]: couldn't access control socket: /tmp/runtime-root/keyring/control: No such file or directory

@Sage - I have been using Microsoft wireless mice for years, and cannot recall any peg-outs other than when the battery went flat (red light warning some time prior). Bluetooth mice do seem a little more challenging however, but then I guess I like a challenge. Smile
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3680

PostPosted: Wed 13 Nov 2019, 18:10    Post subject:  

SFR wrote:
If it comes for the size and the max. amount of applets, I've got the best results with Buildroot, which uses uClibc-ng.

Thanks SFR

_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 27 of 30 [448 Posts]   Goto page: Previous 1, 2, 3, ..., 25, 26, 27, 28, 29, 30 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
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.0928s ][ Queries: 12 (0.0121s) ][ GZIP on ]