Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

samtregar (2699)

samtregar
  (email not shown publicly)
http://sam.tregar.com/

Journal of samtregar (2699)

Monday April 14, 2003
04:41 PM

Linux on the Toshiba Satellite 1130

[ #11652 ]
I just got a new laptop from my generous employers, a Toshiba Satellite 1130. It's fast (2Ghz Celeron) and it has plenty of memory (512MB) and disk space (40GB). Unfortunately, it's somewhat difficult to get Linux running on it. I wrote up a document describing my progress, and you can read it here:

I'm posting this here because Google indexes these journals and I figured it was the fastest way to get it up and searchable. I've submited the link to linux-laptop.net but they haven't updated their page in months. The idea of anyone else having to stumble through the flaming hoops I've already stumbled through is just terrible.

On a Perl-related note, as far as I can tell the Redhat 8 Perl breakage is fixed in Redhat 9. HTML::Template wouldn't install on Redhat 8 but it worked just fine in Redhat 9, even though Redhat 9 still defaults to a UTF-8 locale. Go figure.

-sam

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I got HTML::Template installed by doing telling CPAN to do a "force" install.

    % perl -MCPAN -e shell
    cpan> force install HTML::Template

    Brutal, but effective.

    • Yes, that will work. But be aware that you haven't addressed the real problem and you might very well have to. The combination of RH8's default UTF8 locale with Perl 5.8.0's broken UTF8 locale system is not a safe one. You really should fix it by turning off the UTF8 locale settings in /etc/sysconfig/i18n. Then you won't need to ignore the results of my carefully crafted tests and you won't be subject to random failures deep in the regular expression system.

      -sam

  • ...was probably caused by the RedHat people picking up some of the related fixes from the Perl 5.8.1-to-be.
    • Gah! It'd be nice if RedHat modified perl to actually list the patches that they'd applied when you run "perl -V". It'd make me feel a whole lot more comfortable with it...

      -Dom

      • Did you look? My copy says:
          Locally applied patches:
                MAINT18379

        -sam

        • Really? Mine doesn't. And it's fairly vanilla, too:

          % rpm -q perl
          perl-5.8.0-55
          % rpm -V perl
          SM5....T   /usr/bin/perldoc
          SM5....T   /usr/bin/pod2usage
          SM5....T   /usr/bin/podchecker
          SM5....T   /usr/bin/podselect
          S.5....T   /usr/lib/perl5/5.8.0/ExtUtils/xsubpp
          ..5....T   /usr/lib/perl5/5.8.0/Term/ANSIColor.pm
          S.5....T   /usr/lib/perl5/5.8.0/Term/Cap.pm
          S.5....T   /usr/lib/perl5/5.8.0/Test/Builder.pm
          S.5....T   /usr/lib/perl5/5.

          • I have no idea what rpm -V shows you. I thought we were talking about perl -V:
            $ perl5.8.0 -V

              ...

              Locally applied patches:
                    MAINT18379

            -sam

            • I was saying that my "perl -V" output does not include any mention of what patches have been applied to it. I was then attempting to back it up by showing that my perl install is pretty much vanilla redhat. "rpm -V" checks files against what the rpm database says they should be. The "5" means md5 mismatch, the "T" means timestamp mismatch and so on. It would appear that I have been careless installing CPAN module, which is why the list of altered files is so long. :-(

              Alas, though, still no indication

      • Gah! It'd be nice if RedHat modified perl to actually list the patches that they'd applied when you run "perl -V". It'd make me feel a whole lot more comfortable with it...

        And is anyone surprised why on perl5-porters the first question to answer is "can this be replicated with a perl built from source?" Our source.