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 Fri 13 Dec 2019, 03:30
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
DebianDog64 - 64 bit DebianDog-Jessie
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 21 of 38 [560 Posts]   Goto page: Previous 1, 2, 3, ..., 19, 20, 21, 22, 23, ..., 36, 37, 38 Next
Author Message
rufwoof


Joined: 24 Feb 2014
Posts: 3675

PostPosted: Thu 18 Aug 2016, 15:20    Post subject:  

Shifting the Tint (bottom) panel over to the left screen edge revealed the KDE tray beneath that. Both seem fully operational/functional Smile

Bit like a underdog setup I guess. Make a KDE sfs to load on demand and perhaps set it to desktop 2 Smile

Dragging between rox filer, pcmanfm and dolphin file managers has all three correctly reflecting any changes Laughing
snapshot3.jpg
 Description   
 Filesize   41.96 KB
 Viewed   2450 Time(s)

snapshot3.jpg

Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 4209
Location: holland

PostPosted: Fri 19 Aug 2016, 06:36    Post subject:  

Hi rufwoof,

Quote:
With hindsight, using
Code:
mksquashfs squashfs-root 01-fs.sfs -comp xz -Xbcj x86 -Xdict-size 524288 -always-use-fragments -nopad -b 524288


The 01-filesystem.squashfs from the 20.03.2016 ISO is made with only -comp -b and -Xbcj options:
Code:
mksquashfs ..... ..... -comp xz -b 524288 -Xbcj x86


I found that using blocksize 1048576 makes it boot and run a little slower, so the gain having smaller file size is not worth it in my opinion.

Quote:
ISO filesize 152MB
01-filesystem.squashfs filesize 124MB

ISO here


Thanks, will try to test soon, but may take some time (having a little vacation, feeling very tired these days).

Fred

_________________
Dog Linux website
Tinylinux blog by wiak
Back to top
View user's profile Send private message 
dancytron

Joined: 18 Jul 2012
Posts: 1413

PostPosted: Sat 20 Aug 2016, 00:14    Post subject:  

Never mind, figured it out.

Dan
Back to top
View user's profile Send private message 
dancytron

Joined: 18 Jul 2012
Posts: 1413

PostPosted: Mon 22 Aug 2016, 00:59    Post subject:  

Hi everyone.

I just installed my remastered DD64 on to a usb stick as a test. I am seeing an issue that is somewhat similar to the issue I reported here and was fixed. http://www.murga-linux.com/puppy/viewtopic.php?t=93225&start=30 It may be something as simple as a menu.1st error, I am not sure.

Thanks,

Dan

*************************************

Install was done with installer inside DD64 on sda3 installing from a ISO file to sdc1 (a usb drive). Formatted to ext4 with gparted and used Grub4dos. I am using the Porteus boot (either of the first 2 entries).

Here is my menu.1st file generated by grub4dos.

Code:
# menu.lst produced by grub4dosconfig-v1.7
color white/blue black/cyan white/black cyan/black
timeout 10
default 0

title Debian-PorteusDog  -  changes=EXIT:/live/ (I added this one)
 uuid c82d532c-629d-4555-a784-f1b3e45fda4c
 kernel /live/vmlinuz1 from=/ noauto changes=EXIT:/live/
 initrd /live/initrd1.xz

title Debian-PorteusDog  -  changes to /live/ sysvinit
 uuid c82d532c-629d-4555-a784-f1b3e45fda4c
 kernel /live/vmlinuz1 from=/ noauto changes=/live/
 initrd /live/initrd1.xz

title Debian-PorteusDog  -  Always Fresh sysvinit
 uuid c82d532c-629d-4555-a784-f1b3e45fda4c
 kernel /live/vmlinuz1 from=/ nomagic base_only norootcopy
 initrd /live/initrd1.xz

title Debian-PorteusDog  -  Copy to RAM sysvinit
 uuid c82d532c-629d-4555-a784-f1b3e45fda4c
 kernel /live/vmlinuz1 noauto from=/ copy2ram
 initrd /live/initrd1.xz
 
title DebianDog  -  live-boot-3 Persistence Changes sysvinit
 uuid c82d532c-629d-4555-a784-f1b3e45fda4c
 kernel /live/vmlinuz1 boot=live persistence config quickreboot noeject autologin
 initrd /live/initrd.img

