Category: Computers

Posted on

FUDCon 2011 — Tempe, Arizona

Well, here I am, I finally did it. I’m going to FUDCon 2011 in Tempe, Arizona.

After months of saying to myself and friends “Oh I think I’d like to go do this” and asking my brother if he’s interested, and telling all sorts of people “Yep I’m doing it, I’m thinking about doing it, I’m still in the talking about it stage; I just haven’t committed to it yet”, I bought my airline tickets a couple of weeks ago to go to Phoenix, Arizona, and made reservations at the hotel. (Yes, the nice people at the hotel, months after the block was “closed”, graciously gave me the Red Hat Group rate for 6 out of 7 nights — quite the savings!)

So I’ve been working for the past few weeks at translating, updating, revising, rationalizing, etc. a presentation on System Security I presented at my local LUG a couple of years ago. (Of course it’s not in English, silly, why do you think I’ve had to work on translating it?) I’ve also been following the wiki page for the event (here’s my archive of the page).  I even have my Fedora Friend Finder (here’s my archive of the page, since the webpage disappeared) ready to bring with me.

But … apart from a few blog posts here and there, and of course the availability of the administrative notices / minutes from the planning meetings, I haven’t found what appears to be, let’s say, an online forum where FUDCon is being discussed. (Yes, I know, there’s Planet Fedora — however, it seems to discuss pretty much everything under the Red Hat sun.) The kind of place where people discuss what they’re doing outside of the formal event structure, when they’re arriving, asking questions of participants of previous such events, and so on. Basically, chatter.

I’m wondering a few things, and hope that perhaps this post will help me out in at least finding a nudge in the right direction:

– Is there a forum where people are virtually gathering and discussing the plans and attendance and logistics and so on surrounding going to FUDCon? You know, chatter?
– Assuming that my presentation isn’t tossed for being too long, too technical, too boring, out in left field, or targeted to the wrong audience (it’s sysadmin stuff, not development), will there be a projector available? Will I need my laptop — which I’ll of course have anyway — or just a USB memory stick with the presentation on it? (OO.o format, or PDF? Of course I’ll be ready for all of these circumstances.)
– Regarding my presentation, will someone be wanting it to be submitted in advance for the part about “Refereeing for technical sessions”? Or will “in advance”, in keeping with the “so do not worry about competition” part, mean half an hour before the “Orientation, BarCamp pitches and scheduling” at 9:00am Saturday?
– I signed up after the 140 cut-off mark for food and swag. I don’t have a problem with the basic concept per se: you snooze, you lose, you should have signed up earlier. However, I’m just wondering what the real implications to this are — to what food is being referred? Breakfast, lunch, and supper throughout all the event? Snacks in the hospitality suite — no green stamp on your name tag, no food? A few chits for free meals, given to the first 140 people, at the Student Union cafeteria where a lot of people presumably will eat during the breaks? Food during the FUDPub, at which Red Hat “will be treating everyone to food”? (Or just the first 140 — everyone else with a differently-marked name tag will have to pull out their wallets?) I’m just trying to figure out logistics, that’s all; I’m trying to find the ad for the advertised food, so that I know what’s being discussed. Money isn’t the issue; I’m just looking for some kind of indication, that’s all.

Well, that’s off my chest.

In other directions, I guess I now have to prepare my laptop for going through customs:
– set up an automatic login (a warning against which is in my presentation);
– do a bit of a system cleanup (a suggestion about which is in my presentation);
– remove some privileged information and make sure that it’s really wiped;
– realize that US Customs probably won’t care about my computer, and that the only people who might will be the airline — and hopefully only be amused at the XRay area when they see the square, plastic bucket I carry it in (but hopefully not say that’s it’s oversized, which it shouldn’t be. The primary airline’s limits are 23 cm x 40 cm x 55 cm; the secondary airline’s limits are 23cm x 35cm x 56 cm. I’ve just checked, and it fits.)

Posted on

Free PDF splitters, and other crippleware

