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 Sun 26 Jan 2020, 18:21
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
DebianDog - Jessie (21 June 2017)
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 28 of 68 [1013 Posts]   Goto page: Previous 1, 2, 3, ..., 26, 27, 28, 29, 30, ..., 66, 67, 68 Next
Author Message
rufwoof


Joined: 24 Feb 2014
Posts: 3717

PostPosted: Sat 23 Jan 2016, 16:44    Post subject: Master PDF Editor  

I really like this little program - master pdf editor https://drive.google.com/file/d/0B4MbXu8cvE_WMUlrZ0NDNkFXMDA/view?usp=sharing. That's a Debian Wheezy squashfs that I created to run under DD. Contains the qt libs to run etc.

I'm a bit lost however. In that squashfs I've created a /root with some configuration options in .config sub-directory, however when I 'activate' that squashfs from a 'live' session it doesn't seem to 'copy' those /root files in when activated.

Not really something I would repeatedly load/activate anyway, more inclined to just copy the content in and save that into the core. But it would appear I've still yet to learn things about DD and squashfs loading. Might be because I didn't use a patched/updated DD Wheezy, just ran it straight out of the ISO as is. I believe I recall seeing some postings about sfs loading being updated, so may no longer be a issue.

masterpdfeditor is great in that you can edit pdf's to add in or remove pages. You can add/remove attachments, highlight text, add text, drawings ...etc. Neat little package IMO and I like to keep one alongside Libre. But couldn't find masterpdfeditor in Synaptic.
mpdf.jpg
 Description   
 Filesize   32.06 KB
 Viewed   1174 Time(s)

mpdf.jpg


_________________
( ͡° ͜ʖ ͡°) :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 
fredx181


Joined: 11 Dec 2013
Posts: 4257
Location: holland

PostPosted: Sat 23 Jan 2016, 17:49    Post subject:  

Hi Toni, rufwoof, All,

Thanks to rufwoof's comments about lz4 compression I became curious and explored how to make it work.
Installed from Stretch: squashfs-tools and also linux-image from here:
https://packages.debian.org/stretch/linux-image-4.3.0-1-686-pae
Creating a lz4 compressed squashfs worked fine, but booting or mounting didn't.
Finally found that the kernel .config needs enabled:
Code:
CONFIG_SQUASHFS_LZ4=y

Which isn't the case for the linux-image-4.3.0-1-686-pae.
So got the original Debian source of linux-image-4.3.0-1-686-pae and compiled it with squashfs_lz4 enabled.
Tested only on Jessie:
The archive contains:
vmlinuz1-43
initrd1-43.xz
initrd1-43.img
initrd-43.img
43-kernel-4.3.3-lz4.squashfs
To test, place them in the "live" folder and edit menu.lst accordingly.

See more info e.g. boot examples in the included ReadMe

Also included in the archive the .deb packages for linux-image and linux-headers.

The size of a lz4 compressed squashfs is a lot larger than when using xz, but I noticed clearly a difference in boot time and running speed. (made a remaster .squashfs lz4 compressed)
Creating a lz4 squashfs with mksquashfs is blazing fast!!!

Download: kernel-4.3.3-lz4+aufs+squashfs-tools.tar.gz:
https://googledrive.com/host/0ByBgCDlZZ8K5NlYzQmM2cTh1Uk0/kernel-4.3.3-lz4+aufs+squashfs-tools.tar.gz

Edit:Included also is aufs-module separate .deb package, required when you install linux-image .deb.
(as aufs is not included in the Debian kernel anymore, replaced now by 'overlayfs', live-boot v5 uses that)

Edit2: Re-uploaded kernel-4.3.3-lz4+aufs+squashfs-tools.tar.gz.
As I was focused to much on lz4 support I made mistake, should be fine now.
See above url link.

Fred

Last edited by fredx181 on Sun 24 Jan 2016, 19:14; edited 1 time in total
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3717

PostPosted: Sat 23 Jan 2016, 18:06    Post subject:  