title DebianDog  -  live-boot-3 (no persistence) sysvinit
 uuid c82d532c-629d-4555-a784-f1b3e45fda4c
 kernel /live/vmlinuz1 boot=live config quickreboot noeject autologin
 initrd /live/initrd.img
 
title DebianDog  -  live-boot-3 Copy to RAM sysvinit
 uuid c82d532c-629d-4555-a784-f1b3e45fda4c
 kernel /live/vmlinuz1 boot=live toram=01-filesystem.squashfs
 initrd /live/initrd.img

title Reboot computer
  reboot





Two things happen. It has placed my changes in /live/sda3 (the only linux partition on my computer) instead of sdc1 (the usb stick it is installed on). Also, when I try to open sda3, it has the Debian Dog file system mounted, not the sda3 drive. See screenshot attached.

I managed to find the porteus-livedbg log file. It seems to document what is happening.
Code:
# Recognized devices:
/dev/sda1: LABEL="Old XP" UUID="368C66D28C668C65" TYPE="ntfs" PARTUUID="025f025e-01"
/dev/sda3: LABEL="Puppy 5.2" UUID="3a4a7fe5-6763-4af1-b972-42535e7d8590" TYPE="ext4" PARTUUID="025f025e-03"
/dev/sda4: LABEL="Puppy Swap" TYPE="swap" PARTUUID="025f025e-04"
/dev/sda5: LABEL="MediaData" UUID="6A1C5CFF1C5CC7A9" TYPE="ntfs" PARTUUID="025f025e-05"
/dev/sdb2: LABEL="Internal" UUID="A82454EB2454BDCE" TYPE="ntfs" PARTUUID="c50afefe-02"
/dev/sdb5: LABEL="New XP Pro" UUID="8848056A480557F8" TYPE="ntfs" PARTUUID="c50afefe-05"
/dev/sdc1: UUID="c82d532c-629d-4555-a784-f1b3e45fda4c" TYPE="ext4" PARTUUID="a3f29f5b-01"

# Booting device:
/mnt/sdc1

#  data found in:
/mnt/sdc1///live

# Changes are stored in:
/live/

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/sdc1///live/01-filesystem.squashfs
/mnt/sda3//live//changes
debdog-20160822000812.jpg
Description  This shows the test file saved in root that appears on sda3/live/changes/root instead of instead in sdc1/live/changes/root.
jpg

 Download 
Filename  debdog-20160822000812.jpg 
Filesize  108.94 KB 
Downloaded  252 Time(s) 
debdog-20160821235140.jpg
 Description   Shows what is under sda3 instead of what should be
 Filesize   22.6 KB
 Viewed   2276 Time(s)

debdog-20160821235140.jpg

Back to top
View user's profile Send private message 
mcewanw

Joined: 16 Aug 2007
Posts: 3200

PostPosted: Mon 22 Aug 2016, 17:55    Post subject:  

dancytron wrote:

title Debian-PorteusDog - changes=EXIT:/live/ (I added this one)
uuid c82d532c-629d-4555-a784-f1b3e45fda4c
kernel /live/vmlinuz1 from=/ noauto changes=EXIT:/live/
initrd /live/initrd1.xz


Hello Dan,

I think I've come across this issue before, but I'm not sure. I have a DD64 installation on usb but my partner has that at work today. However, I have a feeling you may need to add root=UUID=xxx to the kernel line (though only Fred might be able to explain why). So I suggest you try the following modification:
Code:

title Debian-PorteusDog  -  changes=EXIT:/live/ (I added this one)
 uuid c82d532c-629d-4555-a784-f1b3e45fda4c
 kernel /live/vmlinuz1 root=UUID=c82d532c-629d-4555-a784-f1b3e45fda4c from=/ noauto changes=EXIT:/live/
 initrd /live/initrd1.xz


Hope that does the job and someone will explain the purpose. I know next to nothing about grub4dos - I just use what I know. From looking at it, I imagine it sets root fs to the device with UUID supplied.

I think the installer program should be modified to make any such change (assuming that is what the 'fix' is).

William

_________________
github mcewanw
Back to top
View user's profile Send private message Visit poster's website 
dancytron

Joined: 18 Jul 2012
Posts: 1413

PostPosted: Tue 23 Aug 2016, 00:55    Post subject:  

