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 Mon 22 Sep 2014, 00:34
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Lucid Puppy 5.2.7 RC2
Moderators: Flash, JohnMurga
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 74 of 91 Posts_count   Goto page: Previous 1, 2, 3, ..., 72, 73, 74, 75, 76, ..., 89, 90, 91 Next
Author Message
backi

Joined: 27 Feb 2011
Posts: 433
Location: GERMANY

PostPosted: Mon 01 Aug 2011, 09:00    Post_subject:  

I´ m not quite shure where to post this information. So I do it here.

Today I have seen in DISTROWATCH some comments about economic crisis and if this maybe will give Linux in future some advantage over MS Windows.
Please read for your own.

There was a comment from a guy " Linux in Africa (by Atle on 2011-08-01 10:37:23 GMT from France)" which I like to cite here.

3 • Linux in Africa (by Atle on 2011-08-01 10:37:23 GMT from France)

"Dear readers. After spending more than 2 years in various African countries, I can for sure tell you why it does not succeed. Its as simple or stupid as this:

There is no money to collect. Nothing to be stolen. No government kickbacks, no 10% percent commission to the government people. So the public sector, as well as the private, will only deal with MS, that has off course specialized into offering the 10 or 20 percent commission on all sales. Microsoft main sales partner in Tanzania was awarded something like “Partner of the Year” by MS, in 2010.

The only ones that uses Linux are a very limited number of individuals and some University’s. To put it into perspective, I once meet a young guy that came to a place to teach in a private school, and he was shocked seeing there is a “internet”. He never heard about it before.

As the above article states, MS has purposely made it easy to copy and steal their products. There is no doubt about that.

I have yet failed to see one school, one single internet cafe, that had license for their MS products. I have a copy of a ridiculous “campaign”, MS had in Tanzania in 2010 and I hope to scan it and send it to the author of the article, that was very well written.

MS is partnering up with the World Bank, with all kind of projects, while the Linux distro’s, are hard to even find. And for sure they can not afford to download this and that as 95% of internet usage is pay pr MB”, using mobile internet.

The only solution for Africa and other third world countries, is to focus on education. Get in at the educational level, and even bypass the whole school and government systems. Education is rotten to its roots, with low end teachers, ability to by good grades, papers and corruption.

So there is the chance, as Africa has to become a society, whereas school papers will count less and less and what you can actually do, will be the key to work.
Get into their first experience, trough focusing on USB key
Get into their first experience, trough focusing on USB key computing, as most Africans can hardly buy a burnable CD.


As I see it, Puppy Linux Lupu is the absolute most “Third World Friendly” OS, followed by Slitaz Live DVD".

I beg you all please! spread this message everywhere.

I wish you a nice day brothers and sisters!
Back to top
View user's profile Send_private_message 
peebee


Joined: 21 Sep 2008
Posts: 1420
Location: Malvern, Worcs, UK

PostPosted: Mon 01 Aug 2011, 09:14    Post_subject: Re: smbc printer error  

rcrsn51 wrote:
peebee wrote:
I did my usual setup of a remote smbc printer to my XP box.Got the attached error when I tried to print....

The solution is to make the following symlink
Code:
ln -s /lib/libreadline.so.6.1 /usr/lib/libreadline.so.5


But I have no idea why 526 requires this but 525 does not.


Thanks rcrsn51

Confirmed - that fixes it.

Cheers
peebee

_________________
LxPup-14.03 = Puppy + LXDE
Back to top
View user's profile Send_private_message 
rerwin


Joined: 24 Aug 2005
Posts: 1515
Location: Maine, USA

PostPosted: Mon 01 Aug 2011, 11:52    Post_subject: Partial simulation of udev upgrade to activate rules  

playdayz,
Although this may make it easier to avoid upgrading udev to the lucid lynx level, I provide here a possible workaround for people to try. It activates udev rules that have never before been in effect in Lucid Puppy, so might cause concern for their possible impacts. Instead of moving the rules to the /etc/udev/rules.d directory (where they will be processed as expected), the package provides absolute links to each of the rules files in /lib/udev/rules.d (which are ignored by the current udev version). The package also has the 526RC versions of the two rc.update scripts that should remain as they are in 526RC.

I encourage anyone with a USB dialup modem, Wacom tablet PC (if anyone is going that route), USB SmartCard Reader (SCM), libgphoto2 devices, or SDP4430 sound card to try this workaround.