I run on a single core Celeron D Fred and LZ4 was noticeably quicker. A couple of weeks back I decided to net (PXE) boot my son's 4 core and created a 160MB test file to see if four cores were correctly being used when monitoring htop. As the pup was running in ram it ate through the 160MB in no time - barely had chance to see the four cores move (but they did).

There is a lz4 -Xhc high compression option that can be used during compression. Slower to compress, but no impact upon decompression speeds apparently. For compress once, decompress many its appropriate to use that high compression choice IMO. Its not like xz high compression however and makes only a marginal improvement upon size reduction. LZ4 is primarily for fast decompression speeds at the expense of less tight compression.

I for one am a LZ4 convert Smile Downloading your lz4 supporting kernel as I write this. Thanks.

....

EDIT

Attached is my mksquashfs-lz4 and unsquashfs-lz4 from Tahr 6.0.5 also with 4.3.3 kernel and they seem to be binary compatible with jessie. I've included the lib for lz4, may be missing the libs for others (lzo etc.) ??? (not sure if it will pick up the libs already in jessie for those ok).

fake .gz suffix on filename

Your kernel is working great for me under Jessie with same 'changes' and sfs's (i.e. as-is, with new kernel dropped in). Failed for me under Wheezy. Booted part of the way but then complained about something like Union and sbin init i.e. I guess incompatible for Wheezy.

I've been using kernel 4.3.3 for a while now with Tahr with no problems that I've found. I believe that's a stable version anyway so a reasonable choice.
lz4.sfs.gz
Description 
gz

 Download 
Filename  lz4.sfs.gz 
Filesize  176 KB 
Downloaded  248 Time(s) 

_________________
( ͡° ͜ʖ ͡°) :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 
rufwoof


Joined: 24 Feb 2014
Posts: 3717

PostPosted: Sat 23 Jan 2016, 19:36    Post subject:  

For completeness - attached is a lz4 compression program (fake .gz suffix)

I've converted all my jessie squashfs's to lz4 now - with -Xhc switch i.e.
mksquashfs DIR some.squashfs -comp lz4 -Xhc

01-filesystem is 253MB
03-LibreOffice is 256MB
04-skype is 41MB
09-change is 79MB
43-kernel... is 54MB

I'm also running with initrd non compressed rather than xz compressed. Not sure but think some of the stuff in busybox/elsewhere inside initrd is compressed already and leaving initrd uncompressed also helps speed things up given that its relatively small (relative to modern day HDD sizes) the speed improvement of having initrd non compressed is beneficial IMO. Don't forget to edit menu.lst (bootloader) to point to initrd without a .xz suffix.

If you decide to lz4 compress initrd with lz4 I believe you have to use legacy mode lz4 compression due to some weird history. See this thread http://murga-linux.com/puppy/viewtopic.php?p=880025#880025

Seems to all be working well - Thanks Fred.
lz4.gz
Description  fake .gz suffix
gz

 Download 
Filename  lz4.gz 
Filesize  130.33 KB 
Downloaded  244 Time(s) 

_________________
( ͡° ͜ʖ ͡°) :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 
rufwoof


Joined: 24 Feb 2014
Posts: 3717

PostPosted: Sat 23 Jan 2016, 23:33    Post subject:  

rufwoof wrote:
fredx181 wrote:
rufwoof wrote:
Does standard DD-Jessie (32bit pae openbox) normally have the network icon blink/change as data flows (or not) when hard wired (ethernet)?

No, it doesn't for me, the little wire at the bottom of the icon shows if there's connection (lightens up) or not.

With the latest fix the icon becomes green if there's connection, but doesn't change when there's data flow.

In DD Wheezy all works fine. I created a squashfs of netmon-wce contents and Activated that and it continued to work ok in Wheezy. So looks like its something in Jessie that's not anything to do with netmon-wce.

If I restart X then the network tray icon changes to all glowing, I think because it locks the icon to when DD is retrieving its external IP address at the time.

Found a neat alternative. Synaptic, search for wicd and mark that for installation, and it will automatically detect that frisbee needs to be removed (and opts to install some python and other dependencies). Apply and after that finishes navigate to /root/.config/openbox and edit autostart.sh ... comment out or remove the frisbee & line and the wait and sleep lines after that and add/replace that with wicd-client &

