Forking the Linux-IL mailing list? (was: Re: Firewall for Linux)

[Omer Zak]

I suppose that there are several Linux-IL subscribers who are NOT
interested in job offers or in advertisements.
(Personally, I am interested in job offers but not in advertisements.)

This is not an issue of opening a separate list for newbie questions (this
does not work).

So, I suggest that Linux-IL be split into three lists:
- Linux-IL, for everything else.
- Linux-IL-jobs, for job offers.  Only those who want to see job offers
  will be subscribed to it.
- Linux-IL-ads, for Linux related advertisements.

By the way, I don't consider the advertisement about firewall for Linux to
be spam, because the sender made the effort to target it.  But if
Linux-IL-ads will be opened and the Linux-IL charter will be modified to
direct advertisers to Linux-IL-ads - then the advertisement would have
been a spam.

On Sat, 20 Nov 1999, Vadim Vygonets wrote:

> Quoth Jan Runyon on Fri, Nov 19, 1999:
> > Hello Linux Users Group:
> 
> I don't really know whether it's spam or not, but I decided to
> approve it.  As I approve job offers.  If you don't want to see
> them, tell me, and I will forward such mail to /dev/null (the
> people in there are dying to read it).
> 
> Vadik.
  --- Omer

   "MS-Word keeps thinking it knows what I'm gonna do next and tries to
   help me.  I've lived with my wife for 27 years and SHE can't do that.
   What makes MS-Word think it can?" Bill Mullins

WARNING:
By sending me unsolicited commercial/political/religious E-mail message/s
(known also as "spam"), you irrevocably agree to pay me US$500.- (plus any
legal expenses incurred by my trying to collect the amount due) per
unsolicited commercial/political/religious E-mail message - for the service
of receiving it.


=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Re: Firewall for Linux

[Vadim Vygonets]

Quoth Jan Runyon on Fri, Nov 19, 1999:
> Hello Linux Users Group:

I don't really know whether it's spam or not, but I decided to
approve it.  As I approve job offers.  If you don't want to see
them, tell me, and I will forward such mail to /dev/null (the
people in there are dying to read it).

Vadik.

-- 
The ill-formed Orange
Fails to satisfy the eye:
Segmentation fault.

=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Firewall for Linux

[Jan Runyon]

Hello Linux Users Group:

In case you haven't heard, the Phoenix Adaptive Firewall is the first
ICSA certified firewall on linux distributions.  It uses adaptive,
state-analysis firewall technology with a java based gui for secure
remote administration.  We have an offer for you.  We will give you a no
cost, full evaluation copy if you will put a protected by Phoenix logo
on your home page for one year.  If you are interested let me know.


Regards,

Jan Runyon  2000 West Henderson Road, Suite 400
Progressive Systems, Inc.   Columbus, Ohio  43220
Sales   Phone:  614/326-4600 ext. 107 
[EMAIL PROTECTED] Fax:  614/326-4601
www.Progressive-Systems.Com Toll Free:  800/558-7827 ext. 107



 


=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Re: creating SRPMs

[Aviram Jenik]

Well, installing only some of the packages makes no sense since they are
libraries needed by the main package and various plugins that depend on
having the main package installed.
Dividing it to 4 packages is a possible solution, but not so elegant. I was
hoping there was a better one...

-
Aviram Jenik

"Addicted to Chaos"

-
Today's quote:
One of my favorite philosophical tenets is that people will agree with you
only if they already agree with you. You do not change people's minds.
 - Frank Zappa, 1979


- Original Message -
From: "Tzafrir Cohen" <[EMAIL PROTECTED]>
To: "Aviram Jenik" <[EMAIL PROTECTED]>
Cc: "linux ILUG" <[EMAIL PROTECTED]>
Sent: Friday, November 19, 1999 9:01 PM
Subject: Re: creating SRPMs