The newly activated rules files are:
    /lib/udev/rules.d/40-gnupg.rules
    /lib/udev/rules.d/40-libgphoto2-2.rules [needs udev 136]
    /lib/udev/rules.d/40-libpisock9.rules
    /lib/udev/rules.d/40-usb_modeswitch.rules
    /lib/udev/rules.d/40-xserver-xorg-video-intel.rules
    /lib/udev/rules.d/64-xorg-xkb.rules [needs missing file: /etc/default/console-setup]
    /lib/udev/rules.d/66-xorg-synaptics.rules
    /lib/udev/rules.d/66-xorg-tslib.rules
    /lib/udev/rules.d/69-xorg-vmmouse.rules
    /lib/udev/rules.d/69-xserver-xorg-input-wacom.rules [needs missing file: check_driver]
    /lib/udev/rules.d/90-alsa-restore.rules
    /lib/udev/rules.d/90-alsa-ucm.rules

While the usb_modeswitch file is definitely required, some of the others may not be, but probably would cause no trouble. To assist with evaluating the rules files, I attach a listing of their content (except for modeswitch). If any of the rules files should not be active, their link in /etc/udev/rules.d can be removed, to deactivate them.

I consider this a partial workaround because it does not provide the full support that udev 151-12 would. At least one of the rules files needs a udev version later than the current one.
Richard
old-udev_workaround-1.pet
Description  adds processable links to udev rules, as partial alternative to upgrading udev.
pet

 Download 
Filename  old-udev_workaround-1.pet 
Filesize  8.76 KB 
Downloaded  116 Time(s) 
lib_udev_rules.txt.gz
Description  udev rules to be activated
gz

 Download 
Filename  lib_udev_rules.txt.gz 
Filesize  8.22 KB 
Downloaded  111 Time(s) 
Back to top
View user's profile Send_private_message 
playdayz


Joined: 25 Apr 2008
Posts: 3788

PostPosted: Mon 01 Aug 2011, 11:58    Post_subject:  

Quote:
But I have news.
I installed the 526 on the dreaded Medion 8818.
It has an nvidia graphics card.
After booting and only using SeaMonkey, xerrs.log stays at some 57 lines.
No VDPAU messages.
It's logic, as nvidia is VDPAU ready. Others not.

So I wonder if there could be:
- a kernel parameter to disable VDPAU
or better
- disable automatically VDPAU in case a nvidia graphics isn't installed.


I think we have come pretty close to what you want Béèm, in the next RC release 5.2.7. I have it where gnome-mplayer and gecko-mediaplayer (in the browsers) do not generate the message. The messages in Seamonkey are from flashplayer. In 527 which I am working on, those flashplayer messages are also eliminated.

Credit where credit is due. In order to investigate the vdpau message I spent *a lot* of time in xerrs.log, and in that way I did discover a serious problem of one program going crazy and generating about 100 messages a minute. That is *very* bad. It would slow the computer down and perhaps even overload the filesystem if one didn't restart X fairly often to reset xerrs.log. I have notified the author of that program.

One helpful hint in general for everyone is that if Puppy slows down or becomes less responsive, it can help to Menu -> Shutdown -> Restart X server.

Quote:
So I wonder if there could be:
- a kernel parameter to disable VDPAU
or better
- disable automatically VDPAU in case a nvidia graphics isn't installed.


The thing is, this is not really a Puppy error. It comes mainly from flashplayer and what I think is some lazy programming. pemasu has found it reported in many places on the web. it looks like flashplayer doesn't bother to check whether you are using an nvida card or not--it just tries to load it and if it fails, that doesn't really matter--flashplayer still plays the video. Then some programs pass the message on to xerrs.log, but other programs are smart enough to know if doesn't matter and to null it. As I say, I think we have what you want in 5.2.7. Thanks.
.

Edited_time_total
Back to top
View user's profile Send_private_message 
playdayz


Joined: 25 Apr 2008
Posts: 3788

PostPosted: Mon 01 Aug 2011, 12:15    Post_subject:  

After Lucid. I have been thinking about this so I might as well post it. Pemasu mentioning EZ-Woof gives me the opportunity.

There will be an EZ-Woof 5.2.7 and I hope people will use it. One thing is that a newer kernel should plug right in--I know it's never that easy but pemasu has already done much work in that direction--and maybe this new business of udev will help further. EZ-Woof is also reasonably easy to update individual programs as well. A 5.2.7 built from EZ-Woof and a new kernel should be a Puppy Derivative, imho, until Slack Pup is released, and for at least a month afterwards, but after that who knows.

