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 Tue 21 Nov 2017, 00:49
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Xenialpup64 CE 7.0.8.6
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 29 of 32 [470 Posts]   Goto page: Previous 1, 2, 3, ..., 27, 28, 29, 30, 31, 32 Next
Author Message
belham2

Joined: 15 Aug 2016
Posts: 1303

PostPosted: Mon 30 Oct 2017, 14:34    Post subject:  

mavrothal wrote:
666philb wrote:
i'll be updating the 32bit xenialpup this coming week and if nothing major is discovered it'll be a 32&64bit 7.0.9 release.


As far as I know there is no "puppy 7" ever released.
Puppy 7.0.9 or any other point release as "official" after puppy 6.3 would be confusing and may go unnoticed.

You might want to discuss it with Mick and probably PB regarding release schedule and versioning.



Boy, I really don't understand this comment and/or reply.

So Micko releases Slacko 6.9.9.9, and officially calls it 'Slacko 700' in the thread title, then has left it like that for several months now. Phil had his "Xenialpups" marked as "7.0.8.#" for the same amount of time, returns & releases "7.0.8.6" which was much arppeciated. Then phil makes a comment that soon he should be able to go to 7.0.9, and Marvothal writes the above comment?


Can I ask why 7.0.9 is such a problem? Is it the fact it is only 3 numbers in length? Because we all are pretty used to seeing the "7" in front of everything when it comes to releases from both Micko and Phil. And the reference to Peebee? What is that?? His releases are like 17.##.## on the zesty/artful side, and same goes for the LxPupSc side.

Again, it begs the question, why did Phil's comment about going to a "7.0.9" elicit such a response? By reasoning and rationale alone in that comment to Phil, then no one (especially Micko) should ever have written a "7", let alone a "700" (like beside Slacko), correct?
Back to top
View user's profile Send private message 
Moat


Joined: 16 Jul 2013
Posts: 766
Location: Mid-mitten, USA

PostPosted: Mon 30 Oct 2017, 14:49    Post subject:  

Yeah, I didn't quite get that one either.

7.1.0 FTW! Smile

Or maybe 8.0.0... Shocked

Bob
Back to top
View user's profile Send private message 
perdido


Joined: 09 Dec 2013
Posts: 691
Location: Altair IV , Just north of Eeyore Junction.

PostPosted: Mon 30 Oct 2017, 15:24    Post subject:  

belham2 wrote:
mavrothal wrote:
666philb wrote:
i'll be updating the 32bit xenialpup this coming week and if nothing major is discovered it'll be a 32&64bit 7.0.9 release.


As far as I know there is no "puppy 7" ever released.
Puppy 7.0.9 or any other point release as "official" after puppy 6.3 would be confusing and may go unnoticed.

You might want to discuss it with Mick and probably PB regarding release schedule and versioning.



Boy, I really don't understand this comment and/or reply.

So Micko releases Slacko 6.9.9.9, and officially calls it 'Slacko 700' in the thread title, then has left it like that for several months now. Phil had his "Xenialpups" marked as "7.0.8.#" for the same amount of time, returns & releases "7.0.8.6" which was much arppeciated. Then phil makes a comment that soon he should be able to go to 7.0.9, and Marvothal writes the above comment?


Can I ask why 7.0.9 is such a problem? Is it the fact it is only 3 numbers in length? Because we all are pretty used to seeing the "7" in front of everything when it comes to releases from both Micko and Phil. And the reference to Peebee? What is that?? His releases are like 17.##.## on the zesty/artful side, and same goes for the LxPupSc side.

Again, it begs the question, why did Phil's comment about going to a "7.0.9" elicit such a response? By reasoning and rationale alone in that comment to Phil, then no one (especially Micko) should ever have written a "7", let alone a "700" (like beside Slacko), correct?




All of the 7.x versions so far are in beta.
No official 7.x versions yet.

I believe the reference about 7.0.9 is solely a problem with semantics.

.

.
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 9517
Location: Charleston S.C. USA

PostPosted: Mon 30 Oct 2017, 19:08    Post subject:  

666philb wrote:
bigpup wrote:
Xenialpup64 7.0.8.6
Frugal
Save folder.

I can live with this and have been for some time.
Just wonder why it is required in Xenialpup.

Video card Nvidia GeForce GTX 970.

Initial first boot, have to use nouveau.modeset=0 to get to visible desktop.


hi bigpup,

