Dpup482-beta5 testing
- gposil
- Posts: 1300
- Joined: Mon 06 Apr 2009, 10:00
- Location: Stanthorpe (The Granite Belt), QLD, Australia
- Contact:
Just a quick word on libiconv discussion....
As of beta6, the point will be somewhat moot, as beta6 has GLIBC_2.10 and a the Debian Squeeze core which will also reflect in a new devx with the updated dev files for the changes....libiconv will disappear from the devx, as glibc now handles all charset support/conversion.
As of beta6, the point will be somewhat moot, as beta6 has GLIBC_2.10 and a the Debian Squeeze core which will also reflect in a new devx with the updated dev files for the changes....libiconv will disappear from the devx, as glibc now handles all charset support/conversion.
[img]http://gposil.netne.net/images/tlp80.gif[/img] [url=http://www.dpup.org][b]Dpup Home[/b][/url]
- gposil
- Posts: 1300
- Joined: Mon 06 Apr 2009, 10:00
- Location: Stanthorpe (The Granite Belt), QLD, Australia
- Contact:
Iguleder said:
You don't have to worry about Busybox, Dpup already has the latest stable version...but the others are well worth looking at, provided we use the Debian bases.gposil: should I compile BusyBox, module-init-utils, util-linux-ng, udev, all those? I think Puppy needs a complete overhaul of all basic utilties, they're totally outdated (things like DVB are supported by the newer udevs, for example). I also think it's possible to ditch dhcpcd in favor of udhcpc to save some space, I use it in my distro and it works just fine. /etc/resolv.conf has the same syntax.
[img]http://gposil.netne.net/images/tlp80.gif[/img] [url=http://www.dpup.org][b]Dpup Home[/b][/url]
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
I wouldn't discard libiconv just yet. Perhaps a year from now. Even though glibc 2.10.1 now has the code in it to handle all charset support/conversion, I have within the past two weeks compiled Xorg 7.5 per BLFS, and Gnome 2.28 using jhbuild, on my heavily modified upup-450 (which carries gcc 4.4.1 and /lib/libc.so.6 version 2.10.1). And have seen that many of these two large packages' components and dependencies, even the newest available versions from git and svn, fail to build without correctly addressing libiconv in their configure line. I presume this is because they have not yet been updated to call the internal iconv functions in the latest glibc.gposil wrote:...as glibc now handles all charset support/conversion.
- gposil
- Posts: 1300
- Joined: Mon 06 Apr 2009, 10:00
- Location: Stanthorpe (The Granite Belt), QLD, Australia
- Contact:
SHS makes a very good point, until application developers catch up with glibc development, we'll leave libiconv in the devx, but all new apps and upgrades should be taken from Debian branch(which doesn't use it).
Cheers
Guy
Cheers
Guy
[img]http://gposil.netne.net/images/tlp80.gif[/img] [url=http://www.dpup.org][b]Dpup Home[/b][/url]
big_bass has already ported the slitaz package manager. See the Slaxer_Pup thread.Iguleder wrote: Oh, last thing ... I'm quite enthusiastic about this one ... SliTaz and Tiny Core compatibility for Puppy, how does that sound? SliTaz's package manager is just bash scripts and one gtkdialog frontend, that can be easily ported. TC's extensions mechanism is even simpler, just SFSs with all files, plus a script (similar to pinstall.sh). The problem is FLWM/JWM menu incompatibility.
Puppy Linux Blog - contact me for access
Yeah I already mentioned that ayttm crashes msn and doesn't work with current yahoo. I'm not sure that there's another good im that's lightweight and supports all protocols, pidgin is the only good alternative but it's fat. Maybe ditch ayttm and put xchat in for irc, and for other im's put menu entry that opens meebo or some other web client like they did in 4.2. After connecting to irc guys from #puppylinux can instruct users to install pidgin or something else. We should definitely have pidgin 2.6.4 compiled at least in repo. I managed to compile it but without voice/video suport as it requires a lot of gstreamer libs.
puppy.b0x.me stuff mirrored [url=https://drive.google.com/open?id=0B_Mb589v0iCXNnhSZWRwd3R2UWs]HERE[/url] or [url=http://archive.org/details/Puppy_Linux_puppy.b0x.me_mirror]HERE[/url]
- gposil
- Posts: 1300
- Joined: Mon 06 Apr 2009, 10:00
- Location: Stanthorpe (The Granite Belt), QLD, Australia
- Contact:
Dpup482beta is no more....
After the huge backend updates i've just finished, the next Dpup will be 484beta1.
Polishing and bug fixing on 482 will continue, for addition to 484.
There is no timescale on this release yet....
Initial changes are listed below:
After the huge backend updates i've just finished, the next Dpup will be 484beta1.
Polishing and bug fixing on 482 will continue, for addition to 484.
There is no timescale on this release yet....
Initial changes are listed below:
- Attachments
-
- shot.png
- Changelog
- (27.58 KiB) Downloaded 1075 times
[img]http://gposil.netne.net/images/tlp80.gif[/img] [url=http://www.dpup.org][b]Dpup Home[/b][/url]
gposil
Can you ditch puptV in favour of my new app, pupRadio? (it includes pupTelly and is smaller.. more bang for byte
__________________________________________________________
Now, I managed to compile the latest tint2 but not without some extreme head banging! It is now only a 36k pet, and a special thanks to the guys at the google code tint2 site.
Musher0, you can start tint2 from your pekwm startup script.
Compiling tint2 was a nightmare. We certainly have a problem with our imlib2, it refused to compile against it, so I used patriot's version, sorry I don't have the link at hand.
The other problem is a Debian issue, but really a libtool problem. I finally got through ./configure with no errors only to have make flake on me . The first problem was "can't find /usr/X11R7/libXext.la". Oh dear, so I stole the one out of 431.. naughty yes.. then it was lixcbxlib.la... hmmm, funny, libxcb and libxcb-xlib are there... so on some googling i found some heated discussion about lib*.la files and Debian not supporting them and how it's really a libtool issue. FFS! I wanna compile an app, not rebuild the OS! Anyway, I found libxcb-xlib on ttuuxxx repo at puppylinux.ca (thanks ttuuxxx, Eric) but on installing that I got a meltdown of X. Oh dear yet again. Lucky I know that I can restore originals from pup_ro2.. did that got X back. I left the libxcb-xlib.la file there though (/usr/lib). Ok , Next was libxcb! Oh dear again? It was a bit like dependency chasing manually in Puppy, a real PITA! Ok, one more the actual libXext.so lib, found that in 431. Yay 'make' ran! Woohoo.
Updated pet is on Page 1 of this thread ( .txt file is at dpup.org in my repo.)
Cheers
Can you ditch puptV in favour of my new app, pupRadio? (it includes pupTelly and is smaller.. more bang for byte
__________________________________________________________
Now, I managed to compile the latest tint2 but not without some extreme head banging! It is now only a 36k pet, and a special thanks to the guys at the google code tint2 site.
Musher0, you can start tint2 from your pekwm startup script.
Compiling tint2 was a nightmare. We certainly have a problem with our imlib2, it refused to compile against it, so I used patriot's version, sorry I don't have the link at hand.
The other problem is a Debian issue, but really a libtool problem. I finally got through ./configure with no errors only to have make flake on me . The first problem was "can't find /usr/X11R7/libXext.la". Oh dear, so I stole the one out of 431.. naughty yes.. then it was lixcbxlib.la... hmmm, funny, libxcb and libxcb-xlib are there... so on some googling i found some heated discussion about lib*.la files and Debian not supporting them and how it's really a libtool issue. FFS! I wanna compile an app, not rebuild the OS! Anyway, I found libxcb-xlib on ttuuxxx repo at puppylinux.ca (thanks ttuuxxx, Eric) but on installing that I got a meltdown of X. Oh dear yet again. Lucky I know that I can restore originals from pup_ro2.. did that got X back. I left the libxcb-xlib.la file there though (/usr/lib). Ok , Next was libxcb! Oh dear again? It was a bit like dependency chasing manually in Puppy, a real PITA! Ok, one more the actual libXext.so lib, found that in 431. Yay 'make' ran! Woohoo.
Updated pet is on Page 1 of this thread ( .txt file is at dpup.org in my repo.)
Cheers
Puppy Linux Blog - contact me for access
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
The 483 is a secret or phantom release?gposil wrote:Dpup482beta is no more....
After the huge backend updates i've just finished, the next Dpup will be 484beta1.
Polishing and bug fixing on 482 will continue, for addition to 484.
There is no timescale on this release yet....
Initial changes are listed below:
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
Using a samba printer share
When trying to help a French fellow poster, I tried to do the setup myself and followed this procedure.
I didn't succeed in configuring correctly CUPS.
In the device selection I should have «Windows shared printer via sambe» or something the like.
Instead I got something like unknown device on....
I deleted the smbspool symlink as instructed in such a case and recreated it, but I still get the same weird device in the selection list.
I then did the same thing in puppy 4.3.1
No problem at all, I could print.
Did someone succeed in using a Windows shared printer un dpup?
What could be the cause of the failure?
I didn't succeed in configuring correctly CUPS.
In the device selection I should have «Windows shared printer via sambe» or something the like.
Instead I got something like unknown device on....
I deleted the smbspool symlink as instructed in such a case and recreated it, but I still get the same weird device in the selection list.
I then did the same thing in puppy 4.3.1
No problem at all, I could print.
Did someone succeed in using a Windows shared printer un dpup?
What could be the cause of the failure?
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
- gposil
- Posts: 1300
- Joined: Mon 06 Apr 2009, 10:00
- Location: Stanthorpe (The Granite Belt), QLD, Australia
- Contact:
Béèm
I use a Canon ip3000 shared by a Windows PC over network, setup was simple worked first time..
Menu-->Setup-->Cups Printer Wizard
Answer Yes to add new printer...Get Cups Welcome Screen
Select Add Printer Button
Name Printer....Press Continue
Choose Windows Printer via SAMBA from dropdown...Press Contine
Enter URI of printer etc etc
Works for me every time.
I use a Canon ip3000 shared by a Windows PC over network, setup was simple worked first time..
Menu-->Setup-->Cups Printer Wizard
Answer Yes to add new printer...Get Cups Welcome Screen
Select Add Printer Button
Name Printer....Press Continue
Choose Windows Printer via SAMBA from dropdown...Press Contine
Enter URI of printer etc etc
Works for me every time.
[img]http://gposil.netne.net/images/tlp80.gif[/img] [url=http://www.dpup.org][b]Dpup Home[/b][/url]
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
Windows shared printer in dpup482b5
Guy, (gposil)
To define the printer in CUPS, that's exactly the procedure I use.
But I have the unknown device (see picture)
When I select this, I can go on in the configuration which seems to be accepted, but when trying to print the test page, the job starts, but after a while I get an error in smb and the job is stopped.
Maybe I have a corruption in the samba client support for the printer or in the save file. Note that I can go to my HDD shares without a problem.
Some time ago I installed the samba server, but as it didn't work I uninstalled it. I hope some support isn't uninstalled as well.
In PPM, searching samba, I only see samba_3.2.5 server and common files.
Should I install the common files?
Bernard
To define the printer in CUPS, that's exactly the procedure I use.
But I have the unknown device (see picture)
When I select this, I can go on in the configuration which seems to be accepted, but when trying to print the test page, the job starts, but after a while I get an error in smb and the job is stopped.
Maybe I have a corruption in the samba client support for the printer or in the save file. Note that I can go to my HDD shares without a problem.
Some time ago I installed the samba server, but as it didn't work I uninstalled it. I hope some support isn't uninstalled as well.
In PPM, searching samba, I only see samba_3.2.5 server and common files.
Should I install the common files?
Bernard
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
- gposil
- Posts: 1300
- Joined: Mon 06 Apr 2009, 10:00
- Location: Stanthorpe (The Granite Belt), QLD, Australia
- Contact:
Bernard
I think that's exactly what has happened...You will have to re-install samba-3.0.26.pet and samba_client-3.0.26.pet from the Puppy-4 packages at ibiblioSome time ago I installed the samba server, but as it didn't work I uninstalled it. I hope some support isn't uninstalled as well.
[img]http://gposil.netne.net/images/tlp80.gif[/img] [url=http://www.dpup.org][b]Dpup Home[/b][/url]
Just this far from giving up...
Can't get the devx package to incorporate either through the boot manager or with the sfs-linker...
=-=-=
On another front, what is dpup doing to keep the capacity for localization without little or big headaches ? The preceding exchanges/posts about the libiconv library were a bit scary for a non-Anglophone...
Can't get the devx package to incorporate either through the boot manager or with the sfs-linker...
=-=-=
On another front, what is dpup doing to keep the capacity for localization without little or big headaches ? The preceding exchanges/posts about the libiconv library were a bit scary for a non-Anglophone...
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
You don't need the full samba server package to access a Windows shared printer. These two files should be sufficient:gposil wrote:BernardI think that's exactly what has happened...You will have to re-install samba-3.0.26.pet and samba_client-3.0.26.pet from the Puppy-4 packages at ibiblioSome time ago I installed the samba server, but as it didn't work I uninstalled it. I hope some support isn't uninstalled as well.
/opt/samba/bin/smbspool
/etc/opt/samba/smb.conf
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
Windows shared printer
@rcrsn51
I have those two files.
I followed the How to you wrote.
Installing the advised samba client didn't help
Installing the advises samba didn't help either.
I am afraid, that with all the testing I did, apt_synaptic installing apps, uninstalling, uninstalling apt_synaptic, that I got corruption in the save file.
It's probably better to start with a fresh save file.
@rcrsn51
I have those two files.
I followed the How to you wrote.
Installing the advised samba client didn't help
Installing the advises samba didn't help either.
I am afraid, that with all the testing I did, apt_synaptic installing apps, uninstalling, uninstalling apt_synaptic, that I got corruption in the save file.
It's probably better to start with a fresh save file.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Talking to myself (:-/), I'd answer that I've reassured musher0 about the localisation issue by copying all the *.mo files from Toutou 4.12 in the corresponding dpup directories. It seems to work so far for the programs I've used.musher0 wrote:Just this far from giving up...
{...}
=-=-=
On another front, what is dpup doing to keep the capacity for localization without little or big headaches ? The preceding exchanges/posts about the libiconv library were a bit scary for a non-Anglophone...
But I'm not talking to myself, I'm posting in a forum.
Tasgarth, tu as lu ça ? Bonne nouvelle, non ? (Tasgarth, have you read this? Good news, no?)
A+ / BFN
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
- Iguleder
- Posts: 2026
- Joined: Tue 11 Aug 2009, 09:36
- Location: Israel, somewhere in the beautiful desert
- Contact:
gposil: pidgin-light maybe?
Should I compile udev for dpup? Does dpup use udev at all? If that's the case, I'll compile udev-147 with custom rules (I'll remove stuff like tape devices, all pre-i686 era stuff), because if I remembe right, it was released with 2.6.31.x. And no, udev-149 doesn't compile on my Debian. If that goes right, I'll try to compile util-linux-ng and module-init-tools.
EDIT: yes, it does ... ancient udev-124.
BTW: dpup has BusyBox svn from the 1.15 era, not 1.15.2.
Should I compile udev for dpup? Does dpup use udev at all? If that's the case, I'll compile udev-147 with custom rules (I'll remove stuff like tape devices, all pre-i686 era stuff), because if I remembe right, it was released with 2.6.31.x. And no, udev-149 doesn't compile on my Debian. If that goes right, I'll try to compile util-linux-ng and module-init-tools.
EDIT: yes, it does ... ancient udev-124.
BTW: dpup has BusyBox svn from the 1.15 era, not 1.15.2.
Last edited by Iguleder on Wed 16 Dec 2009, 07:00, edited 1 time in total.