Save and restart X

My autostart.sh now looks like
Code:
#!/bin/sh
xfdesktop &
xfce4-panel &
sleep 2
xfce4-clipman &
sleep 2
#frisbee-tray &
#wait $!
#sleep 1
wicd-client &
if [ -f /mnt/live/tmp/modules ]; then
conky -c ~/.conkyrc-port &
else
conky -c ~/.conkyrc-live &
fi
wait $!
volumeicon

wicd Wiki https://wiki.archlinux.org/index.php/Wicd

If you don't want/like the dialog each time you boot/restart X then add a --tray (dash dash tray) suffix to the wicd-client command i.e. wicd-client --tray &
wcid-client.jpg
 Description   
 Filesize   40 KB
 Viewed   1048 Time(s)

wcid-client.jpg


_________________
( ͡° ͜ʖ ͡°) :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 
fredx181


Joined: 11 Dec 2013
Posts: 4257
Location: holland

PostPosted: Sun 24 Jan 2016, 06:34    Post subject:  

Hi rufwoof,

Quote:
I for one am a LZ4 convert Smile


Really? Wink

Indeed my 4.3 kernel doesn't work on Wheezy.
Here's a setup that does work on Wheezy with the 4.1 liquorix kernel, aufs and lz4 are supported/included:
https://googledrive.com/host/0ByBgCDlZZ8K5NlYzQmM2cTh1Uk0/kernel-4.1-liquorix+squashfs-tools.tar.gz

Edit: Forgot to include the liquorix linux-headers .deb in the archive, here's link (from Mepis):
http://main.mepis-deb.org/mepiscr/testrepo/pool/test/l/linux-liquorix/linux-headers-4.1-7.dmz.1-liquorix-686-pae_4.1-11mcr120+1_i386.deb

Fred
Back to top
View user's profile Send private message 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Sun 24 Jan 2016, 13:00    Post subject: Re: Master PDF Editor  

rufwoof wrote:
I really like this little program - master pdf editor https://drive.google.com/file/d/0B4MbXu8cvE_WMUlrZ0NDNkFXMDA/view?usp=sharing. That's a Debian Wheezy squashfs that I created to run under DD. Contains the qt libs to run etc.

I'm a bit lost however. In that squashfs I've created a /root with some configuration options in .config sub-directory, however when I 'activate' that squashfs from a 'live' session it doesn't seem to 'copy' those /root files in when activated.

Loading the module should add /root/.config/Trolltech.conf and /root/Code Industry/Master PDF Editor.conf
It does for me on DD-JWM and from testing in the past I'm sure it works well in OpenBox (Wheezy and Jessie). The only difference in OpenBox is it has also safe mode right click option "loadmodule -ano" in /root/.config/Thunar/uca.xml while Jwm version has only "loadmodule -a" in /opt/bin/sfs-activate script. Both should work adding the /root/.config files from your module.
Try with fresh DD-OpenBox (without extra modules in "live") loading from terminal:
Code:
root@debian:~# loadmodule -a /live/image/master-pdf-editor-3.5.10.squashfs
squashfs
mount: warning: /mnt/live/memory/images/master-pdf-editor-3.5.10.squashfs seems to be mounted read-only.
SUCCESS: Module 'master-pdf-editor-3.5.10.squashfs' activated
ACTION: updating mimeinfo cache

Code:
root@debian:~# ls -l /root/.config/Trolltech.conf
-rw-r--r-- 1 root root 4385 Jan  4 00:47 /root/.config/Trolltech.conf
root@debian:~# ls -l "/root/Code Industry/Master PDF Editor.conf"
-rw-r--r-- 1 root root 2087 Jan 23 22:08 /root/Code Industry/Master PDF Editor.conf

Unfortunately masterpdfeditor doesn't start for me. It needs sse2 CPU flag.

Toni
Back to top
View user's profile Send private message MSN Messenger 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Sun 24 Jan 2016, 13:44    Post subject:  

Hi Fred.

