-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, mike ledoux hath spake thusly:
gpg --keyserver keyserver.kjsl.com --send-key your-key-id
This key server now also seems to be rejecting connections...
- --
Derek D. Martin
http://www.pizzashack.org/
GPG Key ID
? Or should I at all? Might
2.5.41 have known IDE issues?
For reporting bugs, see this URL:
http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html
Don't run development kernels on machines that you care about! =8^)
- --
Derek D. Martin
http://www.pizzashack.org/
GPG Key ID: 0x81CFE75D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Paul Iadonisi hath spake thusly:
gpg: BAD signature from Derek D. Martin (for signing software)
[EMAIL PROTECTED]
Is the warning message about the deprecated --honor-http-proxy option
Maybe... Easiest way to find
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Paul Iadonisi hath spake thusly:
gpg: BAD signature from Derek D. Martin (for signing software)
[EMAIL PROTECTED]
Is the warning message about the deprecated --honor-http-proxy
option
Maybe... Easiest way
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Derek D. Martin hath spake thusly:
gpg --keyserver keyserver.kjsl.com --send-key your-key-id
I just did this. You may want to try it again. =8^)
It didn't help me... when I update my own key, I still get an invalid
doing away with it. There is no mechanism provided by
GNOME 2 to change your window manager. Additionally, many, many of
the things which previously WERE configurable, no longer are.
I'm no longer a GNOME user...
- --
Derek D. Martin
http://www.pizzashack.org/
GPG Key ID: 0x81CFE75D
. Corporations are the ones that
make software sales profitable, by and large, so the actual users of
the software suffer.
- --
Derek D. Martin
http://www.pizzashack.org/
GPG Key ID: 0x81CFE75D
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Randy Edwards hath spake thusly:
I'm loathe to use Verisign for anything...
I concur wholeheartedly. Those slimy #*(@%! bastards held one of my
domains hostage (offline) for over a month telling me the only way they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, [EMAIL PROTECTED] hath spake thusly:
ssh pll@system-b -L 8110:pop-server:110
fetchmail --protocol POP3 --port 8110 localhost
Is this supposed to be a single command line, or 2 separate ones?
Two.
I would guess 2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Neal Richardson hath spake thusly:
I have swapped out motherboards using windows me and after several ok
like 10 reboots it did in fact work fine.
I've done this with win98 as well, but with varying success. It
/usually/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Ken Ambrose hath spake thusly:
On Thu, 19 Sep 2002, Michael O'Donnell wrote:
The article mentioned below indicates (to me, anyway) that
it might be harder than you think to detect all sniffers:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Thomas Charron hath spake thusly:
Quoting Derek D. Martin [EMAIL PROTECTED]:
Hmmm. Valid point. I know a fair bit about low-level ethernet
stuff,
so: wouldn't it be possible to set up a MAC:IP table of some sort
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, [EMAIL PROTECTED] hath spake thusly:
On Wed, 18 Sep 2002, at 9:39am, [EMAIL PROTECTED] wrote:
I've always just used the read built-in for this.
Doesn't seem to work with init scripts.
Hmmm. One of the things Red
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For astronomy lovers, some interesting tidbits about an event this
weekend:
Weekend Of The Harvest Moon And The Autumnal Equinox
http://www.miamisci.org:8080/ramgen/stargazer/SG0238.rm
This is from Jack Horkiemer's website (which really could
At some point hitherto, Mark Polhamus hath spake thusly:
Are there any conventions for the use of syslog facility codes LOG_LOCAL0
thru LOG_LOCAL7?
That depends on how you define convention; those facilities are used
as generic syslog facilities, allowing for the ability of the system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Steven W. Orr hath spake thusly:
I posted this to the OO list and didn't get any help except to confirm
that other people's files work as badly for me as my own files do. I
don't know what to think:
I suspect this is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Michael O'Donnell hath spake thusly:
I can hack around this in a number of ways (like
issuing two separate scp commands with the files
temporarily residing on C's disk, or by spawning a
tar on L and one on R and pushing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Mark Komarinski hath spake thusly:
On Mon, Sep 09, 2002 at 12:28:32PM -0400, Derek D. Martin wrote:
A few more questions. I'm getting closer to something that may work.
We did this at MCL. I'm a bit fuzzy about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, [EMAIL PROTECTED] hath spake thusly:
Except that telnet://server isn't a mime type, it's a URL, which is
different. Mime types are used for handling attachements, URLs are
for protocols.
I'm aware of that... the point
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Mark Komarinski hath spake thusly:
Samba and NFS(v2) don't like 2GB file sizes.
http://www.suse.de/~aj/linux_lfs.html
That page is a bit outdated. It talks about RH 6.2 as being current,
and doesn't mention ext3 at all. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, [EMAIL PROTECTED] hath spake thusly:
1. Perl seems to favor supporting a variety of features with obscure,
meaningless, two-character variables that might be clearer with flags
or arguments to functions that make use of it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, [EMAIL PROTECTED] hath spake thusly:
Hmmm, if you don't like $|, as Kevin already pointed out, you can:
Use English;
$OUTPUT_AUTOFLUSH = 1;
which I actually find far more readable and understandable than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Erik Price hath spake thusly:
there is no meaning inherent in $!
Right. Just like there is no meaning inherent in #! but we all know
what it means when it comes at the top of a script.
Yes, but again, it is not that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, [EMAIL PROTECTED] hath spake thusly:
Yet you complain about Perl being hard to learn and use, for the same
reasons, and not just for you, but for everyone?
I absolutely said no such thing.
Let's make this even simpler.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, John Abreau hath spake thusly:
Derek D. Martin [EMAIL PROTECTED] writes:
Feel free to have a look. http://www.pizzashack.org/rssh/
I took a look at it, and found you've hit on one of my pet peeves:
when you untar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, [EMAIL PROTECTED] hath spake thusly:
For example, if I have a RH 6.2 system, I might well upgrade the
sh-utils package to that which shipped with 7.3. Does uname now
report that I'm using 7.3 or 6.2? How does it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, mike ledoux hath spake thusly:
I disagree. The solution is to provide a package specific to each
distribution. Of course, your system admin has to pay attention...
It would need to be named differently on each release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Mark Komarinski hath spake thusly:
On Mon, Aug 19, 2002 at 12:26:12PM -0400, Derek D. Martin wrote:
At some point hitherto, Mark Komarinski hath spake thusly:
Which most security-concious admins still remove or zero
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Anyone have experience getting a laptop with an NVidia GeForce
to suspend to disk? IIRC last time I tried this, it caused problems
that caused the laptop to lock up and not recover. OTOH, I could just
be remembering badly. It's rough getting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Kevin D. Clark hath spake thusly:
BTW, this is actually a fairly good example of
why my immune system always concludes that I'm
in physical danger when perl code is visible...
I would point out that it's just as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, Paul Iadonisi hath spake thusly:
I wouldn't worry about it. I would summarily ignore the 'uname -o'
functionality (if it can even be called that). Someone just pointed out
'lsb_release -d' to me. Using 'lsb_release -a'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, [EMAIL PROTECTED] hath spake thusly:
On Fri, 16 Aug 2002, at 5:21pm, Derek D. Martin wrote:
If you should find this sort of thing useful, you can find it here:
http://www.pizzashack.org/rssh/
Cool. Have not had
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, [EMAIL PROTECTED] hath spake thusly:
Now, last I checked, Stallman wanted to call the entire system GNU/Linux
because so much of the environment is built upon GNU software.
However, in the context of 'uname' would operating
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At some point hitherto, [EMAIL PROTECTED] hath spake thusly:
Did Compaq have 1u or 2u rackmount server?
They have both. The Proliant DL320 is an IDE-based 1u, and the DL360
is a SCSI-based 1u. The DL380 is a really sweet 2u that can hold 6
SCSI
34 matches
Mail list logo
