From shuntim.luk at polyu.edu.hk  Fri Aug  3 22:11:39 2007
From: shuntim.luk at polyu.edu.hk (LUK ShunTim)
Date: Sat, 04 Aug 2007 13:11:39 +0800
Subject: [cAos] Wishlist - please provide lapack-devel
Message-ID: <46B40A8B.2090501@polyu.edu.hk>

Hello,

I need the lapack-devel package but yum cannot find it. Re-building
using the source rpm only gives the lapack and blas binary packages.
Please provide the -devel packages as well.

Regards,
ST
--



From benjamin at py-soft.co.uk  Mon Aug  6 11:55:39 2007
From: benjamin at py-soft.co.uk (Benjamin Donnachie)
Date: Mon, 06 Aug 2007 19:55:39 +0100
Subject: [cAos] ClamAV.
Message-ID: <46B76EAB.9070306@py-soft.co.uk>


Any chance of a updated version of ClamAV?

GnuMP just doesn't seem to want to compile properly on my system at the
moment and it's critical to ClamAV...

I'd be very grateful! :-)

Ben


From benjamin at py-soft.co.uk  Tue Aug  7 02:58:16 2007
From: benjamin at py-soft.co.uk (Benjamin Donnachie)
Date: Tue, 07 Aug 2007 10:58:16 +0100
Subject: [cAos] ClamAV.
In-Reply-To: <46B76EAB.9070306@py-soft.co.uk>
References: <46B76EAB.9070306@py-soft.co.uk>
Message-ID: <46B84238.2010109@py-soft.co.uk>

Benjamin Donnachie wrote:
> GnuMP just doesn't seem to want to compile properly on my system at the
> moment and it's critical to ClamAV...

Ah-ha!  Found gmp on the core repo and now the latest ClamAV is happily
compiling in the background... :)

Ben


From gmkurtzer at gmail.com  Tue Aug  7 06:52:18 2007
From: gmkurtzer at gmail.com (Greg Kurtzer)
Date: Tue, 7 Aug 2007 06:52:18 -0700
Subject: [cAos] ClamAV.
In-Reply-To: <46B84238.2010109@py-soft.co.uk>
References: <46B76EAB.9070306@py-soft.co.uk> <46B84238.2010109@py-soft.co.uk>
Message-ID: <571f1a060708070652i6a7000e6n6e2ec7fe352c472c@mail.gmail.com>

Excellent.

Also check the "testing" repository. I know that Michael has been
updating testing and is brainstorming methods for updating stable and
current.

# yum --enablerepo testing update ClamAV

Thanks,
Greg

On 8/7/07, Benjamin Donnachie <benjamin at py-soft.co.uk> wrote:
> Benjamin Donnachie wrote:
> > GnuMP just doesn't seem to want to compile properly on my system at the
> > moment and it's critical to ClamAV...
>
> Ah-ha!  Found gmp on the core repo and now the latest ClamAV is happily
> compiling in the background... :)
>
> Ben
> _______________________________________________
> cAos mailing list
> cAos at caoslinux.org
> http://lists.caosity.org/mailman/listinfo/caos
>


-- 
Greg Kurtzer
http://www.runlevelzero.net/


From benjamin at py-soft.co.uk  Tue Aug  7 12:26:40 2007
From: benjamin at py-soft.co.uk (Benjamin Donnachie)
Date: Tue, 07 Aug 2007 20:26:40 +0100
Subject: [cAos] ClamAV.
In-Reply-To: <571f1a060708070652i6a7000e6n6e2ec7fe352c472c@mail.gmail.com>
References: <46B76EAB.9070306@py-soft.co.uk> <46B84238.2010109@py-soft.co.uk>
	<571f1a060708070652i6a7000e6n6e2ec7fe352c472c@mail.gmail.com>
Message-ID: <46B8C770.7040206@py-soft.co.uk>

Greg Kurtzer wrote:
> # yum --enablerepo testing update ClamAV

That's my usual source of ClamAV updates but it's still on v0.90.3.  Not
to worry, I've locally compiled v0.91.1 now; if my devel box wasn't
packed away I'd make an rpm available.

Take care,

Ben