Can you share any testing results for both lz4 kernel modules?
Like for example the result from:
Code:
apt-get install virtualbox-dkms

The Jessie module has strange redeb behaviour after booting kernel 4.3 which could explain the huge deb packages size for linux-image and linux-headers. I can't install linux-headers in DD-Jessie btw.
The liquorix headers for DD-Wheezy install works but I still can't compile module with virtualbox-dkms even after installing also the linux-image deb.
Code:
...invoke-rc.d: initscript virtualbox, action "restart" failed.
Setting up cpp (4:4.7.2-1) ...
Setting up gcc (4:4.7.2-1) ...
Setting up make (3.81-8.2) ...
Setting up dkms (2.2.0.3-1.2) ...
Setting up virtualbox-dkms (4.1.42-dfsg-1+deb7u1) ...
Loading new virtualbox-4.1.42 DKMS files...
First Installation: checking all kernels...
It is likely that 4.1-7.dmz.1-liquorix-686-pae belongs to a chroot's host
Building initial module for 4.1-7.dmz.1-liquorix-686-pae
Error! Bad return status for module build on kernel: 4.1-7.dmz.1-liquorix-686-pae (i686)
Consult /var/lib/dkms/virtualbox/4.1.42/build/make.log for more information.
dpkg: error processing virtualbox-dkms (--configure):
 subprocess installed post-installation script returned error exit status 10
Errors were encountered while processing:
 virtualbox-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian:~#

The content of make.log:
Code:
DKMS make.log for virtualbox-4.1.42 for kernel 4.1-7.dmz.1-liquorix-686-pae (i686)
Sun Jan 24 13:15:11 EET 2016
make: Entering directory `/usr/src/linux-headers-4.1-7.dmz.1-liquorix-686-pae'
  LD      /var/lib/dkms/virtualbox/4.1.42/build/built-in.o
  LD      /var/lib/dkms/virtualbox/4.1.42/build/vboxdrv/built-in.o
  CC [M]  /var/lib/dkms/virtualbox/4.1.42/build/vboxdrv/linux/SUPDrv-linux.o
/var/lib/dkms/virtualbox/4.1.42/build/vboxdrv/linux/SUPDrv-linux.c:88:3: error: #error "CONFIG_X86_SMAP is only supported by 4.3 and higher. Please upgrade VirtualBox."
make[2]: *** [/var/lib/dkms/virtualbox/4.1.42/build/vboxdrv/linux/SUPDrv-linux.o] Error 1
make[1]: *** [/var/lib/dkms/virtualbox/4.1.42/build/vboxdrv] Error 2
make: *** [_module_/var/lib/dkms/virtualbox/4.1.42/build] Error 2
make: Leaving directory `/usr/src/linux-headers-4.1-7.dmz.1-liquorix-686-pae'

Another problem with liquorix is installing hal, halevt, sleepd, r8168-dkms or synce-hal for example will auto-remove the kernel leaving the system unbootable.

I like liquorix kernel a lot and as I wrote few posts back I will try to make module with lz4 boot support. But I will post something only if I can keep 100% working official Wheezy and Jessie repository. Breaking the package manager is not acceptable for me.
Just for information the latest linux-image-4.4-0.dmz.2-liquorix-686-pae_4.4-2_i386 boots with lz4 compression in DD-Squeeze, Wheeze and Jessie (with live-boot-2, live-boot-3 and porteus-boot) and after small mods the headers work well in Jessie compiling virtualbox modules with gcc-4.9 but I'm not sure the result is safe for Jessie yet.

Edit: In case you are interested here is part of mine liquorix kernel testing repo compatibility procedure (after success with virtualbox-dkms):
Code:
root@debian:~# apt-get install acpi-call-dkms
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  acpi-call-dkms
0 upgraded, 1 newly installed, 0 to remove and 70 not upgraded.
Need to get 12.9 kB of archives.
After this operation, 73.7 kB of additional disk space will be used.
Get:1 http://ftp.de.debian.org/debian/ jessie/main acpi-call-dkms all 1.1.0-2 [12.9 kB]
Fetched 12.9 kB in 0s (56.3 kB/s)   
Selecting previously unselected package acpi-call-dkms.
(Reading database ... 57088 files and directories currently installed.)
Preparing to unpack .../acpi-call-dkms_1.1.0-2_all.deb ...
Unpacking acpi-call-dkms (1.1.0-2) ...
Setting up acpi-call-dkms (1.1.0-2) ...
Loading new acpi-call-1.1.0 DKMS files...
First Installation: checking all kernels...
Building only for 4.4-0.dmz.2-liquorix-686-pae
Building initial module for 4.4-0.dmz.2-liquorix-686-pae
Done.

