FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor


 
 
LinkBack Thread Tools
 
Old 07-30-2008, 04:35 AM
Chris Bannister
 
Default

On Mon, Jul 28, 2008 at 04:32:54PM -0400, Telemachus wrote:
> On Mon Jul 28 2008 @ 8:48, Brad Rogers wrote:
> > On Mon, 28 Jul 2008 15:33:36 -0400
> > Telemachus <telemachus@ld.net.au> wrote:
> >
> > Hello Telemachus,
> >
> > > that looks for a mail with the same title in your sent folder and
> >
> > That could be risky; If Arvind writes multiple messages in a thread,
> > checking Subject alone is insufficient to be sure the message being
> > deleted is the correct one. That's why I suggested M-ID: which is
> > unique.
>
> You are absolutely right. I was hand-waving rather than giving a proper
> solution. To really do it right, given Arvind's specific requests (keep the
> sent copy, wait for the mail to be received, then clean the corresponding
> copy from the Sent folder) really is more complicated than it seems at
> first. Sorry if I was glib.
>
> I don't believe that Mutt by itself can do what you described. It sounds
> more to me like a multi-part problem:
>
> (1) Have procmail scan for messages that are from Arvind himself & to this
> user list.
> (2) When such a mail is found, execute a script (let's go with Perl).
> (3) The Perl script receives the ID from procmail (maybe as an argument?),
> then it runs through the mails in the Sent folder. If it finds a matching
> ID on a mail, it deletes that item.
>
> I'll be curious to know if anyone has a way to do this just with Mutt, but
> it strikes me that Mutt doesn't have "received-hooks" quite like what this
> would need.

That is why procmail has formail and maildrop has reformail.

--
Chris.
======
"One, with God, is always a majority, but many a martyr has been burned
at the stake while the votes were being counted." -- Thomas B. Reed


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-30-2008, 06:07 AM
M. Piscaer
 
Default

Hi,

I have problems sending emails to this list. I tryed it several times but they dont reach the destination.

Regards,

M. Piscaer
--
Digidiensten

michiel@digidiensten.nl
Tel: +31 77 7501700
Fax: +31 77 7501701


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-30-2008, 06:55 AM
Andrei Popescu
 
Default

On Tue,29.Jul.08, 20:17:52, Celejar wrote:
> On Mon, 28 Jul 2008 17:39:58 +0300
> Andrei Popescu <andreimpopescu@gmail.com> wrote:
>
> ...
>
> > I was somewhat forced to use gmail for smtp because my ISP doesn't allow
> > sending mails with a 'From:' address not on their servers (and I don't
> > want to use that address).
>
> I just posted about this, several minutes ago, on the Debian Exim list:
>
> http://lists.alioth.debian.org/pipermail/pkg-exim4-users/2008-July/001440.html

I can answer the second question: gmail doesn't care what you use in
From and Envelope-From because it will rewrite it to your gmail address.

Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
 
Old 07-30-2008, 07:06 AM
 
Default

Hoi,

> Hi,
>
> I have problems sending emails to this list. I tryed it several times but they dont reach the destination.

Well I got this! So it works! BTW you should put a subject on your mails.


Cheers,
Pavlos



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 07-31-2008, 12:55 PM
"Jon Ciesla"
 
Default

Buildsys issues for EL-5? Tried it twice. This built fine on F-8 koji
and EL-4 plague.

---------------------------- Original Message ----------------------------
Subject: Build Error (Job 39725): drupal-5_9-1_el5 on fedora-5-epel
From: buildsys@fedoraproject.org
Date: Thu, July 31, 2008 7:48 am
To: limb@jcomserv.net
--------------------------------------------------------------------------

Job failed on arch noarch


Build logs may be found at
http://buildsys.fedoraproject.org/logs/fedora-5-epel/39725-drupal-5.9-1.el5/


-------------------------------------------------

DEBUG util.py:250: chcon: /dev/urandom
DEBUG util.py:272: Executing command: ['chcon', '--reference=/dev/tty',
'/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/tty']
DEBUG util.py:250: chcon: /dev/tty
DEBUG util.py:272: Executing command: ['chcon',
'--reference=/dev/console',
'/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/console']
DEBUG util.py:250: chcon: /dev/console
DEBUG util.py:272: Executing command: ['chcon', '--reference=/dev/ptmx',
'/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/ptmx']
DEBUG util.py:250: chcon: /dev/ptmx
DEBUG backend.py:471: mount -n -t proc mock_chroot_proc
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/proc
DEBUG util.py:272: Executing command: mount -n -t proc mock_chroot_proc

/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/proc
DEBUG backend.py:471: mount -n -t sysfs mock_chroot_sysfs
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/sys
DEBUG util.py:272: Executing command: mount -n -t sysfs
mock_chroot_sysfs
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/sys
DEBUG backend.py:471: mount -n --bind
/var/lib/mock/cache/fedora-5-ppc-epel/yum_cache/
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/var/cache/yum
DEBUG util.py:272: Executing command: mount -n --bind
/var/lib/mock/cache/fedora-5-ppc-epel/yum_cache/
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/var/cache/yum
DEBUG backend.py:471: mount -n -t devpts mock_chroot_devpts
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/pts
DEBUG util.py:272: Executing command: mount -n -t devpts
mock_chroot_devpts
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/pts
DEBUG backend.py:490: /usr/bin/yum --installroot
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/
update
DEBUG util.py:272: Executing command: /usr/bin/yum --installroot
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/
update
DEBUG util.py:250:
http://infrastructure.fedoraproject.org/rhel/RHEL5-ppc/Server/repodata/repomd.xml:
[Errno 14] HTTP Error 403: Forbidden
DEBUG util.py:250: Trying other mirror.
DEBUG util.py:250: Error: Cannot retrieve repository metadata
(repomd.xml) for repository: rhel5-install. Please verify its path and try
again
DEBUG backend.py:478: umount -n
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/proc
DEBUG util.py:272: Executing command: umount -n
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/proc
DEBUG backend.py:478: umount -n
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/sys
DEBUG util.py:272: Executing command: umount -n
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/sys
DEBUG backend.py:478: umount -n
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/var/cache/yum
DEBUG util.py:272: Executing command: umount -n
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/var/cache/yum
DEBUG backend.py:478: umount -n
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/pts
DEBUG util.py:272: Executing command: umount -n
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/pts
DEBUG util.py:78: remove tree:
/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86
DEBUG util.py:98: kill orphans


--
novus ordo absurdum

_______________________________________________
epel-devel-list mailing list
epel-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list
 
Old 07-31-2008, 02:56 PM
John Poelstra
 
Default

Reminder: This Weekend


-------- Original Message --------
Subject: bugzilla.redhat.com Web UI, Database, XMLRPC Planned Outage |
August 2nd, 2008 - 9:00 AM EST - 7:00 PM EST

Date: Tue, 29 Jul 2008 00:05:42 -0400
From: Dave Lawrence <dkl@redhat.com>

O U T A G E R E Q U E S T F O R M
=====================================

Severity:
Severity Two (High)

Scheduled Date:
August 2nd, 2008

Scheduled Time:
9:00 AM EST - 7:00 PM EST

Estimated Time Required:
10 hours

Performed By:
Red Hat Engineering Operations

People/Groups Impacted:
Users of bugzilla.redhat.com and any services that rely on
bugzilla.redhat.com


Site/Services Affected:
bugzilla.redhat.com Web UI, Database, XMLRPC

Impact:
bugzilla.redhat.com will be unavailable during the posted
time on August 2nd, 2008.

Description:
On August 2nd, bugzilla.redhat.com will go down for an
update to the latest upstream code base. During this time
the web servers will be reinstalled with the latest OS
updates as well as the latest Bugzilla code. Also the
database servers will undergo a data migration to be made
compatible with the latest Bugzilla code. The web UI,
database, and all XMLRPC services will be unavailable during
the migration. Services that rely on bugzilla.redhat.com may
not function properly during this time so please let your
users know about the outage as well.

Also please take time to point your services/scripts at our
test server https://partner-bugzilla.redhat.com to make sure
that they will still work with the new system once it goes
live. Care has been taken to make the new system backwards
compatible as much as possible with the old XMLRPC API but
still confirm that they work properly. If you encounter any
problems, please contact bugzilla-owner redhat com or file a
bug at
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&version=3.2


Signoff:
kbaker redhat com

_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
 
Old 07-31-2008, 02:56 PM
John Poelstra
 
Default

Reminder: This Weekend


-------- Original Message --------
Subject: bugzilla.redhat.com Web UI, Database, XMLRPC Planned Outage |
August 2nd, 2008 - 9:00 AM EST - 7:00 PM EST

Date: Tue, 29 Jul 2008 00:05:42 -0400
From: Dave Lawrence <dkl@redhat.com>

O U T A G E R E Q U E S T F O R M
=====================================

Severity:
Severity Two (High)

Scheduled Date:
August 2nd, 2008

Scheduled Time:
9:00 AM EST - 7:00 PM EST

Estimated Time Required:
10 hours

Performed By:
Red Hat Engineering Operations

People/Groups Impacted:
Users of bugzilla.redhat.com and any services that rely on
bugzilla.redhat.com


Site/Services Affected:
bugzilla.redhat.com Web UI, Database, XMLRPC

Impact:
bugzilla.redhat.com will be unavailable during the posted
time on August 2nd, 2008.

Description:
On August 2nd, bugzilla.redhat.com will go down for an
update to the latest upstream code base. During this time
the web servers will be reinstalled with the latest OS
updates as well as the latest Bugzilla code. Also the
database servers will undergo a data migration to be made
compatible with the latest Bugzilla code. The web UI,
database, and all XMLRPC services will be unavailable during
the migration. Services that rely on bugzilla.redhat.com may
not function properly during this time so please let your
users know about the outage as well.

Also please take time to point your services/scripts at our
test server https://partner-bugzilla.redhat.com to make sure
that they will still work with the new system once it goes
live. Care has been taken to make the new system backwards
compatible as much as possible with the old XMLRPC API but
still confirm that they work properly. If you encounter any
problems, please contact bugzilla-owner redhat com or file a
bug at
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&version=3.2


Signoff:
kbaker redhat com

_______________________________________________
Fedora-devel-announce mailing list
Fedora-devel-announce@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-announce

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 07-31-2008, 03:35 PM
Mike McGrath
 
Default

This was related to our outage last night. A drive didn't get re-mounted
correctly after the netapp crashed. Please try it again.

-Mike

On Thu, 31 Jul 2008, Jon Ciesla wrote:

> Buildsys issues for EL-5? Tried it twice. This built fine on F-8 koji
> and EL-4 plague.
>
> ---------------------------- Original Message ----------------------------
> Subject: Build Error (Job 39725): drupal-5_9-1_el5 on fedora-5-epel
> From: buildsys@fedoraproject.org
> Date: Thu, July 31, 2008 7:48 am
> To: limb@jcomserv.net
> --------------------------------------------------------------------------
>
> Job failed on arch noarch
>
>
> Build logs may be found at
> http://buildsys.fedoraproject.org/logs/fedora-5-epel/39725-drupal-5.9-1.el5/
>
>
> -------------------------------------------------
>
> DEBUG util.py:250: chcon: /dev/urandom
> DEBUG util.py:272: Executing command: ['chcon', '--reference=/dev/tty',
> '/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/tty']
> DEBUG util.py:250: chcon: /dev/tty
> DEBUG util.py:272: Executing command: ['chcon',
> '--reference=/dev/console',
> '/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/console']
> DEBUG util.py:250: chcon: /dev/console
> DEBUG util.py:272: Executing command: ['chcon', '--reference=/dev/ptmx',
> '/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/ptmx']
> DEBUG util.py:250: chcon: /dev/ptmx
> DEBUG backend.py:471: mount -n -t proc mock_chroot_proc
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/proc
> DEBUG util.py:272: Executing command: mount -n -t proc mock_chroot_proc
>
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/proc
> DEBUG backend.py:471: mount -n -t sysfs mock_chroot_sysfs
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/sys
> DEBUG util.py:272: Executing command: mount -n -t sysfs
> mock_chroot_sysfs
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/sys
> DEBUG backend.py:471: mount -n --bind
> /var/lib/mock/cache/fedora-5-ppc-epel/yum_cache/
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/var/cache/yum
> DEBUG util.py:272: Executing command: mount -n --bind
> /var/lib/mock/cache/fedora-5-ppc-epel/yum_cache/
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/var/cache/yum
> DEBUG backend.py:471: mount -n -t devpts mock_chroot_devpts
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/pts
> DEBUG util.py:272: Executing command: mount -n -t devpts
> mock_chroot_devpts
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/pts
> DEBUG backend.py:490: /usr/bin/yum --installroot
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/
> update
> DEBUG util.py:272: Executing command: /usr/bin/yum --installroot
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/
> update
> DEBUG util.py:250:
> http://infrastructure.fedoraproject.org/rhel/RHEL5-ppc/Server/repodata/repomd.xml:
> [Errno 14] HTTP Error 403: Forbidden
> DEBUG util.py:250: Trying other mirror.
> DEBUG util.py:250: Error: Cannot retrieve repository metadata
> (repomd.xml) for repository: rhel5-install. Please verify its path and try
> again
> DEBUG backend.py:478: umount -n
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/proc
> DEBUG util.py:272: Executing command: umount -n
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/proc
> DEBUG backend.py:478: umount -n
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/sys
> DEBUG util.py:272: Executing command: umount -n
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/sys
> DEBUG backend.py:478: umount -n
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/var/cache/yum
> DEBUG util.py:272: Executing command: umount -n
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/var/cache/yum
> DEBUG backend.py:478: umount -n
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/pts
> DEBUG util.py:272: Executing command: umount -n
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/pts
> DEBUG util.py:78: remove tree:
> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86
> DEBUG util.py:98: kill orphans
>
>
> --
> novus ordo absurdum
>
> _______________________________________________
> epel-devel-list mailing list
> epel-devel-list@redhat.com
> https://www.redhat.com/mailman/listinfo/epel-devel-list
>

_______________________________________________
epel-devel-list mailing list
epel-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list
 
Old 07-31-2008, 04:15 PM
"Jon Ciesla"
 
Default

Ah. Makes sense. Build succeeded. Beauty. Thanks!

> This was related to our outage last night. A drive didn't get re-mounted
> correctly after the netapp crashed. Please try it again.
>
> -Mike
>
> On Thu, 31 Jul 2008, Jon Ciesla wrote:
>
>> Buildsys issues for EL-5? Tried it twice. This built fine on F-8 koji
>> and EL-4 plague.
>>
>> ---------------------------- Original Message
>> ----------------------------
>> Subject: Build Error (Job 39725): drupal-5_9-1_el5 on fedora-5-epel
>> From: buildsys@fedoraproject.org
>> Date: Thu, July 31, 2008 7:48 am
>> To: limb@jcomserv.net
>> --------------------------------------------------------------------------
>>
>> Job failed on arch noarch
>>
>>
>> Build logs may be found at
>> http://buildsys.fedoraproject.org/logs/fedora-5-epel/39725-drupal-5.9-1.el5/
>>
>>
>> -------------------------------------------------
>>
>> DEBUG util.py:250: chcon: /dev/urandom
>> DEBUG util.py:272: Executing command: ['chcon', '--reference=/dev/tty',
>> '/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/tty']
>> DEBUG util.py:250: chcon: /dev/tty
>> DEBUG util.py:272: Executing command: ['chcon',
>> '--reference=/dev/console',
>> '/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/console']
>> DEBUG util.py:250: chcon: /dev/console
>> DEBUG util.py:272: Executing command: ['chcon',
>> '--reference=/dev/ptmx',
>> '/var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/ptmx']
>> DEBUG util.py:250: chcon: /dev/ptmx
>> DEBUG backend.py:471: mount -n -t proc mock_chroot_proc
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/proc
>> DEBUG util.py:272: Executing command: mount -n -t proc
>> mock_chroot_proc
>>
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/proc
>> DEBUG backend.py:471: mount -n -t sysfs mock_chroot_sysfs
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/sys
>> DEBUG util.py:272: Executing command: mount -n -t sysfs
>> mock_chroot_sysfs
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/sys
>> DEBUG backend.py:471: mount -n --bind
>> /var/lib/mock/cache/fedora-5-ppc-epel/yum_cache/
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/var/cache/yum
>> DEBUG util.py:272: Executing command: mount -n --bind
>> /var/lib/mock/cache/fedora-5-ppc-epel/yum_cache/
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/var/cache/yum
>> DEBUG backend.py:471: mount -n -t devpts mock_chroot_devpts
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/pts
>> DEBUG util.py:272: Executing command: mount -n -t devpts
>> mock_chroot_devpts
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/pts
>> DEBUG backend.py:490: /usr/bin/yum --installroot
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/
>> update
>> DEBUG util.py:272: Executing command: /usr/bin/yum --installroot
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/
>> update
>> DEBUG util.py:250:
>> http://infrastructure.fedoraproject.org/rhel/RHEL5-ppc/Server/repodata/repomd.xml:
>> [Errno 14] HTTP Error 403: Forbidden
>> DEBUG util.py:250: Trying other mirror.
>> DEBUG util.py:250: Error: Cannot retrieve repository metadata
>> (repomd.xml) for repository: rhel5-install. Please verify its path and
>> try
>> again
>> DEBUG backend.py:478: umount -n
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/proc
>> DEBUG util.py:272: Executing command: umount -n
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/proc
>> DEBUG backend.py:478: umount -n
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/sys
>> DEBUG util.py:272: Executing command: umount -n
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/sys
>> DEBUG backend.py:478: umount -n
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/var/cache/yum
>> DEBUG util.py:272: Executing command: umount -n
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/var/cache/yum
>> DEBUG backend.py:478: umount -n
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/pts
>> DEBUG util.py:272: Executing command: umount -n
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86/root/dev/pts
>> DEBUG util.py:78: remove tree:
>> /var/lib/mock/fedora-5-ppc-epel-2dfa1018cf9ab40627e34e120cad43f4cbb8be86
>> DEBUG util.py:98: kill orphans
>>
>>
>> --
>> novus ordo absurdum
>>
>> _______________________________________________
>> epel-devel-list mailing list
>> epel-devel-list@redhat.com
>> https://www.redhat.com/mailman/listinfo/epel-devel-list
>>
>


--
novus ordo absurdum

_______________________________________________
epel-devel-list mailing list
epel-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list
 
Old 08-01-2008, 03:09 PM
Ferris McCormick
 
Default

Most interesting. Perhaps of use to you?

-------- Forwarded Message --------
From: dante <dante@virtualblueness.net>
Reply-To: gentoo-hardened@lists.gentoo.org
To: gentoo-hardened@lists.gentoo.org
Subject: [gentoo-hardened] Tin Hat = hardened Gentoo distro in RAM
Date: Fri, 01 Aug 2008 08:24:01 -0400

Hi everyone,

My students and I have started a new gnome-based desktop linux distro
derived from hardened Gentoo. It may be of interest to people on this
list.

Tin Hat is pretty much Gentoo, but it runs purely in RAM. It boots from
CD or pen drive, but is not a liveCD in that it doesn't mount a file
system from the boot device. Rather it copies its squashfs from CD to
tmpfs in RAM. Booting is slow, it requres 4 GB of RAM or more, but it
is lightening fast once up. ("emerge --sync" takes about a minute
between a Tin Hat system offering portage, and one sync-ing from
scratch. Firefox starts in about 1 second.)

Tin Hat was started before the recent coldboot attacks. Within the
limit of such attacks, Tin Hat aims at "zero information loss" if
physical access is obtained to a system which is powered down. We add
Ruusu's loop-aes patch to the kernel so that any hard drives are mounted
using one of the best implimentations of block cipher encryptions we
know of. During power up, Tin Hat uses GRSEC/PaX hardening to hedge
against all the usual attacks. We are now thinking about our own patch
to obfuscate data in RAM to protect against coldboot --- but to be
honest, we think we can only make it harder, not impossible.

Tin Hat is stable. We run 6 systems persistently on clean power and
have typical up times of a couple of months.

We never intended on releasing Tin Hat, but the students love it so much
(the speed!) we thought of announcing it on freshmeat. I thought I'd
post to this list because of it is a successful implementation of
hardened Gentoo.

Home page: http://opensource.dyc.edu/tinhat
Freshmeat: http://freshmeat.net/projects/tinhat

Anthony G. Basile
Chair of Information Technology
D'Youville College
Buffalo NY 14201

(716) 829-8197


Regards,
Ferris

--
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (Devrel, Sparc, Userrel, Trustees)
 

Thread Tools




All times are GMT. The time now is 01:20 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org