Yesterday I downloaded a PDF splitter to use on my MS computer at work. And I got bitten, hard. I wouldn’t exactly call it crippleware; most people expect even crippleware to be minimally useful. This piece was not.

I shall quote the message that I sent to their support email addy:

I am writing to let you know that your free trial download for the PDF splitter is not a useful piece of software at all, for the simple reason that it intentionally and flagrantly renders the split documents useless by inserting the “watermark” — a large message spanning the diagonal of the page, in cherry red characters, saying “in order to remove this message please visit our website” — across every page of the document.


Were it to put a far more discreet message along the top or bottom, this might be tolerable however ugly it would be; however, it is hardly of any value to anyone wishing to take advantage of the “15 free uses” or somesuch in order to evaluate the software before deciding to purchase it; in fact, I expect that most people downloading the evaluation copies are immediately turned off by this malfunction.

Obviously, I don’t expect a response from them, at least not a useful response. Obviously, I would never have bought the software to begin with were I to have had a good experience using the software — I admit it, I’m cheap.

And sure, I should have thought things through a bit better and (as I mention below) install Ghostscript to do the job. Sure, I was in a bind and embarrassed myself and my employer in front of the client.

So of course, the following reactions come to mind:

– What, the programmer(s) wanted to show off their skill at insering “watermarks”, and that are ugly to boot?
– Or did the programmer or company put more thought into the dollar signs floating in front of their eyes than, oh, I don’t know, producing a piece of software that someone may actually wish to buy?
– Or did the Marketing Department convince the programmer’s supervisor that the watermark had to be put in?

And on a personal level:

– I should install ghostscript and run:
“gswin32c -sDEVICE=pdfwrite -dNOPAUSE -dQUIET -dBATCH -dFirstPage=m -dLastPage=n -sOutputFile=out.pdf in.pdf”
– I should stop trying to delude myself that there won’t be an ever increasing number of useless PDF tools out there that require you to buy the product before getting a true evaluation copy;
– When using my work computer, stop using a Windows mentality, and apply a thing or two that I know how to do under linux.

Of course in the short term, what I did was speak with the secretary very nicely, who has Adobe Professional to split the file, and she did.

My point should be clear: If you want to sell your software, go right ahead; I won’t be buying it anyway. And if you want to give away a trial period during which people can, well, try the software, go right ahead; I may try your product during the trial period. But why give a free trial period (in the case above, 15 operations) that reflects poorly on the company and actually annoys your potential customers?

Posted on

Powersurge is a hit!

A few months ago I found a computer on the sidewalk and installed PC-BSD on it. Once I got over the novelty of having done an install, installed something sufficiently “different” from that to which I’m accustomed, etc. etc. etc., the computer languished on my floor beside my home server with no purpose. I never bothered trying other linux distros (partly due to what proved to be the spaghetti wiring inside making my original install seem like a fluke, as it turned out, since I subsequently had trouble booting in and getting the CD players to work), and finally offered it to my brother, who said it’s been a while since he’s had a home server.

To recap, it’s an AMD 1000MHz with 512megs of memory, and to my surprise, an 80gig hard drive (I seem to recall having gotten about 36Gigs out of it with the PC-BSD setup.)

Last weekend we installed Fedora 13 on it after figuring out the spaghetti wiring inside. He brought it home from the cottage, did the updates and started doing his custom setup. Since it’s been a little while since he’s used Fedora — using CentOS on his production servers and having converted to Ubuntu on his desktop, he was impressed at how peppy the Gnome desktop is, and how polished and stable overall the distro is.

And finally, it seems that the problem of it not booting up a few months ago at the cottage has been solved: it seems that it was a defective power cord. The machine worked everywhere else, and when we went through my set of power cords, one didn’t work, so we figured out that any possibility that the previous owner thought it had been fried in a power surge — hence the name of the computer — was due to a faulty wire, that probably came with the computer on the side of the street.

Posted on

News Flash — Linux spotted in the wilds of Montreal — again!