acpi_call:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.4-0.dmz.2-liquorix-686-pae/extra/

depmod..............

DKMS: install completed.

Code:
root@debian:~# apt-get install virtualbox-guest-dkms
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  virtualbox-guest-utils
Recommended packages:
  virtualbox-guest-x11
The following NEW packages will be installed:
  virtualbox-guest-dkms virtualbox-guest-utils
0 upgraded, 2 newly installed, 0 to remove and 70 not upgraded.
Need to get 893 kB of archives.
After this operation, 5610 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.de.debian.org/debian/ jessie/contrib virtualbox-guest-utils i386 4.3.32-dfsg-1+deb8u2 [395 kB]
Get:2 http://ftp.de.debian.org/debian/ jessie/contrib virtualbox-guest-dkms all 4.3.32-dfsg-1+deb8u2 [498 kB]
Fetched 893 kB in 0s (918 kB/s)           
Selecting previously unselected package virtualbox-guest-utils.
(Reading database ... 57106 files and directories currently installed.)
Preparing to unpack .../virtualbox-guest-utils_4.3.32-dfsg-1+deb8u2_i386.deb ...
Unpacking virtualbox-guest-utils (4.3.32-dfsg-1+deb8u2) ...
Selecting previously unselected package virtualbox-guest-dkms.
Preparing to unpack .../virtualbox-guest-dkms_4.3.32-dfsg-1+deb8u2_all.deb ...
Unpacking virtualbox-guest-dkms (4.3.32-dfsg-1+deb8u2) ...
Processing triggers for systemd (215-17+deb8u1) ...
Setting up virtualbox-guest-utils (4.3.32-dfsg-1+deb8u2) ...
Setting up virtualbox-guest-dkms (4.3.32-dfsg-1+deb8u2) ...
Loading new virtualbox-guest-4.3.32 DKMS files...
First Installation: checking all kernels...
Building only for 4.4-0.dmz.2-liquorix-686-pae
Building initial module for 4.4-0.dmz.2-liquorix-686-pae
Done.

vboxguest:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.4-0.dmz.2-liquorix-686-pae/updates/

vboxsf.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.4-0.dmz.2-liquorix-686-pae/updates/

vboxvideo.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.4-0.dmz.2-liquorix-686-pae/updates/

depmod.............

DKMS: install completed.
Processing triggers for systemd (215-17+deb8u1) ...

Code:
root@debian:~# cd /tmp
root@debian:/tmp# wget http://ftp.us.debian.org/debian/pool/non-free/r/r8168/r8168-dkms_8.041.00-1_all.deb
--2016-01-24 21:09:05--  http://ftp.us.debian.org/debian/pool/non-free/r/r8168/r8168-dkms_8.041.00-1_all.deb
Resolving ftp.us.debian.org (ftp.us.debian.org)... 128.30.2.26, 128.61.240.89, 64.50.233.100, ...
Connecting to ftp.us.debian.org (ftp.us.debian.org)|128.30.2.26|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 85584 (84K) [application/x-debian-package]
Saving to: 'r8168-dkms_8.041.00-1_all.deb.1'

r8168-dkms_8.041.00 100%[=====================>]  83.58K   290KB/s   in 0.3s   

2016-01-24 21:09:05 (290 KB/s) - 'r8168-dkms_8.041.00-1_all.deb.1' saved [85584/85584]