> IMHO this sounds like you should create 4 different packages, which depend
> one one another. For instance: maybe someone would like to install only
> the first two components?
>
> Tzafrir Cohen
> mailto:[EMAIL PROTECTED]
> http://www.technion.ac.il/~tzafrir
>
>
> On Fri, 19 Nov 1999, Aviram Jenik wrote:
>
> >
> > Okay, those instructions are pretty helpful. Now things are getting
> > complicated:
> >
> > The application I want to RPM contains 4 components. Building the
package
> > manually look like:
> >
> > cd component1
> > /configure
> > make
> > make install
> > cd ..
> > cd component2
> > /configure
> > make
> > make install
> > .
> > .
> > .
> >
> > The components are dependant: I can't run make on component2 before
making
> > and installing component1.
> > It seems to me the only way to do this is put everything in the build
> > section of the RPM, and just the final make install (of component4) in
the
> > install section. This seems to break the logic of RPMs, though.
> > Does anyone have any suggestions? Is there another way to do this?
> >
> >
> > -
> > Aviram Jenik
> >
> > "Addicted to Chaos"
> >
> > -
> > Today's quote:
> >
> > If it weren't for electricity we'd all be watching television by
> > candlelight.
> >  - George Gobel
> >
> >
> > - Original Message -
> > From: "Tzafrir Cohen" <[EMAIL PROTECTED]>
> > To: "Aviram Jenik" <[EMAIL PROTECTED]>
> > Cc: "linux ILUG" <[EMAIL PROTECTED]>
> > Sent: Thursday, November 18, 1999 8:50 AM
> > Subject: Re: creating SRPMs
> >
> >
> > > Here's something I got from someone else in this list
> > >
> > > Date: Wed, 11 Aug 1999 12:07:02 +0300
> > > From: Oren Tirosh <[EMAIL PROTECTED]>
> > > Subject: Honey, I've RPMed the kids
> > >
> > >  
> > >
> > > > And one slightly related question:
> > > > Do you know how how to "patch" a rpm package (repackage with very
> > > > similar content and description, and keep the dependencies)?
> > >
> > > The SRPM consists of a .spec file (installed to /usr/src/redhat/SPECS)
> > > and one or more source and patch files (installed
/usr/src/redhat/SOURCES)
> > > To rebuild both the binary and source RPMs use:
> > >
> > > rpm -ba /usr/src/redhat/SPECS/foo.spec
> > >
> > > When building an RPM package it unpacks the source, applies any
patches,
> > > builds everything, installs into a temporary directory, verifies the
spec
> > > file list and only then, after successfully building a binary RPM it
packs
> > > the spec and source files into a source RPM. There is no way to bypass
> > this
> > > when creating a source RPM - this ensures that the source RPM is
indeed
> > > valid and can be used to rebuild the package.  Of course, if the .spec
or
> > > makefile have references to components outside the build environment
which
> > > may not be available on other machines the resulting source RPM will
not
> > > work for them.
> > >
> > > The source tar in the SRPM is the original unmodified source from the
> > > program author. Any changes are done using patches, spec file changes
or
> > > adding extra source files.
> > >
> > > Step 1:
> > > rpm -i foo-1.23.src.rpm
> > >  This installs the spec and sources to /usr/src/redhat/{SPECS|SOURCES}
> > >
> > > Step 2:
> > > rpm -bp /usr/src/redhat/SPECS/foo.spec
> > >  This tells rpm to run only the %prep section of the spec file: unpack
the
> > >  sources to /usr/src/redhat/BUILD/foo-1.23 and apply patches.
> > >
> > >  cd to the build directory, examine the source, make changes, run
make,
> > >  test, etc.  Before changing sources keep a backup (foo.c.orig)
> > >
> > >  You can use the actual commands in the spec file to compile:
> > >rpm -bc --short-circuit
> > >  This tells rpm to run the %build section of the spec file. Short
circuit
> > >  means it will skip the %prep section to avoid overwriting the changes
> > >  you made to the unpacked sources.
> > >
> > >   rpm -bi --short-circuit
> > >  Runs only the %install section of the spec file. Usually it installs
> > >  the package to /var/tmp/foo-root and creates there all the target
> > >  directories (/usr/bin, /usr/man/man1, etc).
> > >
> > >  When everything works ok you can generate

unsubscribe

[eran sharvit]