From gmkurtzer at gmail.com  Wed Aug  8 10:00:56 2007
From: gmkurtzer at gmail.com (Greg Kurtzer)
Date: Wed, 8 Aug 2007 10:00:56 -0700
Subject: [cAos] Wishlist - please provide lapack-devel
In-Reply-To: <46B40A8B.2090501@polyu.edu.hk>
References: <46B40A8B.2090501@polyu.edu.hk>
Message-ID: <571f1a060708081000w2f2b7dd4g8fbdde4d00616fee@mail.gmail.com>

I just saw a notification that this was imported and built for both
i386 and x86_64 and is now in the testing repository:

# yum --enablerepo testing install lapack* blas*

Thanks,
Greg

On 8/3/07, LUK ShunTim <shuntim.luk at polyu.edu.hk> wrote:
> Hello,
>
> I need the lapack-devel package but yum cannot find it. Re-building
> using the source rpm only gives the lapack and blas binary packages.
> Please provide the -devel packages as well.
>
> Regards,
> ST
> --
>
> _______________________________________________
> cAos mailing list
> cAos at caoslinux.org
> http://lists.caosity.org/mailman/listinfo/caos
>


-- 
Greg Kurtzer
http://www.runlevelzero.net/


From shuntim.luk at polyu.edu.hk  Wed Aug  8 20:29:37 2007
From: shuntim.luk at polyu.edu.hk (LUK ShunTim)
Date: Thu, 09 Aug 2007 11:29:37 +0800
Subject: [cAos] Wishlist - please provide lapack-devel
In-Reply-To: <571f1a060708081000w2f2b7dd4g8fbdde4d00616fee@mail.gmail.com>
References: <46B40A8B.2090501@polyu.edu.hk>
	<571f1a060708081000w2f2b7dd4g8fbdde4d00616fee@mail.gmail.com>
Message-ID: <46BA8A21.8060008@polyu.edu.hk>

Greg Kurtzer wrote:
> I just saw a notification that this was imported and built for both
> i386 and x86_64 and is now in the testing repository:
> 
> # yum --enablerepo testing install lapack* blas*
> 
> Thanks,
> Greg

Thanks Greg,
ST
--


From dmadsen at ikk-nord.de  Mon Aug 13 09:10:26 2007
From: dmadsen at ikk-nord.de (Dethlef Madsen)
Date: Mon, 13 Aug 2007 18:10:26 +0200
Subject: [cAos] A problem with glibc update (NSA-1.0)
Message-ID: <46C08272.1090003@ikk-nord.de>

Hallo,

Fist of all - thank you very much for your nice OS. Very slim and fast.

I installed Caos-NSA-1.0 (x86_64)  a few days ago on a HP 5700 PC  
(82Q963 chipset, needs the pci=nommconf kernel parameter)

Then I found the caos updater and tried to install the glibc update. 
After downloading and repackaging glibc the update did not finished. No 
commandline. ctrl-d .. nothing helps.  And after that strange things 
happened. rpm -qa is not working  service status requests shows a 
segemention fault.

If you need logs or other information feel free to ask.

Btw. It's a dualboot system with Scientific Linux 5 (based on Redhat 
Enterprise Linux 5) on another partition and there are no problems. Just 
for info.

Thanks for reading



From gmkurtzer at gmail.com  Mon Aug 13 09:14:06 2007
From: gmkurtzer at gmail.com (Greg Kurtzer)
Date: Mon, 13 Aug 2007 09:14:06 -0700
Subject: [cAos] A problem with glibc update (NSA-1.0)
In-Reply-To: <46C08272.1090003@ikk-nord.de>
References: <46C08272.1090003@ikk-nord.de>
Message-ID: <571f1a060708130914s2ccd3c85w908eac9f0051df6f@mail.gmail.com>

Thank you for the thanks, I am glad you are liking it! :)

The glibc update is kinda weird. I didn't release one! What is the
glibc package version currently and what was the update to?

Thanks.
Greg

