From: Heinz Mauelshagen <mauelsha@ez-darmstadt.telekom.de>
To: "S. Ryan Quick" <ryan@thephaedo.com>
Cc: linux-lvm@msede.com, mge@ts1.ez-darmstadt.telekom.de
Subject: Re: [linux-lvm] Compile Problems w/ 0.7
Date: Sun, 25 Jul 1999 22:26:07 METDST [thread overview]
Message-ID: <199907252028.AA30670@mailgate1b.telekom.de> (raw)
In-Reply-To: <379B5B7C.773DCD8B@thephaedo.com>; from "S. Ryan Quick" at Jul 25, 99 6:46 pm
Hi Ryan and all.
I've asked Ryan by direct mail to send stdout/stderr of his 0.7 LVM
compile run on Debian.
On sunday, 25 september 1999, Ryan said:
>
> I am haviing vicious problems compiling the tools for any of the
> distributions (attempting 0.7 for the most part). The kernel
> patch for 2.2.10 compiled without a hitch, but I cannot get any of the
> tools working at all. I'm running Debian/GNU Linux
> 2.1 --current and (obviously) 2.2.10 kernel. I've attempted compiling
> on several other machines, and am beginning
> to wonder if this is a Debian problem (I have no other boxes to
> attempt).
>
> I was wondering if anyone has had the same problems, or would be able to
> consider posting a glibc binary distribution
> somewhere.
Have send him a bin tarball directly (didn't like the blast to you all ;*) ).
> I am also quite interested in mirroring the site (I have
> 9Mbs dedicated between 2 backbones outside
> of Washington DC, US if anyone is interested.)
>
Thanks, go ahead.
Regards,
Heinz
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Systemmanagement CS/TS T-Nova
Entwicklungszentrum Darmstadt
Heinz Mauelshagen Otto-Roehm-Strasse 71c
Senior Systems Engineer Postfach 10 05 41
64205 Darmstadt
mge@ez-darmstadt.telekom.de Germany
+49 6151 886-425
FAX-386
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~1999-07-25 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-25 18:46 [linux-lvm] Compile Problems w/ 0.7 S. Ryan Quick
1999-07-25 20:26 ` Heinz Mauelshagen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199907252028.AA30670@mailgate1b.telekom.de \
--to=mauelsha@ez-darmstadt.telekom.de \
--cc=linux-lvm@msede.com \
--cc=mge@ts1.ez-darmstadt.telekom.de \
--cc=ryan@thephaedo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).