i've no idea why this is required with xenialpup64. do you need to use the same option with xenialpup32 bit as well? if so can you try the 32bit xenialpup with artfuls kernel. just copy the vmlinux & zdrv.sfs over renaming the zdrv.sfs

Yes. Xenialpup 32bit also requires the nouveau.modeset=0.

I tried the Artfulpup kernel 4.9.56-lxpup-32-pae in Xenialpup 32bit V7.0.8.1

It now boots a fresh initial boot, with no added boot options required.
The kernel change fixed it.

_________________
I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1175
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Tue 31 Oct 2017, 06:16    Post subject: wifi failed to connect using b43 module on laptop HP2530p  

Hi 666philb, Smile
Got a try this new 7.0.8.6 version on laptop HP2530p - thanks for it !
Here cannot connect to wifi network (was already the case with earlier 64bits versions).
Other recent Puppies (TahPup, Zesty, Artful, whatever 32 or 64 bits) connect to wifi network OOTB.
I even tried to compile the wl kernel module for the previous xenialpup64-7.0.8.5 version without getting wifi !
Here are some reports from Frisbee network tool to help for an eventual fix.

last edited: added dmesg output on ArtFulPup 32bits for a working WiFi

Quote:
dmesg output about b43:
...
gpiochip_find_base: found new base at 496
gpio gpiochip0: (ssb_chipco_gpio): added GPIO chardev (254:0)
gpiochip_setup_dev: registered GPIOs 496 to 511 on device: gpiochip0 (ssb_chipco_gpio)
ssb: Sonics Silicon Backplane found on PCI device 0000:02:00.0
b43-phy0: Broadcom 4312 WLAN found (core revision 15)
b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1
b43-phy0: Found Radio: Manuf 0x17F, ID 0x2062, Revision 2, Version 0
Broadcom 43xx driver loaded [ Features: PNLS ]
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
e1000e: eth0 NIC Link is Down
ip_tables: (C) 2000-2006 Netfilter Core Team
EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
DMAR: DRHD: handling fault status reg 2
DMAR: [DMA Read] Request device [02:00.0] fault addr fffe9000 [fault reason 06] PTE Read access is not set
b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
b43-phy0 ERROR: This device does not support DMA on your system. It will now be switched to PIO.
b43-phy0: Controller RESET (DMA error) ...
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
b43-phy0: Controller restarted
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0 warning: Forced PIO by use_pio module parameter. This should not be needed and will result in lower performance.


Thanks for any advice!
Charlie