mcewanw wrote:
dancytron wrote:

title Debian-PorteusDog - changes=EXIT:/live/ (I added this one)
uuid c82d532c-629d-4555-a784-f1b3e45fda4c
kernel /live/vmlinuz1 from=/ noauto changes=EXIT:/live/
initrd /live/initrd1.xz


Hello Dan,

I think I've come across this issue before, but I'm not sure. I have a DD64 installation on usb but my partner has that at work today. However, I have a feeling you may need to add root=UUID=xxx to the kernel line (though only Fred might be able to explain why). So I suggest you try the following modification:
Code:

title Debian-PorteusDog  -  changes=EXIT:/live/ (I added this one)
 uuid c82d532c-629d-4555-a784-f1b3e45fda4c
 kernel /live/vmlinuz1 root=UUID=c82d532c-629d-4555-a784-f1b3e45fda4c from=/ noauto changes=EXIT:/live/
 initrd /live/initrd1.xz


Hope that does the job and someone will explain the purpose. I know next to nothing about grub4dos - I just use what I know. From looking at it, I imagine it sets root fs to the device with UUID supplied.

I think the installer program should be modified to make any such change (assuming that is what the 'fix' is).

William


That didn't help. No change.

I'll work on it a little more in a couple of days. Not urgent from my point of view, just a bug that needs to be fixed eventually.

Maybe I'll try running grub4dos on a usb stick from Puppy and see what the menu.1st looks like for comparison.

edit: I tried installing using extlinux instead of grub4dos when it gave me a choice. It was much better, in the sense that it put the /changes directory on the USB stick instead of on my hard drive and the linux partition on my hard drive mounted correctly. However, it didn't mount my usb drive correctly. It mounted the changes directory as sdc1. However, if I browsed to /mnt/sdc1 that was correct.

As an aside, Universal USB Installer from windows works just fine, although only with fat32.

I'll look at this again if I get a chance, but like I said, it is testing for the sake of bug finding, not for my actual use at this point.
Back to top
View user's profile Send private message 
mcewanw

Joined: 16 Aug 2007
Posts: 3200

PostPosted: Tue 23 Aug 2016, 04:30    Post subject:  

Hello again Dan,

My partner is back home so I now have my DD64 installation on her usb available to me. It has been set up with grub4dos, grldr and menu.lst on the usb, but I've renamed the grldr files to disable that and have it booting from my harddisk grub4dos menu.lst instead. The configuration is different from yours: I have my live folder in a subdirectory of the second partition on the usb (which is sdb2 on my machine). The path is /DDjessie64usb/live and the menu.lst stanza I have on my harddisk menu.lst is as follows:
Code:

title Debian-PorteusDog64  -  changes to /live/ sysvinit
 uuid 6c05b5ca-00c3-4661-a097-c3346ae2ae15
 kernel /DDjessie64usb/live/vmlinuz1 root=UUID=6c05b5ca-00c3-4661-a097-c3346ae2ae15 from=/DDjessie64usb/ noauto changes=EXIT:/DDjessie64usb/live/
 initrd /DDjessie64usb/live/initrd1.xz


That booted up fine for me and I made a test blank file in /root which was there on reboot, so persistence seems to be working okay.

I'm wondering if you have any other /live directories somewhere on your system causing boot to get mixed up. I always use a unique subdir to avoid issues like that. However, I know the installer program just uses /live so you are quite correct that either way there seems to be a problem with the installer program, though I haven't myself looked into the menu.lst creation details.

William

_________________
github mcewanw
Back to top
View user's profile Send private message Visit poster's website 
fredx181


Joined: 11 Dec 2013
Posts: 4209
Location: holland

PostPosted: Tue 23 Aug 2016, 14:43    Post subject:  

Hi Dan, William

William wrote:
I'm wondering if you have any other /live directories somewhere on your system causing boot to get mixed up. I always use a unique subdir to avoid issues like that. However, I know the installer program just uses /live so you are quite correct that either way there seems to be a problem with the installer program, though I haven't myself looked into the menu.lst creation details.


Yes, I think also there's conflict because you have a 'live' directory on the root of hd partition, it will search for a 'live' folder anywhere, but hard-disk has priority over USB, so it will use sda3/live if it exists.
Not the fault of the installer, manually install by copying the files and folders and creating menu.lst with entry "/live/..." would produce the same, indeed, as William said, a unique subdir prevents these kind of problems.