Back in January I mentioned a chance meeting with someone on a commuter train using Fedora on their laptop. Well this afternoon, I had another such chance meeting in a pub.

At a 5 à 7 (Quebec speak for “Happy Hour”) at Hurley’s Irish Pub on Crescent Street this afternoon, I walked by someone with a laptop listening to the Irish musicians, and almost walked by, the Ubuntu icon in the corner of the screen was so familiar (despite being a die-hard Fedora user). I realized my error and exclaimed “Wow Ubuntu in the wild!”

I got a quick look at Ubuntu Netbook Remix using Chrome. Dan, the user, said that though he uses Firefox at home on his desktop, he finds that Chrome is way faster at least on his netbook. He said that the machine came with another Linux distro when he bought it, which he didn’t much like, so he reformatted.

Well, Dan, you made my day!

Posted on

I wonder about the new machine

I brought the “new to me” 1GHz AMD to the cottage last weekend, and funny enough it didn’t power up at all. My brother declared the power supply fried, and that that was the likely reason why I found it on the side of the road.

Today I got around to plugging it in, forlorn that a perfectly good computer was suffering from “no power”.

Go figure. I’m typing this from the PC-BSD setup.

I had tried two or three outlets and three power cords. It likely isn’t circuit overload since the current circuit it’s on is also likely overloaded, and I’m using one of the same power cords.

As for the screen, I had difficulty getting it work here too last week but am still holding off until I get a proper cable, since the “cottage test” doesn’t seem to have been valid.

Posted on

Found a ‘puter, it seems useful, installed P-CBSD!

(yes, I know it’s really PC-BSD. I was trying to sing “Found a Peanut” to the tune of Clementine.)

Today I found an old computer AND a 19″ flatscreen on the street, and as per my wont I picked them up, hoping that they would be vaguely useful.

The flatscreen should hopefully prove useful, once I get myself a cable for it.

And the winner is … it’s an AMD 1.0GHz with 512megs of RAM and a hard drive that the windows install said was about 35-ish gigs; I remember the PC-BSD install seemed to only mention about 18 ish but I could be wrong, or it could have done a partition … I don’t know what I’m talking about right now, so I’ll look things up.

The point is, the computer isn’t a clunker, and I’m typing this on the PC-BSD setup (somewhat frustratedly: I’m accustomed to a French-Canadian keyboard, and despite having specified one during setup it’s still acting like an US-English keyboard — I have the same problem with Fedora, funny enough, the installation ignores the designation and even occasionally “forgets”.)

So now I have to decide what to do with it:
– Have a second server (I barely if at all need the first, it certainly does little that my desktop does beyond a few technicalities which could be resolved by switching things around, and of course generate heat);
– Offer it to my brother, but he’s already declined on the basis of claiming to not need another computer in his life at the moment;
– Bring it to the cottage — not much use since I have a laptop, although I suppose that there could always be an argument for it;
– Or, do what I’m planning: Test out various distros with it. I figure I should give each one a couple of weeks or so and try to put things through their paces. One of these days, I’m going to have to try Slackware. Just to annoy my brother, who has always worked on the warning from a friend along the lines of “steer clear of slack, it almost cost me my business.” (In 1995-ish, I should point out.)

Posted on

Google Maps seems to need to learn that some streets go East AND West

I think that Google Maps is overlooking a basic function: In the real world, people sometimes go east, and sometimes go west.

Yesterday for the third time in a couple of years I relied upon Google Maps for directions and was sent to the wrong place. Caveat Emptor strikes again.

In Montreal, east-west streets which bisect St. Laurent Boulevard (which, no surprise, goes sort of north-south), start their numbering in both east and west directions from there. Hence you can have two equally valid addresses on a given street, given the proviso that one is designated as “East” and the other “West”. (Hey! It’s Captain Obvious!)