EZ-Woof is not good for simply installing the latest Woof. That is ultimately doable I think, but that is what Slacko will be doing so maybe the ghost of lucid should do something else. Maybe Lucid should remain the "last non-zzz" Puppy--or maybe it could even do both. Anyway, I will be available and happy to answer questions from people, once 5.2.7 is released.

However, I hope some of the people who have helped with Lucid will now go on to release Puppies of their own--well I am sure some will. One thing that i might mention is the difference between a derivative and an official release. I have found that an official release is a heck of a lot of pressure--the responsibility to develop a Puppy with almost zero problems that will represent all that Barry has built, is a big responsibility--there is a lot more development time and work needed. Everyone can see that, I don't know why I am saying it.

I know iguleder has also been interested in EZ-Woof--I would love to see the hybrid 64-bit system that he has mentioned. OK, now to see what rerwin has found.
Back to top
View user's profile Send_private_message 
playdayz


Joined: 25 Apr 2008
Posts: 3788

PostPosted: Mon 01 Aug 2011, 12:24    Post_subject:  

pemasu, I assume you used the udev from Ubuntu? I notice there is a lucid 10.04 update for udev. I am going to try that. Is there anything you have discovered that might help me? Thanks.

In case anyone would like to follow, my first thoguht was to use the Ubuntu Lucid-update version of udev, but oh my, that seems to be a big mess--with a lot of files that seem to me might conflict with similar files in Lucid puppy.

Now I am looking to see what version of udev is Barry's latest.

In both or either of those cases, rerwin's changes would overwrite what was in the udev package, so that might be OK after all.

More to come.
Back to top
View user's profile Send_private_message 
rerwin


Joined: 24 Aug 2005
Posts: 1515
Location: Maine, USA

PostPosted: Mon 01 Aug 2011, 12:44    Post_subject:  

playdayz,
Quote:
In both or either of those cases, rerwin's changes would overwrite what was in the udev package
I don't think my changes would replace anything in udev. However, the links would still be used, because the rules in /etc/udev/rules.d take precedence over those in /lib/udev/rules.d, but they would just run the same rules. Also, the rules are not part of the udev (151) package, so my workaround is independent of udev itself.
Richard
Back to top
View user's profile Send_private_message 
Sylvander

Joined: 15 Dec 2008
Posts: 3444
Location: West Lothian, Scotland, UK

PostPosted: Mon 01 Aug 2011, 12:54    Post_subject:  

1. Running Lupu-526, and used it to update the lupusave of Lupu-525.

2. All seems to be working well. Very Happy Cool
Haven't noticed any faults/flaws.
Back to top
View user's profile Send_private_message 
rerwin


Joined: 24 Aug 2005
Posts: 1515
Location: Maine, USA

PostPosted: Mon 01 Aug 2011, 13:10    Post_subject:  

Sage wrote:
rerwin:
Quote:
Your question is something every upgrader needs to know.

- care to advise on precautions relating to FULL installation upgrades, please?
I can speak only regarding the "update" process. The same update is done for full installations as for pupsave files. That includes copying all new-puppy files into the full installation.

Since the upgrade would simply be additive (except, now, for deletion of some old puppy-modprobe and modem files), some residue of past versions of apps could be left around. I think the same precaution applies -- uninstall all apps that you know are being upgraded in the new puppy. I would expect a new app version to read an old retained-data file or to adapt to retained-data changes between versions.

To clarify the terms: "Upgrade" means the replacement of puppy into an existing pupsave or full-installation environment. "Updating" is the process of merging the new puppy files into an existing environment.
Richard

Edited_times_total
Back to top
View user's profile Send_private_message 
Jim1911

Joined: 19 May 2008
Posts: 2457
Location: Texas, USA

PostPosted: Mon 01 Aug 2011, 13:22    Post_subject:  

Please provide the latest NVIDIA-Linux-280.13 driver in 5.2.7, otherwise please provide a link to the kernel source so that we can install the driver.

Thanks,
Jim
Back to top
View user's profile Send_private_message 
playdayz


Joined: 25 Apr 2008
Posts: 3788

PostPosted: Mon 01 Aug 2011, 13:29    Post_subject:  

I made a luci-268 with udev 151-12.3 from Ubuntu Lucid-upgrade and it booted. That is a good first step. Upgrading would be good for reasons pemasu mentioned *if* it can be done expeditiously and safely.