On 8/13/07, Dethlef Madsen <dmadsen at ikk-nord.de> wrote:
> Hallo,
>
> Fist of all - thank you very much for your nice OS. Very slim and fast.
>
> I installed Caos-NSA-1.0 (x86_64)  a few days ago on a HP 5700 PC
> (82Q963 chipset, needs the pci=nommconf kernel parameter)
>
> Then I found the caos updater and tried to install the glibc update.
> After downloading and repackaging glibc the update did not finished. No
> commandline. ctrl-d .. nothing helps.  And after that strange things
> happened. rpm -qa is not working  service status requests shows a
> segemention fault.
>
> If you need logs or other information feel free to ask.
>
> Btw. It's a dualboot system with Scientific Linux 5 (based on Redhat
> Enterprise Linux 5) on another partition and there are no problems. Just
> for info.
>
> Thanks for reading
>
> _______________________________________________
> cAos mailing list
> cAos at caoslinux.org
> http://lists.caosity.org/mailman/listinfo/caos
>


-- 
Greg Kurtzer
http://www.runlevelzero.net/


From dmadsen at ikk-nord.de  Mon Aug 13 09:54:10 2007
From: dmadsen at ikk-nord.de (Dethlef Madsen)
Date: Mon, 13 Aug 2007 18:54:10 +0200
Subject: [cAos] A problem with glibc update (NSA-1.0)
In-Reply-To: <571f1a060708130914s2ccd3c85w908eac9f0051df6f@mail.gmail.com>
References: <46C08272.1090003@ikk-nord.de>
	<571f1a060708130914s2ccd3c85w908eac9f0051df6f@mail.gmail.com>
Message-ID: <46C08CB2.8@ikk-nord.de>

Hallo,

Greg Kurtzer schrieb:
> Thank you for the thanks, I am glad you are liking it! :)
>
> The glibc update is kinda weird. I didn't release one! What is the
> glibc package version currently and what was the update to?
>   
I did a fresh install after the glibc-thing from the 
caos-nsa-0.9c.x86_64.iso (ftp.tu-chemnitz.de mirror) and did no update 
after that ;-)

Except one. (last week) Just forgot  which one  ... I'm sorry.  But I 
can still update ntp and new is postfix.

Here are my infos:

[root at nsa64 ~]# rpm -qa | grep glibc
glibc-2.3.6-11.caos.i686
glibc-kernheaders-2.6.16_3-38.caos.x86_64
glibc-devel-2.3.6-11.caos.i686
glibc-utils-2.3.6-11.caos.x86_64
glibc-2.3.6-11.caos.x86_64
glibc-devel-2.3.6-11.caos.x86_64
[root at nsa64 log]#

And the caos update says:

[root at nsa64 log]# caos update
Updating local Caos repository cache
  _caos.pkgs.gz                                 (5.2 kb 100%) 
|==============>|
  _caos.prov.gz                               (423.7 kb 100%) 
|==============>|
  _caos.reqs.gz                                (12.6 kb 100%) 
|==============>|

Updating local Caos patch level information
  _caos.ptch.gz                                 (0.2 kb 100%) 
|==============>|

The following updates were found:
  ntp-4.2.2p3-6.caos.x86_64
  postfix-2.4.3-8.caos.x86_64
Checking for additional package suggestions:
  glibc-2.3.6-11.caos.x86_64
Do you wish to continue? (yes/no): no
[root at nsa64 log]#

May be I should wait until the official release. Your homepage still 
offers the Caos Beta-3 release :-)

In fact I found NSA-1.0 while I was looking for a new Caos-3 version.

I hope my infomation helps.

Thank you







> Thanks.
> Greg
>
> On 8/13/07, Dethlef Madsen <dmadsen at ikk-nord.de> wrote:
>   
>> Hallo,
>>
>> Fist of all - thank you very much for your nice OS. Very slim and fast.
>>
>> I installed Caos-NSA-1.0 (x86_64)  a few days ago on a HP 5700 PC
>> (82Q963 chipset, needs the pci=nommconf kernel parameter)
>>
>> Then I found the caos updater and tried to install the glibc update.
>> After downloading and repackaging glibc the update did not finished. No
>> commandline. ctrl-d .. nothing helps.  And after that strange things
>> happened. rpm -qa is not working  service status requests shows a
>> segemention fault.
>>
>> If you need logs or other information feel free to ask.
>>
>> Btw. It's a dualboot system with Scientific Linux 5 (based on Redhat
>> Enterprise Linux 5) on another partition and there are no problems. Just
>> for info.
>>
>> Thanks for reading
>>
>> _______________________________________________
>> cAos mailing list
>> cAos at caoslinux.org
>> http://lists.caosity.org/mailman/listinfo/caos
>>
>>     
>
>
>   