Edit: A unique subdir for changes only should be OK in your case Dan, something like: changes=EXIT:/live/DD64-USB (requires to have created first "/live/DD64-USB" folder on sdb1).

But... as you mentioned Dan, as second issue, that pcmanfm opens sda3 partition as /mnt/live/memory/images/changes-exit , that is a bug in my opinion.
No clue yet how to fix that, it has to do with the fact that /dev/sda3 is mounted twice and pup-volume-monitor picks the first one Question
Real sda3 partition is at /mnt/sda3 from file-manager , BTW.


Fred

_________________
Dog Linux website
Tinylinux blog by wiak
Back to top
View user's profile Send private message 
dancytron

Joined: 18 Jul 2012
Posts: 1413

PostPosted: Tue 23 Aug 2016, 18:05    Post subject:  

fredx181 wrote:
Hi Dan, William

William wrote:
I'm wondering if you have any other /live directories somewhere on your system causing boot to get mixed up. I always use a unique subdir to avoid issues like that. However, I know the installer program just uses /live so you are quite correct that either way there seems to be a problem with the installer program, though I haven't myself looked into the menu.lst creation details.


Yes, I think also there's conflict because you have a 'live' directory on the root of hd partition, it will search for a 'live' folder anywhere, but hard-disk has priority over USB, so it will use sda3/live if it exists.
Not the fault of the installer, manually install by copying the files and folders and creating menu.lst with entry "/live/..." would produce the same, indeed, as William said, a unique subdir prevents these kind of problems.

Edit: A unique subdir for changes only should be OK in your case Dan, something like: changes=EXIT:/live/DD64-USB (requires to have created first "/live/DD64-USB" folder on sdb1).

But... as you mentioned Dan, as second issue, that pcmanfm opens sda3 partition as /mnt/live/memory/images/changes-exit , that is a bug in my opinion.
No clue yet how to fix that, it has to do with the fact that /dev/sda3 is mounted twice and pup-volume-monitor picks the first one Question
Real sda3 partition is at /mnt/sda3 from file-manager , BTW.


Fred


I think that something to make the subdirectory more unique ought to be added to the installer. It shouldn't be too hard to add "live-usb" instead of just "live" to the installer. As long as there aren't multiple usb drives with DD installed on it, that ought to get rid of any chance of problems.

The reason is that it is potentially pretty destructive. If you have a user that has a "live" directory on their hard drive who then creates a usb version and lets it save to the hard drive, then they've messed up their /hardrive/changes directory. No real harm, so no foul in my case, since I haven't really been using my DD 32 in the /sda3/live since DD 64 came out, but I could see it destroying someone's install in the right circumstance.

I'll test some more tonight or tomorrow.

Last edited by dancytron on Tue 23 Aug 2016, 18:43; edited 2 times in total
Back to top
View user's profile Send private message 
dancytron

Joined: 18 Jul 2012
Posts: 1413

PostPosted: Tue 23 Aug 2016, 18:26    Post subject: Debian Dog Chrome Remaster
Subject description: Google Chrome Version 52.0.2743.116 (64-bit)
 

edit 4-25-17 - Bug to fix from Fred:
Quote:
EDIT: dancytron, I noticed in your chrome-remaster that /etc/fstab is not empty.
It was mistake from the beginning from me, fstab should be empty otherwise there may be problems when someone makes a full install


edit: 3-24-17

I have gone ahead and updated my Debian Dog Chrome Remaster.

ISO file (239 Megabytes):
https://www.dropbox.com/s/hs9lljs0k64g7kj/DebianChromeDog64-Jessie-2017-3-23.iso?dl=0

Checksum file:
https://www.dropbox.com/s/9llt4h5ua3bxlhc/DebianChromeDog64-Jessie-2017-3-23.iso.md5?dl=0

From Readme file

Debian Dog 64 Chrome Remaster - Chrome Version 57.0.2987.110 (64-bit)
Linux jessie64 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux

Up to date through March 23, 2017

This is the update of my remaster of Debian Dog 64 with Chrome. Prior version info below.

Just a few new things. I've incorporated the kernel upgrade script and updated the kernel to the latest version.

I've also added a new user "cat" with the password of "cat." The only real difference from user puppy is that the user cat is not in the sudo group. This mainly a useful to allow other people to use your computer without the risk of them screwing up and trashing things.