Now, I need to know how to handle the rules. The ubu udev comes with a bunch of rules in /lib/udev/rules.d. I will attach a screen shot.

Option 1. Delete them all and let the Puppy rules rule Wink The new udev would look in both places, and that was the problem as I udnerstand it--the old udev not looking in the new place. Therefore no symlinks would be necessary. Do I have this right?

Option 2. Leave the ubu rules. There are certainly a lot more rules than Puppy has. I could arrange it so that the Puppy rules would overwrite any ubu rules. This would be much more complicated than option 1.

I am now going to pursue Option 1 and see what I get.
ubu-rules.png
 Description   
 Filesize   98.48 KB
 Viewed   245 Time(s)

ubu-rules.png


Edited_time_total
Back to top
View user's profile Send_private_message 
playdayz


Joined: 25 Apr 2008
Posts: 3788

PostPosted: Mon 01 Aug 2011, 13:30    Post_subject:  

Quote:
Essentially, the updater will not delete your old app versions, which should override the newer versions.

If I am understanding this.
What good is an update of the save file?
The whole purpose of upgrading is to get the newer version, of a program, with the bug fix.

BTW rerwin, This seems like a good question to me also? I think you may be talking about old apps that were installed with a pet???
Back to top
View user's profile Send_private_message 
pemasu


Joined: 08 Jul 2009
Posts: 5463
Location: Finland

PostPosted: Mon 01 Aug 2011, 13:40    Post_subject:  

I have used ubuntu repo udev, not the one from ubuntu updates. Eventhough I tested several builds with both repos enabled. But the problem was that many packages had duplicates and it was a mess to remove the older ones.
Also ubuntu update packages broke the X. I couldnt boot to the X.
Code:
yes|udev|udev|exe,dev>null,doc,nls

>>>> udev_151-12_i386.deb

Edited_times_total
Back to top
View user's profile Send_private_message 
rerwin


Joined: 24 Aug 2005
Posts: 1515
Location: Maine, USA

PostPosted: Mon 01 Aug 2011, 13:47    Post_subject:  

playdayz wrote:
Option 1. Delete them all and let the Puppy rules rule Wink The new udev would look in both places, and that was the problem as I udnerstand it--the old udev not looking in the new place. Therefore no symlinks would be necessary. Do I have this right?

Option 2. Leave the ubu rules. There are certainly a lot more rules than Puppy has. I could arrange it so that the Puppy rules would overwrite any ubu rules. This would be much more complicated than option 1.

I do not believe there is a conflict in the rules files. Both puppy's and ubuntu's rules files can be retained, unless there is a reason to remove any of them. If there happens to be a match in file names between puppy's and ubuntu's, just rename the puppy file to avoid conflict. If I am missing such a conflict, please tell me.

If we go with the new udev, then please ignore my workaround package. Do not include the symlinks in lupu, but the rc.update files are there if you need them to restore the 526RC versions.
Richard
Back to top
View user's profile Send_private_message 
playdayz


Joined: 25 Apr 2008
Posts: 3788

PostPosted: Mon 01 Aug 2011, 13:57    Post_subject:  

Quote:
I do not believe there is a conflict in the rules files. Both puppy's and ubuntu's rules files can be retained, unless there is a reason to remove any of them. If there happens to be a match in file names between puppy's and ubuntu's, just rename the puppy file to avoid conflict.

Well, I went with Option 1. The result was that /etc/udev/rules.d and /lib/udev/rules.d look exactly as they do in Lupu-526. I regard that as a good thing. I will attach a screenie.

Now, the question, is it worth putting the ubu rules back in? And if so, how do I rename any conflicts? With a higher number? This is more complicated but if it would result in a better Lucid I can give it a go.

Thanks pemasu. The ubu update udev boots OK. There is also a udev_lib that I don't see in your entry, but maybe you had that in a separate entry. (I updated both udev and libudev0 (udev_lib).)

Quote:
If we go with the new udev, then please ignore my workaround package. Do not include the symlinks in lupu, but the rc.update files are there if you need them to restore the 526RC versions.


I tried the update udev option first so the rc.updates should be OK. I will check of course.
option1.png
 Description   
 Filesize   136.9 KB
 Viewed   580 Time(s)

option1.png


Edited_times_total
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 74 of 91 Posts_count   Goto page: Previous 1, 2, 3, ..., 72, 73, 74, 75, 76, ..., 89, 90, 91 Next
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1382s ][ Queries: 13 (0.0274s) ][ GZIP on ]