From dmadsen at ikk-nord.de  Mon Aug 13 10:57:38 2007
From: dmadsen at ikk-nord.de (Dethlef Madsen)
Date: Mon, 13 Aug 2007 19:57:38 +0200
Subject: [cAos] A problem with glibc update (NSA-1.0)
In-Reply-To: <46C08CB2.8@ikk-nord.de>
References: <46C08272.1090003@ikk-nord.de>	<571f1a060708130914s2ccd3c85w908eac9f0051df6f@mail.gmail.com>
	<46C08CB2.8@ikk-nord.de>
Message-ID: <46C09B92.6050703@ikk-nord.de>

Hallo again,

1 additional information:

> And the caos update says:
>
> [root at nsa64 log]# caos update
> Updating local Caos repository cache
>   _caos.pkgs.gz                                 (5.2 kb 100%) 
> |==============>|
>   _caos.prov.gz                               (423.7 kb 100%) 
> |==============>|
>   _caos.reqs.gz                                (12.6 kb 100%) 
> |==============>|
>
> Updating local Caos patch level information
>   _caos.ptch.gz                                 (0.2 kb 100%) 
> |==============>|
>
> The following updates were found:
>   ntp-4.2.2p3-6.caos.x86_64
>   postfix-2.4.3-8.caos.x86_64
> Checking for additional package suggestions:
>   glibc-2.3.6-11.caos.x86_64
> Do you wish to continue? (yes/no): no
> [root at nsa64 log]#
>   

[root at nsa64 ~]# caos pkglist | grep glibc
glibc-2.3.6-11.caos.i686                                    installed
glibc-devel-2.3.6-11.caos.i686                              installed
glibc-kernheaders-2.6.16_3-38.caos.x86_64                   installed
glibc-utils-2.3.6-11.caos.x86_64                            installed
[root at nsa64 ~]#


The caos installer doen't see glibc-2.3.6-11.caos.x86_64. This explains 
the glibc update suggestion.  Both  'old' and ' new' versions are

the same.


Sorry for spam

Thank you






From gmkurtzer at gmail.com  Mon Aug 13 14:59:50 2007
From: gmkurtzer at gmail.com (Greg Kurtzer)
Date: Mon, 13 Aug 2007 14:59:50 -0700
Subject: [cAos] A problem with glibc update (NSA-1.0)
In-Reply-To: <46C09B92.6050703@ikk-nord.de>
References: <46C08272.1090003@ikk-nord.de>
	<571f1a060708130914s2ccd3c85w908eac9f0051df6f@mail.gmail.com>
	<46C08CB2.8@ikk-nord.de> <46C09B92.6050703@ikk-nord.de>
Message-ID: <571f1a060708131459m667c1b43q56517101362dcc15@mail.gmail.com>

OK, it has been fixed. Thanks for all of the information!

Update caos-utils before updating the rest of the system. For example:

# caos -y update caos-utils
# caos update

There was a minor bug in the multilib support in caos-utils. It saw
the 32 bit glibc, and figured that was satisfactory.

Please confirm that this did indeed fix the problem for you.

Thanks,
Greg

On 8/13/07, Dethlef Madsen <dmadsen at ikk-nord.de> wrote:
> Hallo again,
>
> 1 additional information:
>
> > And the caos update says:
> >
> > [root at nsa64 log]# caos update
> > Updating local Caos repository cache
> >   _caos.pkgs.gz                                 (5.2 kb 100%)
> > |==============>|
> >   _caos.prov.gz                               (423.7 kb 100%)
> > |==============>|
> >   _caos.reqs.gz                                (12.6 kb 100%)
> > |==============>|
> >
> > Updating local Caos patch level information
> >   _caos.ptch.gz                                 (0.2 kb 100%)
> > |==============>|
> >
> > The following updates were found:
> >   ntp-4.2.2p3-6.caos.x86_64
> >   postfix-2.4.3-8.caos.x86_64
> > Checking for additional package suggestions:
> >   glibc-2.3.6-11.caos.x86_64
> > Do you wish to continue? (yes/no): no
> > [root at nsa64 log]#
> >
>
> [root at nsa64 ~]# caos pkglist | grep glibc
> glibc-2.3.6-11.caos.i686                                    installed
> glibc-devel-2.3.6-11.caos.i686                              installed
> glibc-kernheaders-2.6.16_3-38.caos.x86_64                   installed
> glibc-utils-2.3.6-11.caos.x86_64                            installed
> [root at nsa64 ~]#
>
>
> The caos installer doen't see glibc-2.3.6-11.caos.x86_64. This explains
> the glibc update suggestion.  Both  'old' and ' new' versions are
>
> the same.
>
>
> Sorry for spam
>
> Thank you
>
>
>
>
> _______________________________________________
> cAos mailing list
> cAos at caoslinux.org
> http://lists.caosity.org/mailman/listinfo/caos
>


