(old)Puppy Linux Discussion Forum

Yes that's a fair view, Toni, and it is sufficient to update apps via debs as and when required; if apps are actively being developed they tend to need that regular upgrade mechanism via package management anyway.

As for interest in DebianDog, it would be nice to know how many people are actually using it or have even tried it. Considering its flexibility, it would make sense that many would be drawn to it, but users tend to stick with what they are used to or trust. I expect many more users have at least tried DebianDog than have posted to the DebianDog threads (though who knows?) - pity they don't say though, since feedback definitely encourages developments (which is always a lot of work, so difficult to maintain enthusiasm for such work when everything is already working so nicely anyway... I remember stopping work on Precord for a couple of years, because there was so little feedback - unknown to me it had stopped working because of ffmpeg changes, yet no-one said anything and it was in Puppy by default! I fixed it one day after I noticed...:-) Personally, I doubt I'd be doing any development work these past several months if it hadn't been for the fact that I took a shine to the concepts and work you started with Debian Light Squeeze followed by DebianDog - so that had a knock on effect in that it encouraged me to upgrade, a little, some of my earlier apps (such as Precord, and pAVrecord, and produce the backends for xhippo etc, with a view to perhaps doing more with these later).

William

Hi Toni and everyone,

The word "icanhazip" in DD GUI ... it's tacky, it makes DD look cheap ... as if Debian has lowered its standards. Why not have the Debian networkmanager as default and frisbee as a downloadable deb?

I'm not sure which ipinfo is in my current DD - self-edited, or the one from Richard. As shown in the pic below, it looks differently.

Hi, Anikin.

DebianDog was born from the idea to look closer as possible like Puppy and keeping Debian functionality untouched. Frisbee is Puppy application, very good one and it is the best one in my opinion regarding size and functions. I see it as improvement compared to Debian alternative network managers.
If it looks cheap to you because of external IP name option (disabled by default) it is enough just to remove it and use Network manager or WICD, but the size of both is much bigger.

Toni

Toni,

My original question was about Richard's version of ipinfo, that doesn't display the word "icanhazip" in the network GUI - which *is* *cheap* and tasteless by any standards (and was always hidden in Puppy, btw). Just a concerned user, thinkin' aloud, not an attempt to criticize your work.

anikin wrote:My original question was about Richard's version of ipinfo...

Because in next page post he decided to use this ipinfo version for next DebianDog packages and seems this ipinfo version includes some fixes missing in the previous one:

rerwin wrote:

About ipinfo:
I did extract one version from the latest slacko with the new comment

Code: Select all

#131126 zigbert: gui (gtkdialog) improvements.

I really like this version better. Looks better and has added a checkbox for optional
use of icanhazip. Only thing I wanted to change was not to use icanhazip by default
(line 17 and 18 in the new version)

from

Code: Select all

[ -f $HOME/.ipinfo ] && . $HOME/.ipinfo || CB0=true

to

Code: Select all

[ -f $HOME/.ipinfo ] && . $HOME/.ipinfo || CB0=false

I think I will use yours as a new basis for the DD version, to get zigbert's fix, but with the icanhazip stuff removed, as was requested.

Toni

Hi anikin, Toni,

anikin wrote:My original question was about Richard's version of ipinfo, that doesn't display the word "icanhazip" in the network GUI - which *is* *cheap* and tasteless by any standards (and was always hidden in Puppy, btw). Just a concerned user, thinkin' aloud, not an attempt to criticize your work.

Please let me understand what's so cheap about "icanhazip", I don't know nothing about it.
Or is it just about displaying IP adress option itself?

Edit: I should have searched first before asking, reading here:
http://www.murga-linux.com/puppy/viewto ... 8&start=15
Made me a little wiser, but don't have a strong opinion about it yet.

Anyway here's the exact same ipinfo I modified without icanhazip option and still with the same improvements.
Attached ipinfo.tar.gz.

Toni, I'll need another day also to upload new iso.

Fred

Saintless and others,

Well, I use it, but to be honest I use Windows XP as my main system because of my non-linux TV card and Beyond TV.

I think you'll get some more people using it once you announce that it is out of beta. A lot of people don't want to mess with beta releases. At least that seemed to be what happens with the main Puppy releases.

I understand that you built this for yourself. But I think that it is just too good to not try to "market" it outside the Puppy Community, at least a little.

Dan

anikin wrote:The word "icanhazip" in DD GUI ... it's tacky, it makes DD look cheap.

I think it looks fine. There has been a lot of discussion about the benefits (or downside) of connecting to an external site in order to find out the external IP that Puppy is using - and the fact that this function is able to be enabled/disabled whichever the user wants seems like a good thing to me.

dancytron wrote: A lot of people don't want to mess with beta releases