__
Get Your Private, Free Email at http://www.hotmail.com

=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Re: creating SRPMs

[Tzafrir Cohen]

IMHO this sounds like you should create 4 different packages, which depend
one one another. For instance: maybe someone would like to install only
the first two components?

Tzafrir Cohen
mailto:[EMAIL PROTECTED]
http://www.technion.ac.il/~tzafrir


On Fri, 19 Nov 1999, Aviram Jenik wrote:

> 
> Okay, those instructions are pretty helpful. Now things are getting
> complicated:
> 
> The application I want to RPM contains 4 components. Building the package
> manually look like:
> 
> cd component1
> /configure
> make
> make install
> cd ..
> cd component2
> /configure
> make
> make install
> .
> .
> .
> 
> The components are dependant: I can't run make on component2 before making
> and installing component1.
> It seems to me the only way to do this is put everything in the build
> section of the RPM, and just the final make install (of component4) in the
> install section. This seems to break the logic of RPMs, though.
> Does anyone have any suggestions? Is there another way to do this?
> 
> 
> -
> Aviram Jenik
> 
> "Addicted to Chaos"
> 
> -
> Today's quote:
> 
> If it weren't for electricity we'd all be watching television by
> candlelight.
>  - George Gobel
> 
> 
> - Original Message -
> From: "Tzafrir Cohen" <[EMAIL PROTECTED]>
> To: "Aviram Jenik" <[EMAIL PROTECTED]>
> Cc: "linux ILUG" <[EMAIL PROTECTED]>
> Sent: Thursday, November 18, 1999 8:50 AM
> Subject: Re: creating SRPMs
> 
> 
> > Here's something I got from someone else in this list
> >
> > Date: Wed, 11 Aug 1999 12:07:02 +0300
> > From: Oren Tirosh <[EMAIL PROTECTED]>
> > Subject: Honey, I've RPMed the kids
> >
> >  
> >
> > > And one slightly related question:
> > > Do you know how how to "patch" a rpm package (repackage with very
> > > similar content and description, and keep the dependencies)?
> >
> > The SRPM consists of a .spec file (installed to /usr/src/redhat/SPECS)
> > and one or more source and patch files (installed /usr/src/redhat/SOURCES)
> > To rebuild both the binary and source RPMs use:
> >
> > rpm -ba /usr/src/redhat/SPECS/foo.spec
> >
> > When building an RPM package it unpacks the source, applies any patches,
> > builds everything, installs into a temporary directory, verifies the .spec
> > file list and only then, after successfully building a binary RPM it packs
> > the spec and source files into a source RPM. There is no way to bypass
> this
> > when creating a source RPM - this ensures that the source RPM is indeed
> > valid and can be used to rebuild the package.  Of course, if the .spec or
> > makefile have references to components outside the build environment which
> > may not be available on other machines the resulting source RPM will not
> > work for them.
> >
> > The source tar in the SRPM is the original unmodified source from the
> > program author. Any changes are done using patches, spec file changes or
> > adding extra source files.
> >
> > Step 1:
> > rpm -i foo-1.23.src.rpm
> >  This installs the spec and sources to /usr/src/redhat/{SPECS|SOURCES}
> >
> > Step 2:
> > rpm -bp /usr/src/redhat/SPECS/foo.spec
> >  This tells rpm to run only the %prep section of the spec file: unpack the
> >  sources to /usr/src/redhat/BUILD/foo-1.23 and apply patches.
> >
> >  cd to the build directory, examine the source, make changes, run make,
> >  test, etc.  Before changing sources keep a backup (foo.c.orig)
> >
> >  You can use the actual commands in the spec file to compile:
> >rpm -bc --short-circuit
> >  This tells rpm to run the %build section of the spec file. Short circuit
> >  means it will skip the %prep section to avoid overwriting the changes
> >  you made to the unpacked sources.
> >
> >   rpm -bi --short-circuit
> >  Runs only the %install section of the spec file. Usually it installs
> >  the package to /var/tmp/foo-root and creates there all the target
> >  directories (/usr/bin, /usr/man/man1, etc).
> >
> >  When everything works ok you can generate the patches:
> >  In the BUILD directory type:
> >   diff -u foo-1.23/foo.c.orig foo-1.23/foo.c > ../SOURCES/foo-fixit.patch
> >
> >  Then add the patch file to the list of sources in the spec:
> >Patch7: foo-fixit.patch
> >  And use the %patch macro to apply the patch in the %prep section
> >%patch7 -p1
> >  (or -p0, depending on how many path elements you need to strip)
> >
> >  To test the patches use rpm -bp to rerun the %prep section which will
> >  erase the build directory, unpack the source and apply the new patches.
> >  After the patches apply cleanly you can test the %build and %install
> >  sections or just go all the way:
> >   rpm -ba /usr/src/redhat/specs/foo.spec
> >
> >  If everything is ok it will build a binary and source rpms and put them
> in
> >  /usr/src/redhat/RPMS/i386/foo-1.23-2.i386.rpm
> >  /usr/src/redhat/SRPMS/foo-1.23-2.src.rpm
> >
> >  Remember to update the revision number. The version number is the version
> >  of the original program, the revision is for modif

