- WLUG - wlug.mailman3.com

REMINDER: Meeting Tonight 7:00 PM

by Andy Stewart

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 HI gang, Our monthly WLUG meeting is TONIGHT, Thursday, June 19th, 2008, at 7:00 PM. Our guest speaker will be WLUG member Frank Sweetser, who will be talking about GEGL, the Generic Graphics Library (http://gegl.org) I will bring a couple of books for the raffle: Running Xen, Prentice Hall 2008 Refactoring HTML, Addison-Wesley 2008 Afterwards, we'll go out for some food and fun! Please also note that our WLUG BBQ is coming up in July! The current date is Thursday, July 17th. We'll talk more about this during the June meeting. See ya there! Andy - -- Andy Stewart, Founder Worcester Linux Users' Group (http://www.wlug.org) Chelmsford Linux Meetup Group (http://linux.meetup.com/393) Amateur Radio: KB1OIQ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFIWlQgHl0iXDssISsRAgplAJ0VgDA4+QJOzJ85OS4OD2NAMv+nqQCdH7/c H0E/RxaaRREsfAh9imtphXw= =OmuK -----END PGP SIGNATURE-----

June 19, 2008

Re: [Wlug] KDE died on me

by Chuck Noyes

On Wed, 18 Jun 2008 20:09:37 -0400 Andy Stewart <andystewart(a)comcast.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > vze284qe(a)verizon.net wrote: > > Hello, > > > > KDE 3.5.9 died on me. I installed some updates via the adept > > updater and after rebooting, I get dropped into run-level 3 (which > > I actually prefer). When I type startkde, which is in /usr/bin, I > > get the following errors: > > Hello, > > I would recommend trying the following: > > cd ~ > mv .kde .kde.saveme > startkde > > If this works, it suggests that you have some user setting that is > causing KDE some grief. If it does not, we'll need more information > to help. > > Please let us know the result of this little experiment. > > Later, > > Andy > > - -- > Andy Stewart, Founder > Worcester Linux Users' Group (http://www.wlug.org) > Chelmsford Linux Meetup Group (http://linux.meetup.com/393) > Amateur Radio: KB1OIQ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2 (GNU/Linux) > Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org > > iD8DBQFIWaPAHl0iXDssISsRAmzaAJ4+8Vxg4E1V62VDbjkC00bgVTiV4gCggd2C > xulZXVvFcKu2X9i0pYG7wYE= > =k6Ty > -----END PGP SIGNATURE----- > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug Actually, I think I solved the problem.... I created .xinitrc file in my home directory that contains exec startkde then I ran startx and kde started up. I have to recreate some settings and configurations, but it looks like it's working. Thanks Andy. -- -Chuck

June 19, 2008

Re: [Wlug] KDE died on me

by Andy Stewart

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 vze284qe(a)verizon.net wrote: > Hello, > > KDE 3.5.9 died on me. I installed some updates via the adept updater and > after rebooting, I get dropped into run-level 3 (which I actually > prefer). When I type startkde, which is in /usr/bin, I get the following > errors: Hello, I would recommend trying the following: cd ~ mv .kde .kde.saveme startkde If this works, it suggests that you have some user setting that is causing KDE some grief. If it does not, we'll need more information to help. Please let us know the result of this little experiment. Later, Andy - -- Andy Stewart, Founder Worcester Linux Users' Group (http://www.wlug.org) Chelmsford Linux Meetup Group (http://linux.meetup.com/393) Amateur Radio: KB1OIQ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFIWaPAHl0iXDssISsRAmzaAJ4+8Vxg4E1V62VDbjkC00bgVTiV4gCggd2C xulZXVvFcKu2X9i0pYG7wYE= =k6Ty -----END PGP SIGNATURE-----

June 19, 2008

KDE died on me

by vze284qe＠verizon.net

Hello, KDE 3.5.9 died on me. I installed some updates via the adept updater and after rebooting, I get dropped into run-level 3 (which I actually prefer). When I type startkde, which is in /usr/bin, I get the following errors: Xsetroot : unable to open display '' Xset : unable to open display "" Xsetroot : unable to open display '' Startkde : Starting up. . . Startkde : Running kpersonalizer. . . Kwin : X server can not connect to Kpersonalizer can not connect to X server : Kpersonalizer can not connect to X server : Kpersonalizer can not connect to X server : If I type startx instead, the gnome window manager starts up fine. Any ideas??? I really prefer KDE. Thanks, -- -Chuck

June 19, 2008

FYI: Linux Admin / Contract 3-5 months / Framingham, MA

by Israel Ellner

My Name is Israel Ellner I am a Technical Recruiter with JVT Advisors. This new contract just came in. If there are circumstances in which you would consider job change now or in the future. Opportunities that you would like to explore based on location, technology or career growth. I recommend we spend a few minutes on the phone so I can ask you questions about your interests and match you responses with any suitable opportunities that meet your time table and expectations. I keep office hours Monday and Wednesday evening until 7:30 pm. You may send me your resume in confidence and contact me via e-mail or phone to set up a time to speak. Feel free to review my profile on linkedin. If you know of anyone who may benefit from consulting with me about resume preparation, compensation and benefit analysis, interview techniques or industry trends please feel free to pass my information forward. Job Order: IJE7355 Job Title: UNIX Administrator (Linux) Location: Framingham, MA Position Type: Contract 3 months + could go longer Rate: Open (Market) Contact Israel Ellner e-mail israel(a)jvtadvisors.com phone 978-557-7140 Responsibilities: * Operating system and hardware support for Linux servers / clustering. * Server performance, performs back-ups and restores Disaster Recovery, problem tracking. * Investigate / solve problems / escalates serious issues. * Manages hardware / support calls to vendors. * Implementation of hardware / software. * Assists technical, development / end-user if needed, * Assists security, scheduling, / compliance. * Documents procedures / policies. * Senior level experience with Suse / Redhat. * Current experience in a Systems environment, including analysis, design, implementation, security, back-up/restore and support of UNIX Operating Systems. * Strong partitioning & virtualization, software and hardware upgrade, Sarbanes-Oxley and Audit compliance, Disaster Recovery, and remote access configuration. The following technical skills are a plus: AIX, HP-UX, Windows XP, DB2, UDB, Networking, Websphere, Apache, VMware, C++, NIM, LDAP, Disk/Storage Management (ESS, HP, EMC, other), HACMP, MQseries, Candle Omegamon, Oracle and Tivoli Monitoring. Contact Israel Ellner e-mail israel(a)jvtadvisors.com phone 978-557-7140 Click to view my Current <http://www.4uisearch.blogspot.com/> Opportunities Sincerely, Israel Ellner, Senior Consultant JVT ADVISORS 35 New England Business Center Andover MA 01810 Main (978) 683-4555 Direct (978) 557 - 7140 Fax (978) - 681- 4569 <mailto:israel@jvtadvisors.com> israel(a)jvtadvisors.com www.jvtadvisors.com <http://www.jvtadvisors.com/> http://www.linkedin.com/in/israelellner

June 18, 2008

Re: [Wlug] inconsistent results with du and multiple arguments

by Brett Russ

On Wed, Jun 18, 2008 at 10:35 AM, Chuck Anderson <cra(a)wpi.edu> wrote: > On Wed, Jun 18, 2008 at 10:20:08AM -0400, Brett Russ wrote: > > Thanks Mike, looks like it is related to the -x argument: > > http://www.mail-archive.com/bug-gnulib@gnu.org/msg04655.html > ... > > Chuck, > > If it were rounding error I should still be able to make direct > comparisons > > between the results, as long as they all used the -m argument. > > In my tests, with or without -x didn't make a difference: > > >du -smxc yum jigdo > 1 yum > 48 jigdo > 48 total > >du -smc yum jigdo > 1 yum > 48 jigdo > 48 total Your version of du does not have the bug that I was writing about. I believe versions 6.1 - 6.6 were affected. The issue I had was that the second file/dir argument onwards was not properly tallied. So, using your example, jigdo would show a size of 1 if it were run as: >du -smxc yum jigdo but if you changed the command line to: >du -smxc jigdo yum Then jigdo would show the correct size of 48. -BR

June 18, 2008

Re: [Wlug] inconsistent results with du and multiple arguments

by Chuck Anderson

On Wed, Jun 18, 2008 at 10:20:08AM -0400, Brett Russ wrote: > Thanks Mike, looks like it is related to the -x argument: > http://www.mail-archive.com/bug-gnulib@gnu.org/msg04655.html ... > Chuck, > If it were rounding error I should still be able to make direct comparisons > between the results, as long as they all used the -m argument. In my tests, with or without -x didn't make a difference: >du -smxc yum jigdo 1 yum 48 jigdo 48 total >du -smc yum jigdo 1 yum 48 jigdo 48 total But leaving off the -m, the total is the correct sum of the two directories: >du -sxc yum jigdo 416 yum 48660 jigdo 49076 total I think that du -mc is adding the sizes first, then converting to 1 MiB blocks, therefore showing the approximation error in the total. In the -m case, 416 KiB rounds to 1 MiB, 48660 KiB rounds to 48 MiB, but the total isn't calculated as 1 + 48, but rather as 416 KiB + 48660 KiB = 49076 KiB, 49076 KiB / 1024 = 47.92 MiB, which rounded off becomes 48 MiB.

June 18, 2008

Re: [Wlug] inconsistent results with du and multiple arguments

by Brett Russ

On Wed, Jun 18, 2008 at 7:08 AM, Mike Frysinger <vapier(a)gentoo.org> wrote: > this has come up on the gnu coreutils list in the past iirc (so try > searching > their mail archives). i think it was one part bug and one part unexpected > for the user. make sure you're using coreutils-6.11. once you have that, > i > think the way symlinks are counted may not be as you expect. > Thanks Mike, looks like it is related to the -x argument: http://www.mail-archive.com/bug-gnulib@gnu.org/msg04655.html I've confirmed it's fixed in coreutils-6.9-43, but haven't yet checked on my home machine where I saw the problem. Pretty sure it's the same thing though. Chuck, If it were rounding error I should still be able to make direct comparisons between the results, as long as they all used the -m argument. Thanks, BR

June 18, 2008

Re: [Wlug] inconsistent results with du and multiple arguments

by Chuck Anderson

On Wed, Jun 18, 2008 at 06:42:18AM -0400, Brett Russ wrote: > Can anyone explain why du (which advertises the ability to evaluate N > file/dir arguments) seems to only be accurate for the first provided > argument? See the following: > > brett@spider:/> sudo du -smxc tmp > 60 tmp > 60 total > brett@spider:/> sudo du -smxc tmp bin > 60 tmp > 1 bin > 60 total Try without the -m argument. You may be seeing round off error.

June 18, 2008

Re: [Wlug] inconsistent results with du and multiple arguments

by Mike Frysinger

On Wednesday 18 June 2008, Brett Russ wrote: > Can anyone explain why du (which advertises the ability to evaluate N > file/dir arguments) seems to only be accurate for the first provided > argument? See the following: > > brett@spider:/> sudo du -smxc tmp > 60 tmp > 60 total > brett@spider:/> sudo du -smxc tmp bin > 60 tmp > 1 bin > 60 total > brett@spider:/> sudo du -smxc bin > 9 bin > 9 total > brett@spider:/> sudo du -smxc bin tmp > 9 bin > 1 tmp > 9 total this has come up on the gnu coreutils list in the past iirc (so try searching their mail archives). i think it was one part bug and one part unexpected for the user. make sure you're using coreutils-6.11. once you have that, i think the way symlinks are counted may not be as you expect. -mike

June 18, 2008