Fortunately, the address I was looking for was 151; during an hour of going around the neighbourhood looking for parking around “151 Laurier” (East as proposed by Google Maps), I found out that that address wasn’t a dépanneur that sells a huge variety of microbrewery beers, and looked like it never was, and finally decided to go further down the street looking for similar businesses. I suddenly had a V-8 moment and realized “Ooops what about 151 Laurier WEST?” I high-tailed it in the opposite direction and found the business in question. And to my disappointment, they were out of the particular beer I was seeking — Weizenbock, by La Brasserie Les Trois Mousquetaires, which has replaced my previous definition of ambrosia, Trois Pistoles by Unibroue.

Twice before I have had similar experiences:

About a year ago, while in Western Canada in completely unfamiliar territory on a business trip, I had looked up a client’s address, and not knowing about any local east/west splits that addresses on the Trans-Canada Highway may have in that locality, I tried to find the address, on the east end of town, that Google Maps had provided; I was about 45 minutes late by the time I finally managed to suspect that my client’s address was a “West” address and got there.

And just to quash any participant in the Peanut Gallery out there about to say “Aha well when using Google Maps you should know that in such cases they’ll always send you to the East address, so be sure to always check both!” a couple of years ago I had looked up a local address for client, and Google sent me to Gouin Boulevard West here in Montreal, a solid 45 minute drive away from my client’s Gouin Boulevard East address.

Now the Peanut Gallery may have a point: In the real world, people sometimes go east, and sometimes go west. And when it comes to using a free online service, you get what you paid for. As such, when looking up an address on any online service, one should notice “Hmmm this is an east-west street which may bisect such and such a street and as such have East addresses and West addresses; I should specify both east and west in my address search.”

But I wonder how many other people place enough faith in Google that under such circumstances — such as when they don’t know that there’s an East and West of a given street — they would reasonably expect in the case that a street has valid East addresses and valid West addresses (and likewise for North and South addresses) that Google’s response page would come back with “Did you mean (A) 151 Laurier East, or did you mean (B) 151 Laurier West?” Certainly Google seems good enough at asking such a question when you slightly misspell a street or city name, or decides that it doesn’t recognize the address you supply and provide you with half a dozen options, as often spread across the country as spread across the city.

Posted on

Cool (or mundane) computer trick impresses co-worker

I managed to impress someone at the office this week with a cool (read mundane) computer trick.

I got a call from the secretary, who is a few seconds’ walk from my desk, asking for a scanned version of my hand-written signature. I replied that on my computer at home I have it, and I could easily get it within a few minutes; she replies that it would be faster for her to just walk over with a piece of paper for me to sign, which she would then scan and play around with.

And this is where I began to impress her: By the time she got to my desk with said sheet of paper, I had already VNC’d into my home server’s desktop and was in the process of doing the same from the server to my main computer’s desktop (gotta finish the process of giving it a static IP and setting it up so that I don’t have to go through my home server. 🙂 ) I finished logging into my desktop, and looked in the likely directory, and voilà ! I fired up my home email client, and within a couple of minutes, she’d received my scanned signature.

Beyond the fact that the Gnome desktop is set up standard to do VNC — and the fact that I installed TigerVNC instead of using the standard Gnome Remote Desktop Viewer — too bad that I can’t really claim that this is a cool Linux trick, since my computer at work is Windows, and you can set up Windows boxes to “pick up the phone” too ….

She was still impressed, though. And it took about as much time as the whole process of signing a piece of paper, scanning it, cropping it, etc.

Posted on

PDF’s, Scanning, and File Sizes

I’ve been playing around with PDF’s for the past few weeks and have noticed a very interesting thing: A PDF is *not* a PDF is *not* a PDF is *not* a PDF, ad nauseum, and it would seem, ad infinitum. At least, so it would seem. Part of me almost wonders if the only distinguishing feature of a PDF is the .pdf extension at the end of the file. In “researching” this post I have learned what I knew already; PDF boils down to being simply a container format.

Lately I have been scanning some annual reports from years past for an organization I belong to, and due to the ways xsane 0.997 that comes with Fedora 12 scans pages — which I will concede straight out of the gate I have only explored enough to get it to do what I want and to learn how it does things “its way” — the PDF file sizes are “fairly” large.