Re: OFF Topic: Linux educated student from Haifa is needed

[Nir Simionovich \(Rin Solo\)]

Hi Geoff,

On Thu, 18 Nov 1999, Geoffrey S. Mendelson wrote:

> Nir Simionovich \ wrote:
> > 
> >   I need a haifa area student, (meaning someone living in Haifa), that has
> > vast knowladge in Installing and configuring Linux machines (needs
> > knowladge in Sendmail, Apache, WU-FTPD, Squid, etc...).
> 
> > this job is for students only !
> 
> Why?

  The job's nature is of flex hours, and not every day I have something to
do for the student, so it's ideal for a student. As you can see, there are
specific days for the job.

Best regards,
  Nir Simionovich

 . Technionus Dormus Farmus Administratus Regularus .
---
   Taub Computer Center, Technion   Cellphone:054-898834
   The Network Flight Recorder Project  Phone:04-8282741
   E-mail: [EMAIL PROTECTED] Pager:058-474747
   Admin : vipe, heller, tux  (05437)
---
Linux is not an Operating System, It's a way of life - Dare to live it!
---


=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Off Topic: Talanted Linux programmer needed.

[Pasha Glozman]

Optibase Ltd. www.optibase.com   (NASDAQ: OBAS) is
looking for talented Linux programmer for the following projects:

1.  Writing driver for our Real-Time MPEG Decoder card for Linux. 
2.  Porting its 3-ring software to Linux. (SDK).
3.  Porting  SDK/driver software for our Real-Time Encoders boards to
Linux.( In future )

The employment is a at permanent basis but consulting propositions are also
welcomed.

Pasha.

=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Off Topic: Talanted Linux programmer needed.

[pashag]

Optibase Ltd. www.optibase.com (NASDAQ: OBAS) is looking for talented Linux programmer 
for the following projects:

1.  Writing driver for our Real-Time MPEG Decoder card for Linux. 
2.  Porting its 3-ring software to Linux. (SDK).
3.  Porting  SDK/driver software for our Real-Time Encoders boards to Linux.( In 
future )

The employment is a at permanent basis but consulting propositions are also welcomed.

Pasha.


---
Get free personalized email at http://www.iname.com

=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Re: creating SRPMs

[dorit]

>Does anyone have any suggestions? Is there another way to do this?

Exactly.
I am running against exactly the same problems
in my very modest project of patching mailx
(interdependencies between earlier patches
and mine).

Thanks again

Dorit

=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Re: creating SRPMs

[Aviram Jenik]

Okay, those instructions are pretty helpful. Now things are getting
complicated:

The application I want to RPM contains 4 components. Building the package
manually look like:

cd component1
/configure
make
make install
cd ..
cd component2
/configure
make
make install
.
.
.

The components are dependant: I can't run make on component2 before making
and installing component1.
It seems to me the only way to do this is put everything in the build
section of the RPM, and just the final make install (of component4) in the
install section. This seems to break the logic of RPMs, though.
Does anyone have any suggestions? Is there another way to do this?