Code:
root@debian:~# dpkg -i /tmp/r8168-dkms_8.041.00-1_all.deb
Selecting previously unselected package r8168-dkms.
(Reading database ... 57359 files and directories currently installed.)
Preparing to unpack .../r8168-dkms_8.041.00-1_all.deb ...
Unpacking r8168-dkms (8.041.00-1) ...
Setting up r8168-dkms (8.041.00-1) ...
Loading new r8168-8.041.00 DKMS files...
First Installation: checking all kernels...
Building only for 4.4-0.dmz.2-liquorix-686-pae
Building initial module for 4.4-0.dmz.2-liquorix-686-pae
Done.

r8168:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.4-0.dmz.2-liquorix-686-pae/updates/dkms/

depmod............

Backing up initrd.img-4.4-0.dmz.2-liquorix-686-pae to /boot/initrd.img-4.4-0.dmz.2-liquorix-686-pae.old-dkms
Making new initrd.img-4.4-0.dmz.2-liquorix-686-pae
(If next boot fails, revert to initrd.img-4.4-0.dmz.2-liquorix-686-pae.old-dkms image)
update-initramfs....

DKMS: install completed.
Processing triggers for initramfs-tools (0.120) ...
update-initramfs: Generating /boot/initrd.img-4.4-0.dmz.2-liquorix-686-pae
W: Possible missing firmware /lib/firmware/e100/d102e_ucode.bin for module e100
W: Possible missing firmware /lib/firmware/e100/d101s_ucode.bin for module e100
W: Possible missing firmware /lib/firmware/e100/d101m_ucode.bin for module e100
cryptsetup: WARNING: failed to detect canonical device of aufs
cryptsetup: WARNING: could not determine root device from /etc/fstab
Warning: /sbin/fsck.aufs doesn't exist, can't install to initramfs, ignoring.
live-boot: core filesystems devices utils udev wget blockdev ftpfs.


Toni
Back to top
View user's profile Send private message MSN Messenger 
rufwoof


Joined: 24 Feb 2014
Posts: 3717

PostPosted: Sun 24 Jan 2016, 16:34    Post subject:  

Hi Toni

I just installed the Infinality Fonts - and Synaptic no longer works (Jessie using k4.3.3). Not a issue for me - just highlighting a observation.

_________________
( ͡° ͜ʖ ͡°) :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 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Sun 24 Jan 2016, 17:22    Post subject:  

Hi rufwoof.

It takes no time to break DebianDog (and Debian) using unofficial kernel and unofficial packages. This is the reason I'm against posting untested modules and packages.

Infinality story for DebianDog-Wheezy started a long time ago here if you are interested:
http://murga-linux.com/puppy/viewtopic.php?p=830049&sid=58ff4b05d83be32c0acf22253b00b28e#830049

Now we have safe to install and working packages for DD-Wheezy:
http://murga-linux.com/puppy/viewtopic.php?p=832727&sid=ba7ead398e1ca2eaa7bf44a9b24d60f8#832727

Keisha's work on DD-Jessie packages started somewhere here:
http://murga-linux.com/puppy/viewtopic.php?p=833637&sid=2b790a8d6221a16e3de61d1b1112f185#833637
http://murga-linux.com/puppy/viewtopic.php?p=839575&sid=2b790a8d6221a16e3de61d1b1112f185#839575

We never made safe to install DD-Jessie infinality packages. Maybe some day Keisha will decide to continue working on this but till then I'm afraid there is no safe to install infinality package for Jessie.

Toni
Back to top
View user's profile Send private message MSN Messenger 
rufwoof


Joined: 24 Feb 2014
Posts: 3717

PostPosted: Sun 24 Jan 2016, 19:03    Post subject:  

Hi Toni.

So what is an appropriate way to run? I guess for Debian to be stable everything installed (removed) should be via Synaptic/apt-get, but does that extend to Firefox? i.e. should I stay with the (old) version that comes with jessie, or is it ok to use the firefox update to update to the latest version? Or is there some method to update firefox via Synaptic?

What about other code changes, for instance creating the likes of ~/.retrovol and /etc/alsa-base.conf ...etc files to assign a particular sound card. Or should that be managed some other way.

I sort of get it (I think). Debian do all the hard work of making sure things run smoothly (stable) but that means having to keep the packages and packages database all working 100%.