-- 
Greg Kurtzer
http://www.runlevelzero.net/


From mej at caoslinux.org  Mon Aug 13 18:07:58 2007
From: mej at caoslinux.org (Michael Jennings)
Date: Mon, 13 Aug 2007 21:07:58 -0400
Subject: [cAos] Idea
Message-ID: <20070814010758.GG31962@kainx.org>

So I had this sudden thought...

I'm constantly debating whether or not is it Wise and Proper for
packages which install daemons (postfix, openssh, samba, etc.) to
1. activate and/or 2. (re)start the service in question.  Partially
due to the unattended nature of RPM installs, these are not the kinds
of questions one can ask the sysadmin.  To date, most distributions
have made Universal Policy Decisions in this regard to behave one way
or the other.  I don't like that idea for the same reason I don't want
my distro vendor forking rpm or the kernel.  :-)

My idea is as follows:

1.  Create a "policy file" in /etc/sysconfig/pkgpolicy containing
shell variable/value pairs such as STARTSVC=0 to define policies
regarding package installation such as whether or not daemons should
be (re)started on install/upgrade.

2.  Provide a command such as "pkgpolicy" which could be invoked from
%post/%preun scriptlets to check this policy before doing things like
"chkconfig foo on" or "service foo restart".

3.  Invoke this command as a conditional macro to seamlessly work on
other distros that lack the command:
%post
if [ $1 -eq 1 ]; then
    %{?pkgpolicy} chkconfig foo on
    %{?pkgpolicy} service foo restart
fi

Any thoughts?

Michael

-- 
Michael Jennings (a.k.a. KainX)  http://www.kainx.org/  <mej at kainx.org>
Linux Server/Cluster Admin, LBL.gov       Author, Eterm (www.eterm.org)
-----------------------------------------------------------------------
 "Because I want you to understand what my music means to me...and
  what it means for me to be able to share it with someone."
       -- Captain Jean-Luc Picard (Patrick Stewart), ST:TNG, "Lessons"


From gmkurtzer at gmail.com  Mon Aug 13 20:15:30 2007
From: gmkurtzer at gmail.com (Greg Kurtzer)
Date: Mon, 13 Aug 2007 20:15:30 -0700
Subject: [cAos] Idea
In-Reply-To: <20070814010758.GG31962@kainx.org>
References: <20070814010758.GG31962@kainx.org>
Message-ID: <571f1a060708132015w51ee52ces4fee40f1f27f34c8@mail.gmail.com>

On 8/13/07, Michael Jennings <mej at caoslinux.org> wrote:
> So I had this sudden thought...

Whoa, cool!

>
> I'm constantly debating whether or not is it Wise and Proper for
> packages which install daemons (postfix, openssh, samba, etc.) to
> 1. activate and/or 2. (re)start the service in question.  Partially
> due to the unattended nature of RPM installs, these are not the kinds
> of questions one can ask the sysadmin.  To date, most distributions
> have made Universal Policy Decisions in this regard to behave one way
> or the other.  I don't like that idea for the same reason I don't want
> my distro vendor forking rpm or the kernel.  :-)

I second that motion. Premature NPTL were bad enough!

