From: Michael Schumacher
> environment: new Centos 6 installation out of the box.
> somebody has an idea what causes this error mail to be sent?
> This pops up every three minutes. There is no ascservicemonitor on
> that machine, I cannot find any reference to a file with this name and
> I cannot
first off..if you are using the on bios raid turn it off. Secondly
black drives form WD intentionally put themselves into deep cycle diags
every so often. This makes them impossible to use in hardware and FRAID
setups. I have 4 of them in raid 10 under mdraid and i had to disable
bios raid f
On 2012-02-28 19:04, Markus Falb wrote:
> On 28.2.2012 19:49, Rajagopal Swaminathan wrote:
>> Greetings,
>>
>> On Tue, Feb 28, 2012 at 7:23 PM, Tony Placilla
>> wrote:
>>>
>>> I have an opening for a full-time Systems Administrator.
>>>
>>> Please contact me off list for details
>>
>> Is this app
On Wednesday 29 February 2012 02:11:25 fakessh @ wrote:
> What is the correct procedure to build an rpm with this type of package
> tar.xz
AFAIK the %setup macro should be able to handle the decompression.
If not, just do it yourself within the %prep section
Regards
PS: there's an rpm-list ( rp
On Sunday 26 February 2012 20:39:03 Michael Lampe wrote:
> So I can build, but the resulting RPM cannot be installed -- if not
> forced. (No problems then as everything is there.)
Why don't you add the files needed as dependencies to the spec file? (it's one
of the beautis of the rpm system over
On 02/28/2012 10:49 AM, R - elists wrote:
> what exactly is the planned day and time that centos4 will be moved removed
> from working "yum update" & current mirrored functionality ??
>
> march 1st or a day or two later please?
>
> - rh
>
CentOS 4.9 is currently (and will remain forever) at:
htt
On 23.02.2012 14:25, Lamar Owen wrote:
> On Wednesday, February 22, 2012 09:52:54 AM Volker Poplawski wrote:
>> Hi all,
>>
>> I'm booting Centos6 from a usb 3.0 stick.
>>
>> This works fine as long as the usb-stick is connected to a usb 2.0 port.
>> Once I plug the the usb-stick into a blue usb 3.0
From: Volker Poplawski
> The required xhci_hcd kernel module is not part of the 260 modules in
> the initrd for some reason. Sony Memory-Stick is included, if you happen
> to have one of these...
> I was able to rebuild the initrd plus the xhci_hdc module:
> mkinitrd -v --with=xhci_hdc
> /boot
A few months ago I had an enormous amount of grief trying to understand
why a RAID array in a new server kept getting corrupted and suddenly
changing configuration. After a lot of despair and head scratching it
turned out to be the SATA cables. This was a rack server from Asus with
a SATA back
Le mercredi 29 février 2012 à 10:18 +0300, Mihamina Rakotomandimby a
écrit :
> On 02/29/2012 04:11 AM, fakessh @ wrote:
> > What is the correct procedure to build an rpm with this type of package
> > tar.xz
>
> the standard package rebuilding, I guess.
> just have to change the decompression utili
On Wed, 29 Feb 2012 20:52:09 +0100
fakessh @ wrote:
> any idees
My "idee" would be to de-archive your xz file and create a new tar.gz (or
tar.bz) file using the result, then use that to build the rpm.
unxz gnutls-3.0.9.tar.xz
bzip2 gnutls-3.0.9.tar
Now you have a gnutls-3.0.9.tar.bz2
--
MELVI
Miguel Medalha wrote:
>
> A few months ago I had an enormous amount of grief trying to understand
> why a RAID array in a new server kept getting corrupted and suddenly
> changing configuration. After a lot of despair and head scratching it
> turned out to be the SATA cables. This was a rack server
Marc Deop wrote:
> On Sunday 26 February 2012 20:39:03 Michael Lampe wrote:
>> So I can build, but the resulting RPM cannot be installed -- if not
>> forced. (No problems then as everything is there.)
>
> Why don't you add the files needed as dependencies to the spec file? (it's
> one of the beaut
13 matches
Mail list logo