For the highly security concious/paranoid, the cat id could also be used to run Chrome from the root or puppy user id. See http://distro.ibiblio.org/fatdog/web/faqs/login.html .

I've also added a script to "empty litterbox". This allows you to easily delete all cats Chrome user profile settings and cache files. I've put it on the root desktop for easy access.

For convenience, I've added a script to delete all Chrome user profile settings and cache files for all users. It is also on the root desktop for easy access.

Otherwise, more of the same except newer.

******************************
From 8-21-2016 version
******************************


I've decided to go ahead and publish my Debian Dog Chrome Remaster.

Total size is 225 megabytes.

The main user advantage being that it runs Netflix out of the box with no modification needed.

Unlike Puppy versions of Chrome, the Google Repositories are added and Chrome can be updated by "apt-get upgrade" like any other program in Debian.

I documented every step I took to create it in the Readme.txt file attached. I didn't really understand the menu system entirely, so there are some trial and error workarounds that probably aren't so great, but they seem to work and survive the upgrade process.

ISO file on dropbox.com 225 meg https://db.tt/UF3i8Vn6

MD5 file on dropbox -https://db.tt/UF3i8Vn6

I hope this will get a few more users for DD 64 enabling more feedback and bug finding/fixing.

Edit: 11-14-16

The only thing that has proven to not work is my fairly lame editing of the menu. When you upgrade Chrome, it will replace the .desktop file in /usr/shared/applications, which will make it reappear in the menu. However, it won't work because does not have the correct command line switches (it will work correctly if logged in as puppy).

Either ignore it or delete it every time you do an upgrade.
debdog-2017032317.jpg
 Description   new and improved obligatory screenshot
 Filesize   78.77 KB
 Viewed   1474 Time(s)

debdog-2017032317.jpg

ReadMe2017-3-23.txt.gz
Description  Remove ".gz" to use
gz

 Download 
Filename  ReadMe2017-3-23.txt.gz 
Filesize  9.22 KB 
Downloaded  181 Time(s) 

Last edited by dancytron on Tue 25 Apr 2017, 15:57; edited 11 times in total
Back to top
View user's profile Send private message 
mcewanw

Joined: 16 Aug 2007
Posts: 3200

PostPosted: Tue 23 Aug 2016, 21:15    Post subject: Re: Debian Dog Chrome Remaster
Subject description: Google Chrome Version 52.0.2743.116 (64-bit)
 

dancytron wrote:
I've decided to go ahead and publish my Debian Dog Chrome Remaster.

Total size is 225 megabytes.


Nice to have a Chrome version for some things. I'll download and try this one.

I've made it clear on here that I'm taking a long break, but I was thinking of long being pretty much permanent, but the more I have thought about it the more I feel I don't want Toni's departure to cause the breakup of DebianDog-related developments.

I hope also that rufwoof will also include his work under the DebianDog hood if some of the developments in there are closely related - that would help boost the DebianDog development team for when Fred becomes more active again. More can be done when a team expands and becomes stable - of course I would like to see Toni come back since his exactness for detail is much missed I feel.

Also, would be good to see these new contributions being documented on DebianDog webpages Fred has created and perhaps link into the main GitHub pages there. Having originally pushed for DebianDog to use GitHub I haven't myself used it since! but if I'm sticking around I'll sharpen up on that again.

It is summer coming here soon though, and I always pretty much vanish for months and most of this current winter I was mucking around developing weX for screencast, which, as the download and feedback statistics suggest (!), was probably a waste of time really (though I like my own work!;-) ).

I don't think Toni did the right thing, and I'd think better of him if he came back in acknowledgement of that, but I also think it is the wrong thing to allow negativeness to take over as a result of things going a bit awry.

William

_________________
github mcewanw
Back to top
View user's profile Send private message Visit poster's website 
dancytron

Joined: 18 Jul 2012
Posts: 1413

PostPosted: Tue 23 Aug 2016, 23:34    Post subject:  

Further testing on the installer for usb/grub4dos.

I created a new installation using ext4 on my usb stick.

I modified the menu.1st file as follows:

Code:
title Debian-PorteusDog  -  changes=EXIT:/live/usbchanges/ sysvinit (this entry added)
 uuid 64df9ede-52ec-4631-b562-4f8d56e55b67
 kernel /live/vmlinuz1 from=/ noauto changes=EXIT:/live/usbchanges/
 initrd /live/initrd1.xz

title Debian-PorteusDog  -  changes to /live/usbchanges/ sysvinit
 uuid 64df9ede-52ec-4631-b562-4f8d56e55b67
 kernel /live/vmlinuz1 from=/ noauto changes=/live/usbchanges/
 initrd /live/initrd1.xz


I then added a directory /live/usbchanges.

It now works correctly in all respects!!!

Changes are being recorded in sdc1/live/usbchanges and when I click on sdc1 in the file manager it is showing sdc1 correctly.
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3675

PostPosted: Wed 24 Aug 2016, 11:39    Post subject:  

Running several Debian versions and I have previously experienced weird behaviour likely due to picking up unintended versions. I now try to more clearly differentiate by using sub directories, my 32 bit DebianDog for instance has a menu.lst entry of
Code:
title 2 Debian Jessie 32 only saves if run save2flash
find --set-root /DEBJESSIE32/live/01-filesystemlz4.squashfs
kernel /DEBJESSIE32/live/vmlinuz1 from=/DEBJESSIE32 noauto changes=EXIT:/DEBJESSIE32/live
initrd /DEBJESSIE32/live/initrd1-lz4-addon

As has been previously mentioned the hunt sequence will search for and use the first version it finds and where the HDD tends to be searched first.

I love that 32 bit DebDog, it runs well and is stable, Toni (and Fred) did a outstanding job of it IMO, and one that I keep coming back around to rebooting again. My concern after Toni left the building was a feeling of being left somewhat high and dry, which prompted me to look at the alternatives. The more it and the 64 bit version retains usage/support the better IMO.
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 4209
Location: holland

PostPosted: Wed 24 Aug 2016, 18:19    Post subject:  

Hi William and everyone

Quote:
I hope also that rufwoof will also include his work under the DebianDog hood if some of the developments in there are closely related - that would help boost the DebianDog development team for when Fred becomes more active again. More can be done when a team expands and becomes stable - of course I would like to see Toni come back since his exactness for detail is much missed I feel.


Would be very nice if there's a developers team and great if you still like to cooperate in any way William !
If it can be done with pleasure (without any pressure felt) it's OK.
Just guessing, maybe that's where it went wrong for Toni, too much pressure from outside.
Maybe you've seen what he is up to for Jwm version at the moment here:
https://github.com/MintPup/DebianDog-Wheezy
Quote:
I will get back to the starting point first building base version with only live-boot-2 (without yad, without gtkdialog, without porteus-boot scripts, without /opt directory and sh restored to dash). From this point I will try to make command line scripts for frugal and full install, sfs-load, remaster and some more working with dash. The result from this base will tell how DebianDog-Jwm and MintPup development will continue here for me.

That looks to me that he likes to go back to the beginning of DebianDog without adding any programs borrowed from Puppy and without any of the programs that you (William), Terry or myself produced!.
Not very likely that he will "come back" IMO.

Although having a little break now, I do not plan to quit working on DebianDog development, I'm just contemplating about how.
For example: DebianDog-Jessie 32 bit needs to be upgraded, e.g. bug fixes, new additions, start a new thread? (for upgrade openbox_xfce version ISO (when ready), don't want to touch Jwm version because it's exclusively Toni's project).
Also, indeed, rufwoof's "Debian Live" discoveries might be nice to add to the "new" "fresh" Question DD project.
Any thoughts are welcome.

Fred

_________________
Dog Linux website
Tinylinux blog by wiak

Last edited by fredx181 on Thu 25 Aug 2016, 16:47; edited 1 time in total
Back to top
View user's profile Send private message 
backi

Joined: 27 Feb 2011
Posts: 1852
Location: GERMANY

PostPosted: Thu 25 Aug 2016, 05:36    Post subject:  

Hi fred !
Glad to hear ......sounds quite promising....o.k. relax ...have some fun .

Don`t hurry....just.....be... happy ! Smile

Blessings !
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 21 of 38 [560 Posts]   Goto page: Previous 1, 2, 3, ..., 19, 20, 21, 22, 23, ..., 36, 37, 38 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.1155s ][ Queries: 13 (0.0301s) ][ GZIP on ]