>
> My idea is as follows:
>
> 1.  Create a "policy file" in /etc/sysconfig/pkgpolicy containing
> shell variable/value pairs such as STARTSVC=0 to define policies
> regarding package installation such as whether or not daemons should
> be (re)started on install/upgrade.
>
> 2.  Provide a command such as "pkgpolicy" which could be invoked from
> %post/%preun scriptlets to check this policy before doing things like
> "chkconfig foo on" or "service foo restart".
>
> 3.  Invoke this command as a conditional macro to seamlessly work on
> other distros that lack the command:
> %post
> if [ $1 -eq 1 ]; then
>     %{?pkgpolicy} chkconfig foo on
>     %{?pkgpolicy} service foo restart
> fi
>
> Any thoughts?

I like the idea, and I think you just touched on something important
as well. Restarting a daemon on a package update should be treated
differently then starting a service when a package is installed.

The script/program pkgpolicy can just look at the arguments to see
which configuration option applies.

I guess the other idea would be just to slightly modify the
/sbin/service script and maybe provide a check to see if it was called
from RPM (either by command line option or PPID) and then behave
appropriately.

Good idea!

Greg

-- 
Greg Kurtzer
http://www.runlevelzero.net/


From dmadsen at ikk-nord.de  Mon Aug 13 21:03:57 2007
From: dmadsen at ikk-nord.de (Dethlef Madsen)
Date: Tue, 14 Aug 2007 06:03:57 +0200
Subject: [cAos] A problem with glibc update (NSA-1.0)
In-Reply-To: <571f1a060708131459m667c1b43q56517101362dcc15@mail.gmail.com>
References: <46C08272.1090003@ikk-nord.de>	<571f1a060708130914s2ccd3c85w908eac9f0051df6f@mail.gmail.com>	<46C08CB2.8@ikk-nord.de>
	<46C09B92.6050703@ikk-nord.de>
	<571f1a060708131459m667c1b43q56517101362dcc15@mail.gmail.com>
Message-ID: <46C129AD.9090201@ikk-nord.de>

Good morning,

Greg Kurtzer schrieb:
> OK, it has been fixed. Thanks for all of the information!
Always happy to serve :-)


> Update caos-utils before updating the rest of the system. For example:
>
> # caos -y update caos-utils
> # caos update
>   

[root at nsa64 ~]# caos update
Updating local Caos repository cache
  _caos.pkgs.gz                                 (5.2 kb 100%) 
|==============>|
  _caos.prov.gz                               (423.8 kb 100%) 
|==============>|
  _caos.reqs.gz                                (12.6 kb 100%) 
|==============>|

Updating local Caos patch level information
  _caos.ptch.gz                                 (0.2 kb 100%) 
|==============>|

The following updates were found:
  cports-tree-0.113-1.caos.noarch
  ntp-4.2.2p3-6.caos.x86_64
  postfix-2.4.3-8.caos.x86_64
Checking for additional package suggestions:
No additional packages required
Do you wish to continue? (yes/no): yes
Using mirror: http://mirror.caoslinux.org/Caos-NSA-1.0
  cports-tree-0.113-1.caos.noarch.rpm          (17.9 kb 100%) 
|==============>|
  ntp-4.2.2p3-6.caos.x86_64.rpm              (1806.6 kb 100%) 
|==============>|
  postfix-2.4.3-8.caos.x86_64.rpm           (19943.1 kb 100%) 
|==============>|
Vorbereiten...              ########################################### 
[100%]
Erneut packen...
   1:cports-tree            ########################################### 
[ 33%]
   2:ntp                    ########################################### 
[ 67%]
   3:postfix                ########################################### 
[100%]
Aktualisiere...
   1:postfix                ########################################### 
[ 33%]
   2:cports-tree            ########################################### 
[ 67%]
   3:ntp                    ########################################### 
[100%]
System is at patch level: 6
[root at nsa64 ~]#


Looks good.  No glibc suggestion now and the update  works correct now.

Thank you and keep on the good work




From gmkurtzer at gmail.com  Mon Aug 13 21:10:57 2007
From: gmkurtzer at gmail.com (Greg Kurtzer)
Date: Mon, 13 Aug 2007 21:10:57 -0700
Subject: [cAos] A problem with glibc update (NSA-1.0)
In-Reply-To: <46C129AD.9090201@ikk-nord.de>
References: <46C08272.1090003@ikk-nord.de>
	<571f1a060708130914s2ccd3c85w908eac9f0051df6f@mail.gmail.com>
	<46C08CB2.8@ikk-nord.de> <46C09B92.6050703@ikk-nord.de>
	<571f1a060708131459m667c1b43q56517101362dcc15@mail.gmail.com>
	<46C129AD.9090201@ikk-nord.de>