-
Aviram Jenik

"Addicted to Chaos"

-
Today's quote:

If it weren't for electricity we'd all be watching television by
candlelight.
 - George Gobel


- Original Message -
From: "Tzafrir Cohen" <[EMAIL PROTECTED]>
To: "Aviram Jenik" <[EMAIL PROTECTED]>
Cc: "linux ILUG" <[EMAIL PROTECTED]>
Sent: Thursday, November 18, 1999 8:50 AM
Subject: Re: creating SRPMs


> Here's something I got from someone else in this list
>
> Date: Wed, 11 Aug 1999 12:07:02 +0300
> From: Oren Tirosh <[EMAIL PROTECTED]>
> Subject: Honey, I've RPMed the kids
>
>  
>
> > And one slightly related question:
> > Do you know how how to "patch" a rpm package (repackage with very
> > similar content and description, and keep the dependencies)?
>
> The SRPM consists of a .spec file (installed to /usr/src/redhat/SPECS)
> and one or more source and patch files (installed /usr/src/redhat/SOURCES)
> To rebuild both the binary and source RPMs use:
>
> rpm -ba /usr/src/redhat/SPECS/foo.spec
>
> When building an RPM package it unpacks the source, applies any patches,
> builds everything, installs into a temporary directory, verifies the .spec
> file list and only then, after successfully building a binary RPM it packs
> the spec and source files into a source RPM. There is no way to bypass
this
> when creating a source RPM - this ensures that the source RPM is indeed
> valid and can be used to rebuild the package.  Of course, if the .spec or
> makefile have references to components outside the build environment which
> may not be available on other machines the resulting source RPM will not
> work for them.
>
> The source tar in the SRPM is the original unmodified source from the
> program author. Any changes are done using patches, spec file changes or
> adding extra source files.
>
> Step 1:
> rpm -i foo-1.23.src.rpm
>  This installs the spec and sources to /usr/src/redhat/{SPECS|SOURCES}
>
> Step 2:
> rpm -bp /usr/src/redhat/SPECS/foo.spec
>  This tells rpm to run only the %prep section of the spec file: unpack the
>  sources to /usr/src/redhat/BUILD/foo-1.23 and apply patches.
>
>  cd to the build directory, examine the source, make changes, run make,
>  test, etc.  Before changing sources keep a backup (foo.c.orig)
>
>  You can use the actual commands in the spec file to compile:
>rpm -bc --short-circuit
>  This tells rpm to run the %build section of the spec file. Short circuit
>  means it will skip the %prep section to avoid overwriting the changes
>  you made to the unpacked sources.
>
>   rpm -bi --short-circuit
>  Runs only the %install section of the spec file. Usually it installs
>  the package to /var/tmp/foo-root and creates there all the target
>  directories (/usr/bin, /usr/man/man1, etc).
>
>  When everything works ok you can generate the patches:
>  In the BUILD directory type:
>   diff -u foo-1.23/foo.c.orig foo-1.23/foo.c > ../SOURCES/foo-fixit.patch
>
>  Then add the patch file to the list of sources in the spec:
>Patch7: foo-fixit.patch
>  And use the %patch macro to apply the patch in the %prep section
>%patch7 -p1
>  (or -p0, depending on how many path elements you need to strip)
>
>  To test the patches use rpm -bp to rerun the %prep section which will
>  erase the build directory, unpack the source and apply the new patches.
>  After the patches apply cleanly you can test the %build and %install
>  sections or just go all the way:
>   rpm -ba /usr/src/redhat/specs/foo.spec
>
>  If everything is ok it will build a binary and source rpms and put them
in
>  /usr/src/redhat/RPMS/i386/foo-1.23-2.i386.rpm
>  /usr/src/redhat/SRPMS/foo-1.23-2.src.rpm
>
>  Remember to update the revision number. The version number is the version
>  of the original program, the revision is for modifications to the RPM.
>
> Oren
>
> Tzafrir Cohen
> mailto:[EMAIL PROTECTED]
> http://www.technion.ac.il/~tzafrir
>
>



=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]