| ||||||||||||||
The Lockergnome staff is in a frenzy of preparation. If you're going to Gnomedex, have a great time! I won't be there this year since I'm so busy churning out material (and didn't know early enough to leave the time open in my schedule), but maybe next year. However, I'll have friends and compatriots there, so I'll be virtually with you. Not that much else to say this week. Workin' hard, hopin' Canada Post doesn't go on strike in the morning, and I'll talk to you folks next week. Anything you want to see in particular? Gimme a shout and I'll see what I can do. Digitally Yours,
Finding Out What You're Running
Brad B. asks:
I'm such a geek. I like working at the console. Of course, you can
also open a terminal window in your GUI and not completely leave
the GUI if you're not comforable when faced with only a black
screen with white letters. I've decided to cover this in EGGS
instead of MAN because there's a number of ways to do this,
partially depending on what distribution you're running.
If you're running an RPM-based distribution, such as Red Hat,
Mandrake, or SuSE, you can get a package's version number by using
the
This gives me the results:
The last item in the version number, the -26, is probably related
to the distribution's version of the Python package. This one
would be the 26th variant on Python 2.2.2. Don't worry about this
issue. What matters is the 2.2.2.
If you're running a DEB-based distribution, like Debian or
Knoppix, then you can find out what version of the package in
question is using the
This gives me the following results when I type it in Knoppix:
If you're not utilizing RPM or DEB, don't worry. There's a number
of ways you can find out what version you're running. If you're
running the version that came with your distribution, you can use
the filesystem movement commands (
Finally, you can usually ask a program itself what version it is.
Just like you can find this information in a GUI tool by clicking
So, I get out with
Submit a Resource | Discuss | Recommend It!
Already, these have created quite a buzz online. Robert Skobel
says: "I love these white tees!" John P. Dvorak claims: "I predict
that in one month, everyone will have one." Dave Wyner notes:
"Yes, but are they RSS compatible?" Gnome-Girl exclaims: "Yo,
dawg! They be fly and all that sh*t." Joey Ito writes: "I stuck
one on my wiki." Slashdoft cheers: "There's no other t-shirt like
it - anywhere." Jayson DeFillippo scribbles: "I wash mine in
SOAP." Menah Trott proclaims: "I love #FFFFFF stuff." Jason Blair
extols: "It's the one thing I dare not say is mine."
UPDATE: Mark Kanter spews: "I'll wait for someone else to
review it, and then quote them heavily in my blog - which has an
impossible URL to remember." Anvil Dash screams: "I'd rather go
naked." Even Williams asserts: "I'd rather see Anvil Dash go
naked." Halley Suit interjects: "All the alpha males are wearing
them." Dock Surls laments: "I lost mine last year." Don Boxx
giggles: "I wear it when I code." Metaflitter chimes: "This is
your worst post yet, Chris." Lowernce Lessig laughs: "I've already
copywritten mine." Tim O'Rally records: "We're already writing a
'Gnomedex T-Shirts Hacks' book."
Compiling Software from Source, Part IV
So, I grabbed the latest non-beta TIFF libraries from ftp://ftp.remotesensing.org/pub/libtiff (tiff-v3.5.7.tar.gz), the latest PNG
libraries from ftp://swrinde.nde.swri.edu/pub/png/src/ (libpng-1.2.5.tar.bz2) and the latest
JPEG libraries from ftp://ftp.uu.net/graphics/jpeg/ (jpegsrc.v6b.tar.gz).
I start with tiff, uncompressing and unpackaging it. It's an
Autoconf setup so I type
Now, I cross my fingers and type
Finally, I'm out of the detour. I go back and look at last week's
article (isn't that sad?) to find that it was gtk+ that I was
trying to build when I had to go off chasing libraries. Again, I
cross my fingers and type
Next week: I continue with the valiant struggle that
is compiling GNOME from source.
(I'm sure the GNOME team would laugh at me. They've got a special
method for doing this that's a lot easier. But that's not the
point, as I said before. This is a learning "workshop.")
Submit a Resource | Discuss | Recommend It!
Introduction to DocBook, Part III
So far, I have the file:
Now, rather than having my numbered list embedded in the
paragraph, I want to break it up. For that, I need a procedure:
That wraps up your introduction to DocBook. Go forth and make
documentation!
Submit a Resource | Discuss | Recommend It!
"Might be a little belated, but 'Welcome!' to the Gnome crew. Seems like you're settling in well. I'm a Linux-user wannabe (it is part of my new job's responsibilities), and the newsletter has been helpful for information. I look forward to the future.Dee-Ann responds: I have used VMWare on occasion, but I find it cumbersome and often not as reliable as I'd like. Where it comes in really handy is when I need to get screenshots of things where it's otherwise almost impossible to do so! It's hard to get a BIOS screenshot, for example, since the computer isn't even really running. :) However, one of you readers might find VMWare quite useful! Submit a Resource | Discuss | Recommend It! Author Morris Rosenthal has taken the boot failure diagnosis flow charts from his latest book, Computer Repair with Diagnostic Flowcharts - ISBN 0972380116 ($14.95). You can get the free poster through the book's main page. Submit a Resource | Discuss | Recommend It!
In response to the problem regarding SuSE Linux and the CD player,
Joe Joseph says: |
Cool Tools: GnomeDomains GnomePortable Gnomies.com GnomeSavings GnomePersonals GnomeJobs
Reading Materials:
Current Content:
Our Community:
Contact Us:
Question: which group is 250,000+ strong and always looking for stuff to make their personal and professional lives run smoother?
©1996-2003, Lockergnome LLC. ISSN: 1095-3965. All Rights Reserved. Please read our Terms of Service. Web site hosted by DigitalDaze. Domain registered at DNS Central. Powered by Lyris ListManager. Chris Pirillo fueled by Peet's Coffee. Headers provided by Habeas. Statistics provided by Urchin. | |||||||||||||