On Mon, 11 Mar 2002, David Douthitt wrote:
> On 3/11/02 at 10:42 PM, Manfred Schuler <[EMAIL PROTECTED]>
> wrote:
>
> > Today I received this security announcements.
> > If you think, it is not necessary to forward this message
> > to the list, please tell me.
>
> Should we (as distribution cre
On 3/11/02 at 10:42 PM, Manfred Schuler <[EMAIL PROTECTED]>
wrote:
> Today I received this security announcements.
> If you think, it is not necessary to forward this message
> to the list, please tell me.
Should we (as distribution creators) be sending out our own "Official
Vendor Security Aler
On 3/11/02 at 5:33 PM, Markus A Lien <[EMAIL PROTECTED]> wrote:
> I am trying to find the hdparm utility, I have looked in
> hdsupp.lrp, hdsupp_s.lrp and hdutil.lrp. I tried to run
> hdparm from my RH6.1 system with 2.2.19 kernel and of
> course got a segmentation fault.
Not of course. You did
On 3/10/02 at 8:24 PM, KP Kirchdörfer <[EMAIL PROTECTED]> wrote:
> Am Sonntag, 10. März 2002 03:30 schrieb Mike Noyes:
> export CVSEDITOR=/usr/bin/e3
>
> allows me to use our well known e3-editor for checkin comments.
There's a new version of e3 (2.2); it'll show up in the Oxygen package
area
On 3/11/02 at 1:46 AM, Matt Schalit <[EMAIL PROTECTED]> wrote:
> guitarlynn wrote:
> The section below needs a little more work. The syntax shown
> will overwrite forward.txt.
>
> cp /var/log/messages /mnt/messages.txt
> ip addr show > /mnt/address.txt
> ipchains -nvL > /mnt/filter.txt
> /usr/
On Monday 11 March 2002 03:46, Matt Schalit wrote:
> The section below needs a little more work. The syntax shown
> will overwrite forward.txt.
It is fixed, thanks!!!
> And I request again that you add in
>
> ip route show > /mnt/routes.txt
>
> and remove the netstat -rn, only because ip
I am trying to find the hdparm utility, I have looked in hdsupp.lrp,
hdsupp_s.lrp and hdutil.lrp. I tried to run hdparm from my RH6.1 system
with 2.2.19 kernel and of course got a segmentation fault.
The reason for this is that I am trying to get the hdparm -Y functionality
so I can boot from a
Hi Charles,
> Actually, most development teams try pretty hard to keep a single repository
> for source code...you start running into way too many problems otherwise,
> and this is exactly what CVS is designed to do.
Yes, makes sense (especially from what you and Mike wrote).
> typically this m
Hi Mike,
> >I wonder how the guys who work on larger projects handle that (since I
> >doubt that they don't have local copies of their CVS repositories).
>
> Martin,
> They download tarballs of their repository, and install them on their local
> machine. This is usually only for backup purposes
At 2002-03-11 22:58 +0100, Martin Hejl wrote:
>My goal with this is being able to use CVS locally, while at the same
>time keeping the latest changes "public", without having to go through
>all the double-checking I always need to when releasing a new version
>(if you look at the lrpStat changelog
> You're right, that should work. But in that case, wouldn't I just be
keeping
> two different CVS repositories (rather than two that contain the same
info,
> and are "just" in different locations)? I wonder how the guys who work on
> larger projects handle that (since I doubt that they don't have
At 2002-03-11 22:41 +0100, Martin Hejl wrote:
>I wonder how the guys who work on larger projects handle that (since I
>doubt that they don't have local copies of their CVS repositories).
Martin,
They download tarballs of their repository, and install them on their local
machine. This is usually
Hi Mike,
> >My hope is that something like this will work: I change my CVSROOT and
> >CVS_RSH settings and then simply do a commit from my local working directory
> >into the sourceforge CVS.
>
> Don't do that. It will not work properly.
Hmm, too bad.
> Follow the instructions below,
> and l
Today I received this security announcements.
If you think, it is not necessary to forward this message to the list,
please tell me.
The zlib compression library is being used by many applications to
provide data compression/decompression routines. An error in a
decompression routine
Hi Charles,
> > Now, I already have all my sources in CVS here on my machince, and looking
> > through the CVS docs I have here, I have not found anything on how to keep
> > _two_ repositories "current" without running into problems (maybe it's so
> > simple that they didn't even consider it wort
At 2002-03-11 21:54 +0100, Martin Hejl wrote:
>I was wondering if I should upload the sources to lrpStat into CVS on
>the sourceforge server. Not that I'm worried about the space I'm using,
>but I'd like to provide a "development snapshot" between the releases.
>With the little spare time I have r
> Now, I already have all my sources in CVS here on my machince, and looking
> through the CVS docs I have here, I have not found anything on how to keep
> _two_ repositories "current" without running into problems (maybe it's so
> simple that they didn't even consider it worth mentioning).
This
Hi everybody,
I was wondering if I should upload the sources to lrpStat into CVS on the
sourceforge server. Not that I'm worried about the space I'm using, but I'd
like to provide a "development snapshot" between the releases. With the
little spare time I have right now, it takes me much too long
guitarlynn wrote:
> Alright, the "how do I ask for help" FAQ is posted
> along with updates in all but 1 or 2 of the rest of
> the FAQ's up to Section 7. You can check out the
> new FAQ at:
>
> http://sourceforge.net/docman/display_doc.php?docid=1891&group_id=13751
>
> Thanks to everyone for h
Matt Schalit wrote:
> But -Lvn is better.
^
Darnit. -nvL is better as you said and I couldn't repeat
one sentence later.
___
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
20 matches
Mail list logo