In order to find this out, I first found out about one of the quirks in xsane 0.997: Something about the settings with xsane doesn’t have it stop between pages for me to change pages; at least, I haven’t gotten around to finding where the settings in xsane are to have it pause between pages. This is important because my scanner doesn’t have an automatic page feeder. The first page of results of a google search indicate several comments about this problem, but not a solution. At first glance the second page of results is of no help.

So I end up scanning pages one at a time, and then use GhostScript to join them all up at the end to make a single PDF.

Without having added up file sizes, it was obvious that the total size of all the scanned pages at 75 dpi and in black and white was sufficiently larger than the single PDF with all the pages joined. This did not bother me since, again without having added things up, the difference didn’t seem *too* great, and I assumed that the savings were principally due to adminstrative redundancies being eliminated by having one “container” as opposed to having 25 to 30 “containers” for each individual page.

Then this week a curious thing occurred: I scanned a six page magazine article, and then separately, another two page magazine article, at 100 dpi and colour, and whaddya know, the combined PDF of each set is smaller than any of the original source files. Significantly so. In fact, the largest page from the first set of six pages is double the size of the final integrated PDF, and in the case of the second set of two pages, each of the original pages are triple the size of the combined PDF. I’m blown away.

Discussing this with someone who knows the insides of computers way more than I, I learn something: It would appear that xsane probably creates PDF’s using the TIFF format (for image quality) as opposed to what I imagine Ghostscript does when joining files, which would seem to be to do what it can to reduce filesizes, and as such in this case I imagine convert the TIFF’s inside the PDF’s into JPEG’s. A bit of googling indeed appears to associate tiffs and PDF’s when it comes to xsane; indeed a check on the “multipage” settings shows three output file formats — PDF, PostScript and TIFF. And looking in Preferences/Setup/Filetype under the TIFF Zip Compression Rate, it’s set at 6 out of 9.

So I google PDF sizing, and one result led me to an explanation of the difference between using “Save” and “Save As …” options when editing a PDF: “Save” will typically append metadata on top of metadata (including *not* replacing the expired metadata in the “same” fields!); “Save As”, well, that’s what you really want to do to avoid a bloated file since all that should be will be replaced.

Another result begins describing (what is no doubt but a taste of) the various possible settings in a PDF file, and how using a given PDF editing application, you can go through a PDF, remove some setings, correct others, etc., and reduce the size of PDF’s by essentially eliminating redundant or situationally irrelevant — such as fields with null values — information whose presence would have the effect of bloating the file unecessarily.

I’ve known for a few years that PDF’s are a funny beast by nature when it comes to size: For me the best example by far used to be the use of “non-standard fonts” in the source file, oh say any open-source font that isn’t in the standard list of “don’t bother embedding the font since we all know that nine out of ten computers on the planet has it”. In and of itself this isn’t a problem; why not allow for file size savings when it is a reasonable presumption that many text PDF’s are based on a known set of fonts, and most people have said known set of fonts installed already on their system. However, when one uses a non-standard font or uses one of the tenth computers, when one constantly creates four to 6 page PDF text documents ten times the size of source documents, frustration sets in; having wondered if designating a font substitution along the lines of “use a Roman font such as Times New Roman” when such a font is used — such as in my case, Liberation Serif or occasionally Nimbus Roman No9 L — I asked my “person in the know”. Apparently, Fedora 12’s default GhostScript install, whose settings I have not modified, seems to do just that.

I guess what really gets me about this is how complicated the PDF standard must be, and how wildly variable the implementations are — at least, given that Adobe licences PDF creation for free provided that the implementations respect the complete standard — or more to the point, how wildly variable the assumptions and settings are in all sorts of software when creating a PDF. I bet that were I to take the same source and change one thing such as equipment or software that the results would be wildly different.