Message-ID: <571f1a060708132110k31912b7apf992a54a52ab579e@mail.gmail.com>

Glad to hear everything is working now.

Maybe you can help me with the German translation for the caos-utils
when I get caught up!  ;-)

Thanks,
Greg

On 8/13/07, Dethlef Madsen <dmadsen at ikk-nord.de> wrote:
> Good morning,
>
> Greg Kurtzer schrieb:
> > OK, it has been fixed. Thanks for all of the information!
> Always happy to serve :-)
>
>
> > Update caos-utils before updating the rest of the system. For example:
> >
> > # caos -y update caos-utils
> > # caos update
> >
>
> [root at nsa64 ~]# caos update
> Updating local Caos repository cache
>   _caos.pkgs.gz                                 (5.2 kb 100%)
> |==============>|
>   _caos.prov.gz                               (423.8 kb 100%)
> |==============>|
>   _caos.reqs.gz                                (12.6 kb 100%)
> |==============>|
>
> Updating local Caos patch level information
>   _caos.ptch.gz                                 (0.2 kb 100%)
> |==============>|
>
> The following updates were found:
>   cports-tree-0.113-1.caos.noarch
>   ntp-4.2.2p3-6.caos.x86_64
>   postfix-2.4.3-8.caos.x86_64
> Checking for additional package suggestions:
> No additional packages required
> Do you wish to continue? (yes/no): yes
> Using mirror: http://mirror.caoslinux.org/Caos-NSA-1.0
>   cports-tree-0.113-1.caos.noarch.rpm          (17.9 kb 100%)
> |==============>|
>   ntp-4.2.2p3-6.caos.x86_64.rpm              (1806.6 kb 100%)
> |==============>|
>   postfix-2.4.3-8.caos.x86_64.rpm           (19943.1 kb 100%)
> |==============>|
> Vorbereiten...              ###########################################
> [100%]
> Erneut packen...
>    1:cports-tree            ###########################################
> [ 33%]
>    2:ntp                    ###########################################
> [ 67%]
>    3:postfix                ###########################################
> [100%]
> Aktualisiere...
>    1:postfix                ###########################################
> [ 33%]
>    2:cports-tree            ###########################################
> [ 67%]
>    3:ntp                    ###########################################
> [100%]
> System is at patch level: 6
> [root at nsa64 ~]#
>
>
> Looks good.  No glibc suggestion now and the update  works correct now.
>
> Thank you and keep on the good work
>
>
> _______________________________________________
> cAos mailing list
> cAos at caoslinux.org
> http://lists.caosity.org/mailman/listinfo/caos
>


-- 
Greg Kurtzer
http://www.runlevelzero.net/


From dmadsen at ikk-nord.de  Tue Aug 14 00:34:42 2007
From: dmadsen at ikk-nord.de (Dethlef Madsen)
Date: Tue, 14 Aug 2007 09:34:42 +0200
Subject: [cAos] A problem with glibc update (NSA-1.0)
In-Reply-To: <571f1a060708132110k31912b7apf992a54a52ab579e@mail.gmail.com>
References: <46C08272.1090003@ikk-nord.de>	<571f1a060708130914s2ccd3c85w908eac9f0051df6f@mail.gmail.com>	<46C08CB2.8@ikk-nord.de>
	<46C09B92.6050703@ikk-nord.de>	<571f1a060708131459m667c1b43q56517101362dcc15@mail.gmail.com>	<46C129AD.9090201@ikk-nord.de>
	<571f1a060708132110k31912b7apf992a54a52ab579e@mail.gmail.com>
Message-ID: <46C15B12.1000404@ikk-nord.de>

Hallo,

> Maybe you can help me with the German translation for the caos-utils
> when I get caught up!  ;-)
>   

Sure. I'll do my very best. :-)

Just pm me where I get the files to translate (no src-rpm yet available) 
or what I have to do.

Thank you