I think dancytron is right - as long as people know that beta testing is finished more people will be prepared to try it. (I know that attitude doesn't help testing/development much but many people are not confident trialling a system that still has bugs - they want to wait till the experts feel happy with the overall performance)

@dancytron

What is the chipset in your tv card?

Not sure anymore what chipset it is.

It is a avertv hybrid volar max.

Per this page, not supported. http://www.linuxtv.org/wiki/index.php/AVerMedia

It was years and years ago, but I spent some time trying to get it to work in Puppy and Ubuntu and couldn't.

I am happy with it and how it works in Windows XP.

I am using Debian Dog on my old Pentium III military/police surplus laptop (Itronix ix-250) too. For it, it will probably be the main OS from now on.

fredx181 wrote:
Toni, I'll need another day also to upload new iso.

Fred

Hi Fred and Toni,

I suspect this is too late for inclusion in your isos but I worked on the mods I needed to shinobar's ffconvert 1.4.2 to produce compatible deb package for DebianDog as quickly as I could and here it is anyway. Tested it quickly and seems to be fine as per previous 1.4.1 version. As per previous version deb I created, this also includes the needed probedisk and probepart programs by BarryK (with all references to /root changed to ${HOME} for multi-user DebianDog system).

Cheers, William

Toni and Fred,

Though too late for any changes probably, I know, The following list is just to help you check you have installed all the latest versions of stuff I worked on that you wanted. I thought I'd just list a quick summary of all the changes I have for new iso compared to old iso. May be some other stuff I wrote in this thread, but this is all I remember! :


ffconvert 1.4.2 deb download (previous post in this thread): http://www.murga-linux.com/puppy/viewto ... 524#790524

DoMyFile 0.9.8. deb download: http://www.murga-linux.com/puppy/viewtopic.php?t=94909

Precord 9.0.1 deb download: http://www.murga-linux.com/puppy/viewtopic.php?t=49907

As far as I recall, the previous iso already had the latest pAVrecord version 9.0.0. Otherwise, you can get the deb here:
http://www.murga-linux.com/puppy/viewtopic.php?t=81332

xrecord latest: http://www.murga-linux.com/puppy/viewto ... 915#789915

Cheers, William

EDIT: Note - I am also finishing off a small upgrade to DoMyCommand, mainly so that it also contains the hijack facility of pAVrecord and DoMyFile. I'll be uploading deb for that with a couple of hours probably. No big deal if you also don't have time now to include the changes to that though.

Will be uploading latest DoMyCommand deb here shortly.

Here is the latest DoMyCommand (version 0.9.8) deb package for DebianDog:

http://www.murga-linux.com/puppy/viewto ... 220#781220

Note that only the main script /usr/bin/domycommand has actually changed in this one.

William

I will try to include the latest changes, William.

Toni

dancytron wrote:Not sure anymore what chipset it is.

V4L (video 4 linux) has undergone lots of development and firmware and driver support built into newer kernels is much improved.

you can find the chipset by typing lspci or lsusb in a terminal.

Hi Toni, All,

Uploaded new openbox_xfce iso:
DebianDog-Porteus-openbox_xfce.iso
https://drive.google.com/file/d/0ByBgCD ... sp=sharing
New updated locale files module "00-locale-files-openbox_xfce.squashfs" :
https://drive.google.com/file/d/0ByBgCD ... sp=sharing

Toni, rename it as you think it's best.
I agree with William that "final" sounds to much "final" As there will be never anything after it.
Maybe "stable" is a better definition.
Also I think the "Porteus" can be removed from the name, it's misleading, why not just DebianDog, in the documentation anyone can read it has porteus-boot option along with the other boot options.

Besides the changes from "changes and fixes" post changed also:
- xfdesktop4 4.11 package downgraded to more stable version 4.10.
- Added Snapshot-make (for live-boot v2 only)
- Automatic symlinks /live/cow and /live/image created when booting with porteus boot method.
- Added latest changes from William for DoMyFile, DoMyCommand, ffconvert, precord and xrecord.

New screenshot below attached.

Fred

Hi, Fred.

All uploaded and first post updated. If we do not find problems in the next few days I really do not see reason to rebuild new iso for wheezy versions anymore.

Toni

Hi Fred and Toni,

Been a lot of changes so inevitably there are some problems. I've just had time for a quick test and found the following bugs:

1. In debiandog_jwm, when you click /mnt/home in filemanager, it no longer takes you to the /dev/mounted_partition it would in Puppy and used to in DebianDog_jwm. That works fine in openbox version though.

2. In openbox version, mplayer alone isn't playing simple mp3 files on my system, but gnome-mplayer is. mplayer worked fine with same mp3 files in jwm version.

3. I've made a mistake in Precord, at line 456 I have: when it should be lame not lame1

I had put the 1 at the end of lame during testing in order to check that mplayer would be used if lame not present, but I forgot to take the 1 out after...

To be honest, I was rushing too much at the end because the isos were in process of being released, so my other releases all need a bit of testing before I could confidently say they were 'stable'. Also, I think you have made a number of major system changes under the hood, so I'd say some further testing of these new isos is really necessary before you can say stable too...

I'll fix Precord and upload new deb later tonight (NZ time) but I won't be changing version number. That's the only fault I've found it in so far though.

Note that I wouldn't have spotted my Precord error had it not been for the mplayer issue in openbox version. In jwm version, Precord seemed to be working fine for Playback mp3, but that's cos it was using mplayer to playback (when it should have been using lame piped to aplay...).

Personally, I could do with a few more days to check the system more generally, before assigning stable to it, and my own programs in it also since they are newly released versions and could do with longer testing.

Cheers, William

Hi, William.

mcewanw wrote:1. In debiandog_jwm, when you click /mnt/home in filemanager, it no longer takes you to the /dev/mounted_partition it would in Puppy and used to in DebianDog_jwm.

In portesus-boot only you have /mnt/home. /live/image is symlink to /mnt/home which is symlink to the boot partition where /live folder is located. Check out your boot code again or some left save fle or save folder. It works the same way as in OpenBox version. No bug here.

3. I've made a mistake in Precord, at line 456 I have:

Code: Select all

if [ $(command -v lame1 2>/dev/null) ];then

when it should be lame not lame1

This is not enough reason for me for new iso. Debian package will fix this.

Personally, I could do with a few more days to check the system more generally, before assigning stable to it, and my own programs in it also since they are newly released versions and could do with longer testing.

I'm testing the system more than few days. Stable is the right word for me unless some critical bug is found. I will check mp3 problem for OpenBox version to confirm if it is the same for me.

Toni