So, concurrent to the above scanning project, I happened to experiment with a portable scanner — a fun challenge in and of itself to make it work, but it did without “too much fuss”. And I found out something interesting, which I knew had nothing to do with PDF’s but (I presume) rather with scanners, drivers, and xsane. I tried scanning some pages of one of the said annual reports with the portable scanner on an identical Fedora 12 setup using xsane, and the PDF’s that were produced were far greater in size than those scanned with my desktop flatbed scanner. My flatbed scanner would scan the text and the page immediately surrounding the text, but correctly identified the “blank” part of the page as being blank, and did not scan in those areas, thereby significantly reducing the image scanned size. The other scanner, a portable model, did no such thing and created images from the whole page, blank spaces rendered, in this case, to a dull grey and all, thereby creating significantly larger PDF files than the scans of the same pages created on my flatbed scanner. However, as I mentioned, I assume that this is a function of the individual scanners and their drivers, and possibly how xsane interacts with them, and in my mind is not a function per se of how xsane creates PDF files.

Another interesting lesson.

Posted on

Fedora 12 installed — I’m a linux addict with an install every 6 months habit

Well over the past couple of weeks I’ve just installed Fedora 12 on three systems — mainly because I got a great great great new P4 3.0GHz home server, which I have been considering using as my desktop while using my current desktop as the server, a P4 2.8GHz.

To my dismay I have done this 6 months after I made a point of having the same version of Fedora on all my computers so as to avoid the “reformat a system every six months” treadmill that I was on by having different versions, because, well, my old server died and of course there was no point to putting a 6 month old version of Fedora on which I would only *have* to change 6 months from now, anyway … Sigh, the bliss of using CentOS, were only it not so completely obsolete, I would love to use it again … However on the other side, Fedora is the crack cocaine of “latest and greatest”, so for the moment there’s no going back!

All of this started back in, what, September, if not before; I couldn’t get the 80 gig drive and the 500 gig to play nice together, or so I thought. There *was* an issue with different spin speeds, but wait folks, there’s more. When I *did* have the 500gig as the boot disk, something seemed off with the amount of available storage, although I wasn’t fully aware. When I finally brought the 500 back as the boot drive, the installation went well several times with Fedora, then with Centos 5.1 (which would have been promptly updated upon reboot.) Except, the first reboot wouldn’t work, the system would freeze, and the keyboard buffer would fill up real quick. Forums were of little help, with sufficient dead ends and apparent red herrings. Finally, I started figuring out on my own that the BIOS was way too old to recognize such a large drive, and flashing it with a “new” bios would have required a lot of fun with WINE, which I wasn’t really wanting to get into using a live CD.

Christmas and a new server came along, and I’m up and running with a desktop upgraded from june 2008 — CentOS 5.1 to 5.2, July 2008 some version of Ubuntu, December 2008 Fedora 10, July 2009 Fedora 11, and now January 2010 Fedora 12 … and a netbook, a laptop which is no longer used, an old server, and a new server following a similar route for much of the way each. So much for even taking advantage of Fedora’s “1 month after the release of the second version following” … I’m still upgrading every 6 months!

As a result, though, I finally now have refined my “to-do” list when installing a machine so that it’s not so much of a hassle, and in fact two of the three setups were not only a breeze in and of themselves but the to-do lists also made the rest of the work a breeze, too. Of course my brother told me two years ago that his list was 300+ steps long and he’d found a two year old such list, that was only about 120+ items long. My list is currently somewhere around 58 items long depending on how you count it … I wonder how long it’ll take to get to 300? 🙂

However, I had problems with the desktop right after it was installed like a breeze, the disk boot sector died (I expected it would anyway as of about 6 months ago) and funnily enough the mem stick on which the setup worked like a breeze before suddenly wasn’t cooperating. Gotta figure out what was going wrong with UNetbootin creating the ram stick images from ISO, in which, curiously, the boot image required after the disk formatting in Anaconda wasn’t being properly copied or at least activated on the ram stick.

Anyway, I think I have to work on getting the most out of the system, I bet that months from now Fedora will find a way to make me upgrade again, with that lucky number associated with it and all … 🙂