From martyn at theendofhistether.org.uk  Tue Aug 14 08:33:55 2007
From: martyn at theendofhistether.org.uk (Martyn)
Date: Tue, 14 Aug 2007 16:33:55 +0100
Subject: [cAos] Idea
In-Reply-To: <20070814010758.GG31962@kainx.org>
References: <20070814010758.GG31962@kainx.org>
Message-ID: <46C1CB63.4050900@theendofhistether.org.uk>

Michael Jennings wrote:
> So I had this sudden thought...
>   
<snip good thought lol>
> 3.  Invoke this command as a conditional macro to seamlessly work on
> other distros that lack the command:
> %post
> if [ $1 -eq 1 ]; then
>     %{?pkgpolicy} chkconfig foo on
>     %{?pkgpolicy} service foo restart
> fi
>   
Here's something though - suppose you have a service (e.g. samba) that 
you have installed but only start when you want to.  In that case you 
certainly wouldn't want a chkconfig on in upgrade and you would probably 
not want a restart.  Some services have condrestart, which from it's 
name might be right, but I've never used it.

So, really, my concern would be suddenly enabling services for users who 
don't want them on if they happen to upgrade that service as part of a 
once-a-month update or as a dependancy that they don't notice.
> Any thoughts?
>
> Michael
>   
Other than that, looks like a good idea to me.
--
Martyn (Joran)


From mej at caoslinux.org  Thu Aug 23 12:14:56 2007
From: mej at caoslinux.org (Michael Jennings)
Date: Thu, 23 Aug 2007 15:14:56 -0400
Subject: [cAos] Idea
In-Reply-To: <46C1CB63.4050900@theendofhistether.org.uk>
	<571f1a060708132015w51ee52ces4fee40f1f27f34c8@mail.gmail.com>
References: <20070814010758.GG31962@kainx.org>
	<46C1CB63.4050900@theendofhistether.org.uk>
	<20070814010758.GG31962@kainx.org>
	<571f1a060708132015w51ee52ces4fee40f1f27f34c8@mail.gmail.com>
Message-ID: <20070823191456.GT12020@kainx.org>

On Monday, 13 August 2007, at 20:15:30 (-0700),
Greg Kurtzer wrote:

> I like the idea, and I think you just touched on something important
> as well. Restarting a daemon on a package update should be treated
> differently then starting a service when a package is installed.

True, but that's a different point.  That should already be handled in
%post, and if that were not done properly, this change wouldn't help.

> The script/program pkgpolicy can just look at the arguments to see
> which configuration option applies.

The only thing pkgpolicy would really do is look at the policy
configuration and the arguments given, and either run them or not
based on the policy.

> I guess the other idea would be just to slightly modify the
> /sbin/service script and maybe provide a check to see if it was
> called from RPM (either by command line option or PPID) and then
> behave appropriately.

What is it you're trying to alter about how /sbin/service behaves?




On Tuesday, 14 August 2007, at 16:33:55 (+0100),
Martyn wrote:

> > %post
> > if [ $1 -eq 1 ]; then
> >     %{?pkgpolicy} chkconfig foo on
> >     %{?pkgpolicy} service foo restart
> > fi
>
> Here's something though - suppose you have a service (e.g. samba)
> that you have installed but only start when you want to.  In that
> case you certainly wouldn't want a chkconfig on in upgrade and you
> would probably not want a restart.  Some services have condrestart,
> which from it's name might be right, but I've never used it.
> 
> So, really, my concern would be suddenly enabling services for users
> who don't want them on if they happen to upgrade that service as
> part of a once-a-month update or as a dependancy that they don't
> notice.

That's the whole point of being able to specify policy.  "Restart iff
running" ("iff" == "if and only if") is a policy one could choose and
which pkgpolicy would enforce by inhibiting "service foo restart" if
foo was not running at the time.  Other example policies would include
"activate on install" or "restart on upgrade."

HTH,
Michael

-- 
Michael Jennings (a.k.a. KainX)  http://www.kainx.org/  <mej at kainx.org>
Linux Server/Cluster Admin, LBL.gov       Author, Eterm (www.eterm.org)
-----------------------------------------------------------------------
 "Learn to enjoy your own company.  You are the one person you can
  count on living with for the rest of your life."     -- Ann Richards