I've still not figured out how to to about installing system updates/security patches either!

Thanks.

_________________
( ͡° ͜ʖ ͡°) :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 
fredx181


Joined: 11 Dec 2013
Posts: 4257
Location: holland

PostPosted: Sun 24 Jan 2016, 19:25    Post subject:  

Hi Toni, rufwoof,

I keep it short because it's late here.
Re-uploaded kernel-4.3.3-lz4+aufs+squashfs-tools.tar.gz. all files replaced that are kernel/boot related.
As I was focused to much on lz4 support I made mistake, so compiled again, should be fine now. The .deb files have normal sizes now.
For me linux-headers installs now, virtualbox-dkms also.
Edited one of my previous posts (Edit2)
https://googledrive.com/host/0ByBgCDlZZ8K5NlYzQmM2cTh1Uk0/kernel-4.3.3-lz4+aufs+squashfs-tools.tar.gz
Toni, I'll look at your liquorix fix tomorrow.

Fred
Back to top
View user's profile Send private message 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Mon 25 Jan 2016, 03:50    Post subject:  

Hi Fred.

I can't do any testing till the end of the week and I like to continue working on linux-image-4.4-0.dmz.2-liquorix-686-pae_4.4-2_i386.deb which works very well on my old machine.
fredx181 wrote:
Toni, I'll look at your liquorix fix tomorrow.

I moved the non-free firmware in separate optional to install firmware-liquorix package. It can be easy replaced with:
Code:
apt-get install firmware-linux-nonfree firmware-bnx2 firmware-linux-free firmware-qlogic

I also removed the conflicting packages from linux-image and linux-headers and I changed gcc-5 to gcc-4.9 in .kernelvariables inside the headers package. Compiling works well in Jessie this way with Jessie gcc official version.
I have the packages uploaded in jessie repo extra section if you like to see the changes. Look for liquorix in the package name. I will not upload initrd files till I can test them well.

BTW squashfs-tools from Sid is dist-upgradable in DD-Jessie now. I keep version 4.2 from Jessie to prevent problems if some packages depend on the Jessie version. Probably I will change it to version 4.3 later when I'm sure it doesn't conflict with some Jessie package.

Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Mon 25 Jan 2016, 04:32    Post subject:  

rufwoof wrote:
Hi Toni.

So what is an appropriate way to run? I guess for Debian to be stable everything installed (removed) should be via Synaptic/apt-get, but does that extend to Firefox? i.e. should I stay with the (old) version that comes with jessie, or is it ok to use the firefox update to update to the latest version? Or is there some method to update firefox via Synaptic?

Debian has its own firefox based browser called iceweasel. If you prefer firefox I think it keeps all libs and binary files in its own subfolder outside system path and this should be safe enough. Probably you can upgrade firefox from its own check for updates button. I know Fred made sure the included firefox in openbox version is safe to use and upgrade.

Quote:
What about other code changes, for instance creating the likes of ~/.retrovol and /etc/alsa-base.conf ...etc files to assign a particular sound card. Or should that be managed some other way.

This is the way to do it. In worst case you will end up with broken sound and you will have to reverse the changes. But it is good to search for information how to do it in Debian. I'm sure there will be Debian examples.

Quote:
I sort of get it (I think). Debian do all the hard work of making sure things run smoothly (stable) but that means having to keep the packages and packages database all working 100%.

It is really hard work to make sure a package is safe and suitable for the system and it will not break something. We still have some examples for this in the special dd-repository like gnome-mplayer-1.0.7 (fix 1 here):
https://github.com/DebianDog/Jessie/blob/master/Bugs-and-Fixes.md
Any package from any debian based distro could break something on your system. This includes different Debian versions like installing Jessie packages on Wheezy or Sid packages on Jessie.

Quote:
I've still not figured out how to to about installing system updates/security patches either!

This one is easy. To get all upgrades (security, fixes and improvements from official Debian and special dd-repository) just type in terminal:
Code:
apt-get upgrade