Quote:
dmesg output for workig WiFi on ArtFulPup on the VERY SAME PC
...
ssb: Sonics Silicon Backplane found on PCI device 0000:02:00.0
Console: switching to colour frame buffer device 160x50
i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
b43-phy0: Broadcom 4312 WLAN found (core revision 15)
b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1
b43-phy0: Found Radio: Manuf 0x17F, ID 0x2062, Revision 2, Version 0
Broadcom 43xx driver loaded [ Features: PNLS ]
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
udevd[8046]: Process '/sbin/crda' failed with exit code 254.
udevd[8162]: Process '/sbin/crda' failed with exit code 254.
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
udevd[8407]: Process '/sbin/crda' failed with exit code 254.
udevd[8673]: Process '/sbin/crda' failed with exit code 254.
wlan0: authenticate with 20:0c:c8:16:e0:7c
wlan0: send auth to 20:0c:c8:16:e0:7c (try 1/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 2/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 3/3)
wlan0: authenticated
wlan0: associate with 20:0c:c8:16:e0:7c (try 1/3)
wlan0: RX AssocResp from 20:0c:c8:16:e0:7c (capab=0x1411 status=0 aid=1)
wlan0: associated
udevd[8718]: Process '/sbin/crda' failed with exit code 254.
udevd[9384]: Process '/sbin/crda' failed with exit code 254.
wlan0: deauthenticated from 20:0c:c8:16:e0:7c (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
udevd[9388]: Process '/sbin/crda' failed with exit code 254.
wlan0: authenticate with 20:0c:c8:16:e0:7c
wlan0: send auth to 20:0c:c8:16:e0:7c (try 1/3)
wlan0: authenticated
wlan0: associate with 20:0c:c8:16:e0:7c (try 1/3)
wlan0: RX AssocResp from 20:0c:c8:16:e0:7c (capab=0x1411 status=0 aid=1)
wlan0: associated
udevd[9396]: Process '/sbin/crda' failed with exit code 254.
udevd[9451]: Process '/sbin/crda' failed with exit code 254.
udevd[9502]: Process '/sbin/crda' failed with exit code 254.
wlan0: deauthenticating from 20:0c:c8:16:e0:7c by local choice (Reason: 3=DEAUTH_LEAVING)
udevd[9523]: Process '/sbin/crda' failed with exit code 254.
udevd[9544]: Process '/sbin/crda' failed with exit code 254.
e1000e: enp0s25 NIC Link is Down
b43-phy0: Radio hardware status changed to DISABLED
b43-phy0: Radio hardware status changed to ENABLED
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
wlan0: authenticate with 20:0c:c8:16:e0:7c
wlan0: send auth to 20:0c:c8:16:e0:7c (try 1/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 2/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 3/3)
wlan0: authentication with 20:0c:c8:16:e0:7c timed out
wlan0: authenticate with 20:0c:c8:16:e0:7c
wlan0: send auth to 20:0c:c8:16:e0:7c (try 1/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 2/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 3/3)
wlan0: authentication with 20:0c:c8:16:e0:7c timed out
wlan0: authenticate with 20:0c:c8:16:e0:7c
wlan0: send auth to 20:0c:c8:16:e0:7c (try 1/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 2/3)
wlan0: send auth to 20:0c:c8:16:e0:7c (try 3/3)
wlan0: authenticated
b43 ssb0:0 wlan0: disabling HT/VHT due to WEP/TKIP use
wlan0: associate with 20:0c:c8:16:e0:7c (try 1/3)
wlan0: RX AssocResp from 20:0c:c8:16:e0:7c (capab=0x1411 status=0 aid=1)
wlan0: associated

Netw_set_failed.png
 Description   
 Filesize   135.23 KB
 Viewed   384 Time(s)

Netw_set_failed.png

pdiag-20171031.tar.gz
Description 
gz

 Download 
Filename  pdiag-20171031.tar.gz 
Filesize  182.85 KB 
Downloaded  8 Time(s) 
Netw_set_wpa-status.png
 Description   
 Filesize   130.18 KB
 Viewed   385 Time(s)

Netw_set_wpa-status.png

Net_set_wpa_Supp_Log.png
 Description   
 Filesize   137.7 KB
 Viewed   387 Time(s)

Net_set_wpa_Supp_Log.png

Back to top
View user's profile Send private message 
666philb


Joined: 07 Feb 2010
Posts: 3121
Location: wales

PostPosted: Tue 31 Oct 2017, 07:17    Post subject:  

bigpup wrote:

Yes. Xenialpup 32bit also requires the nouveau.modeset=0.

I tried the Artfulpup kernel 4.9.56-lxpup-32-pae in Xenialpup 32bit V7.0.8.1

It now boots a fresh initial boot, with no added boot options required.
The kernel change fixed it.


hi bigpup,
could you try a live boot xenialpup with artfulpups fdrv.sfs.
just rename it to fdrv_xenialpup64_7.0.8.6.sfs and stick it in your xenialpup folder

_________________
Tahrpup, built with trusty tahr packages http://murga-linux.com/puppy/viewtopic.php?t=96178
Quickpet_Precise, install popular apps quickly http://www.murga-linux.com/puppy/viewtopic.php?t=83642
Back to top
View user's profile Send private message 
666philb


Joined: 07 Feb 2010
Posts: 3121
Location: wales

PostPosted: Tue 31 Oct 2017, 07:29    Post subject: Re: wifi failed to connect using b43 module on laptop HP2530p  

charlie6 wrote:
Hi 666philb, Smile
Got a try this new 7.0.8.6 version on laptop HP2530p - thanks for it !
Here cannot connect to wifi network (was already the case with earlier 64bits versions).
Other recent Puppies (TahPup, Zesty, Artful, whatever 32 or 64 bits) connect to wifi network OOTB.
I even tried to compile the wl kernel module for the previous xenialpup64-7.0.8.5 version without getting wifi !


hi charlie6,

can you try the suggestion pointed to in this link https://bbs.archlinux.org/viewtopic.php?id=230381

_________________
Tahrpup, built with trusty tahr packages http://murga-linux.com/puppy/viewtopic.php?t=96178
Quickpet_Precise, install popular apps quickly http://www.murga-linux.com/puppy/viewtopic.php?t=83642
Back to top
View user's profile Send private message 
charlie6


Joined: 30 Jun 2008
Posts: 1175
Location: Saint-Gérard / Walloon part of Belgium

PostPosted: Tue 31 Oct 2017, 08:26    Post subject:  [SOLVED] wifi failed to connect using b43 module on HP2530p  

[quote="666philb"]
charlie6 wrote:
Hi 666philb, Smile
Got a try this new 7.0.8.6 version on laptop HP2530p - thanks for it !
Here cannot connect to wifi network (was already the case with earlier 64bits versions
...
hi charlie6,
can you try the suggestion pointed to in this link https://bbs.archlinux.org/viewtopic.php?id=230381


Hi 666philb Very Happy !
tons of thanks for you quick reply ! Razz
it works now !
Have added «intel_iommu=off» to the GRUBs kernel parameters as suggested in the above link; aftrwds reboot (frugal install) and it connects to WiFi straight on after inserting WPA code!

Here is my grub code:
Code:
title Puppy Linux XENIALPUP64_7.0.8.6 frugal in sda4 dir xen64
  root (hd0,3)
  kernel /xen64/vmlinuz psubdir=xen64 pmedia=atahd pfix=fsck intel_iommu=off
  initrd /xen64/initrd.gz


as reported in the above links by forum moderator V1del:
Quote:
About linux-4.13.3-1-x86_64 kernel: One new option enabled in the 4.13 kernel by default is iommu, have you tried the mentioned kernel parameter to turn that off again?


Best regards
Charlie

last edited:
For Xenialpup64-7.0.8.5-uefi: /lib/firmware/b43 is missing:
It also fixes the same issue on Xenialpup64-7.0.8.5-uefi provided the /lib/firmware/b43 has previuosly been installed, and the PC rebooted: firmware copied from Xenialpup64-7.0.8.6

HTH, Charlie

Last edited by charlie6 on Mon 13 Nov 2017, 04:14; edited 1 time in total
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 9517
Location: Charleston S.C. USA

PostPosted: Tue 31 Oct 2017, 09:58    Post subject:  

666philb wrote:
bigpup wrote:

Yes. Xenialpup 32bit also requires the nouveau.modeset=0.

I tried the Artfulpup kernel 4.9.56-lxpup-32-pae in Xenialpup 32bit V7.0.8.1

It now boots a fresh initial boot, with no added boot options required.
The kernel change fixed it.


hi bigpup,
could you try a live boot xenialpup with artfulpups fdrv.sfs.
just rename it to fdrv_xenialpup64_7.0.8.6.sfs and stick it in your xenialpup folder

Artfulpup is 32bit.
Is it's fdrv going to work in a 64bit Xenialpup?

_________________
I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
Back to top
View user's profile Send private message 
666philb


Joined: 07 Feb 2010
Posts: 3121
Location: wales

PostPosted: Tue 31 Oct 2017, 10:28    Post subject:  

bigpup wrote:
666philb wrote:
bigpup wrote:

Yes. Xenialpup 32bit also requires the nouveau.modeset=0.

I tried the Artfulpup kernel 4.9.56-lxpup-32-pae in Xenialpup 32bit V7.0.8.1

It now boots a fresh initial boot, with no added boot options required.
The kernel change fixed it.


hi bigpup,
could you try a live boot xenialpup with artfulpups fdrv.sfs.
just rename it to fdrv_xenialpup64_7.0.8.6.sfs and stick it in your xenialpup folder

Artfulpup is 32bit.
Is it's fdrv going to work in a 64bit Xenialpup?

i believe so, as i don't think the firmware is dependent on the operating systems architecture. (could be wrong though Smile )

_________________
Tahrpup, built with trusty tahr packages http://murga-linux.com/puppy/viewtopic.php?t=96178
Quickpet_Precise, install popular apps quickly http://www.murga-linux.com/puppy/viewtopic.php?t=83642
Back to top
View user's profile Send private message 
666philb


Joined: 07 Feb 2010
Posts: 3121
Location: wales

PostPosted: Tue 31 Oct 2017, 15:44    Post subject:  

mavrothal wrote:
666philb wrote:
i'll be updating the 32bit xenialpup this coming week and if nothing major is discovered it'll be a 32&64bit 7.0.9 release.


As far as I know there is no "puppy 7" ever released.
Puppy 7.0.9 or any other point release as "official" after puppy 6.3 would be confusing and may go unnoticed.

You might want to discuss it with Mick and probably PB regarding release schedule and versioning.


ok.... i'll ask and see what they reckon . i actually don't mind what it is.

_________________
Tahrpup, built with trusty tahr packages http://murga-linux.com/puppy/viewtopic.php?t=96178
Quickpet_Precise, install popular apps quickly http://www.murga-linux.com/puppy/viewtopic.php?t=83642
Back to top
View user's profile Send private message 
666philb


Joined: 07 Feb 2010
Posts: 3121
Location: wales

PostPosted: Tue 31 Oct 2017, 15:50    Post subject: Re: Xenial Pup 64
Subject description: XenialPup64 and web browsers
 

Duprate wrote:


BUG:
For the proper functioning of the audio in Firefox, it is necessary that the libs in usr/lib/apulse/, are located in usr/lib/ e I solved the problem by copying and pasting it in the right place.


hi Duprate,

the problem with this solution is with apps that check to see if there is a working pulse audio, and then not finding it use the alsa interace instead. those apps will then always use the pulseaudio interface provided by apulse.
and whilst they work there's less control over them in puppys native mixer.

so i reckon i'll be sticking with the apulse libs in /usr/lib/apulse and using 'apulse firefox' to run firefox

_________________
Tahrpup, built with trusty tahr packages http://murga-linux.com/puppy/viewtopic.php?t=96178
Quickpet_Precise, install popular apps quickly http://www.murga-linux.com/puppy/viewtopic.php?t=83642
Back to top
View user's profile Send private message 
mavrothal


Joined: 24 Aug 2009
Posts: 2908

PostPosted: Tue 31 Oct 2017, 16:13    Post subject:  

666philb wrote:
i actually don't mind what it is.

Can't find the post now that BK archived his blogs, but the story goes that Distowatch does not want to go back and forth with numbers, (you should not have puppy-xenial7.1 and then puppy-slacko 7.0) and not like to "announce" point releases.
(They do announce development/beta releases with any version, and maybe puppy builders should take advantage of it).

_________________
== Here is how to solve your Linux problems fast ==
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 9517
Location: Charleston S.C. USA

PostPosted: Tue 31 Oct 2017, 18:44    Post subject:  

SOMEBODY JUST POST SOME NEW INFO ABOUT PUPPY ON DISTROWATCH. Exclamation Exclamation Exclamation Exclamation Exclamation Exclamation
WHATEVER IT IS Exclamation Exclamation Exclamation

The last Puppy version talked about is Slacko 6.3 and that was in 2015 Shocked Rolling Eyes Exclamation
Tahrpup is talking about Tahrpup 6.0. Nothing about Tahrpup 6.0.5 or 6.0.6 and any of the 64bit versions of Tahrpup.

Do not say why do you not do it?

Distrowatch would like the, developer of a Puppy version, to give the info to post.
I agree. The developer knows the Puppy version and what it is all about. Someone else, may think they know it, but there may be other features they know nothing about.

_________________
I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 9517
Location: Charleston S.C. USA

PostPosted: Tue 31 Oct 2017, 19:36    Post subject:  

Quote:
the story goes that Distowatch does not want to go back and forth with numbers, (you should not have puppy-xenial7.1 and then puppy-slacko 7.0) and not like to "announce" point releases.

Seems Ubuntu can do it Shocked

Quote:
2017-10-19: Distribution Release: Ubuntu 17.10
• 2017-09-29: Development Release: Ubuntu 17.10 Beta 2
• 2017-08-03: Distribution Release: Ubuntu 16.04.3
• 2017-04-13: Distribution Release: Ubuntu 17.04
• 2017-03-23: Development Release: Ubuntu 17.04 Beta 2
• 2017-02-17: Distribution Release: Ubuntu 16.04.2
• 2016-10-13: Distribution Release: Ubuntu 16.10
• 2016-09-28: Development Release: Ubuntu 16.10 Beta 2
• 2016-08-05: Distribution Release: Ubuntu 14.04.5
• 2016-07-21: Distribution Release: Ubuntu 16.04.1
• 2016-04-21: Distribution Release: Ubuntu 16.04
• 2016-03-25: Development Release: Ubuntu 16.04 Beta 2


Seems if you are talking about two or more completely different named Puppy versions. The version number should go along with the development of that specific Puppy.
They may all be considered version 7 in the Puppy series, which is now controlled by WOOF-CE.
But where in that named version of Puppy may be completely different from one named version to another.

DistroWatch needs to understand that there is more than one version of Puppy. Several different ones are developed at the same time based on different core programs, features, and files.

_________________
I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 29 of 32 [470 Posts]   Goto page: Previous 1, 2, 3, ..., 27, 28, 29, 30, 31, 32 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.1422s ][ Queries: 12 (0.0273s) ][ GZIP on ]