This will install all upgradable packages which do not have new dependencies (some do have extra dependencies added). You will see a list of the packages for upgrade and you can confirm or cancel the upgrade.
Then remove the deb files from /var/cache/apt/archives to safe space (you don't need them after installing the packages):
Code:
apt-get clean

To upgrade the packages which have new dependencies compared to the installed older version type:
Code:
apt-get dist-upgrade

Checkout the new installed packages and the caculated disk space for them before confirming. Some could have huge dependencies you don't like to install. Canceling will keep the old package version working as before.
In Jessie for example now this will dist-upgrade squashfs-tools with lz4 support version.

To upgrade only some packages type the package name:
Code:
apt-get install squashfs-tools

This will install new version of one package (if there is available newer version).

Synaptic also has option to select packages for upgrade but it is not as good as apt-get solving problems with dpkg. Sometimes you can get 'can't fix broken package" message in Synaptic after installing/uninstalling packages which is very easy to fix with:
Code:
dpkg --configure -a
apt-get -f install
apt-get autoremove


Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
rufwoof


Joined: 24 Feb 2014
Posts: 3717

PostPosted: Mon 25 Jan 2016, 09:23    Post subject:  

saintless wrote:
Debian has its own firefox based browser called iceweasel.

I did read somewhere about how Debian had a fall-out with Mozilla resulting in more or less identical code/program (Firefox) being rebadged (Iceweasel).
Quote:
Any package from any debian based distro could break something on your system. This includes different Debian versions like installing Jessie packages on Wheezy or Sid packages on Jessie.

Understandable given the structure. From a clean version fo Jessie I tried installing Libre and Openshot (with its associated Blender, Inkscape ...etc) using Synaptic. The Libre menu text and icons were small and a test Openshot render resulted in a hang. So whilst easily available from the repository not always the best choices.

Perhaps then a core system that's aligned/updated as/when required and then add other programs externally. Running portable versions of Libre, Gimp and Firefox from that core DD-J worked well and being portable they don't affect the core system other than some config data being written under /root (or /root/.config). That way Synaptic/apt can be used to keep the core kernel/desktop maintained/updated without the added complexities/risk of other programs having conflicting/damaging libs.

If Openshot/Blender/Python/Inkscape - as all required to fully utilise Openshot video editing are all contained within a single SFS along with their required libs, then there's a good chance that those programs will run OK and can be loaded/unloaded as required. Loading of the sfs (as one example) might however conflict with other programs whilst loaded (perhaps for instance a different lib being 'over-written' by the sfs load of Openshot). But that might only be a issue if it were required to run both at the same time, otherwise sfs load Openshot, use, sfs unload and use the other (otherwise conflicting) program.

When I mentioned earlier that I was using a osmo (diary) sfs you highlighted that osmo could be installed from Synaptic, which I later did. I have my diary outside of the core system on HDD however so that's equally accessible from other pup's. A risk with using the synaptic version is that the version is different and a change to that later/different version could mean a change in how the diary is actually stored - which might corrupt or change it in a manner that other pup's could no longer access the diary. Having a common osmo sfs that all pup's use elminates that risk.

A relatively light DD core system, maintained using the methods you detailed (thanks), with everything else being loadable/unloadable modules (portable app/rox apps/SFS's) seems to me to be a reasonable choice. You get a stable core desktop, that's relatively easily maintained/updated, and have a bunch of programs (openshot, osmo, firefox ...etc) that can all be loaded/unloaded on top of that as/when required. When performing a 'system' update, just make sure all programs (sfs's/portable apps) are unloaded at the time such that the update is only applied to the core DD system (kernel and desktop type bits).

EDIT : Portable Libre 4.3.0.4 : https://drive.google.com/file/d/0B4MbXu8cvE_WRDhzTFFtUU56LUk/view?usp=sharing

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

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh

Last edited by rufwoof on Mon 25 Jan 2016, 10:23; edited 1 time in total
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 28 of 68 [1013 Posts]   Goto page: Previous 1, 2, 3, ..., 26, 27, 28, 29, 30, ..., 66, 67, 68 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.1215s ][ Queries: 13 (0.0325s) ][ GZIP on ]