Displaying 20 results from an estimated 210 matches similar to: "Release for CentOS-5.10 i386 and x86_64"
2014 Sep 30
1
Release for CentOS-5.10 i386 and x86_64
We are pleased to announce the immediate availability of CentOS-5.11 for
i386 and x86_64 Architectures.
CentOS-5.11 is based on source code released by Red Hat, Inc. and
includes packages from all variants including Server and Client. All
upstream repositories have been combined into one, to make it easier
for end users to work with.
This is just an announcement email, not the release notes.
2014 Sep 30
1
Release for CentOS-5.10 i386 and x86_64
We are pleased to announce the immediate availability of CentOS-5.11 for
i386 and x86_64 Architectures.
CentOS-5.11 is based on source code released by Red Hat, Inc. and
includes packages from all variants including Server and Client. All
upstream repositories have been combined into one, to make it easier
for end users to work with.
This is just an announcement email, not the release notes.
2011 Sep 14
0
CentOS-announce Digest, Vol 79, Issue 5
Send CentOS-announce mailing list submissions to
centos-announce at centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-request at centos.org
You can reach the person managing the list at
centos-announce-owner at centos.org
When
2006 Apr 19
2
ubuntu 5.10 postrgres gem
Hi,
I''ve installed Ubuntu 5.10, with Ruby 1.8.4
with thoose rep:
deb http://www-devel.orcaware.com/packages/ubuntu/ breezy/
deb-src http://www-devel.orcaware.com/packages/ubuntu/ breezy/
when I give:
sudo gem install postgres
I get:
Attempting local installation of ''postgres''
Local gem file not found: postgres*.gem
Attempting remote installation of
2013 Jun 05
1
Syslinux 5.10 released
On Wed, Jun 5, 2013 at 12:58 AM, Gerardo Exequiel Pozzi
<vmlinuz386 at yahoo.com.ar> wrote:
> On 06/04/2013 06:16 PM, Matt Fleming wrote:
>> Folks,
>>
>> Finally, Syslinux 5.10 has been released. This release includes a merge
>> of the 4.10 development branch, which means that there's a new network
>> stack availble, based on the lwIP embedded TCP/IP
2013 Jun 06
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Wed, Jun 5, 2013 at 8:29 PM, Gerardo Exequiel Pozzi
<vmlinuz386 at yahoo.com.ar> wrote:
> Hello,
>
> First, this setup works fine without any error in syslinux 4.06 as show
> below.
>
> For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2]
> directories (~2MB each) are uploaded ready for test.
>
> As said before, this is tested on qemu-1.5.0 +
2013 Jun 06
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
Am 06.06.2013 07:00, schrieb Gene Cumm:
> iPXE details. My testing was with an Intel PXE OROM in a VMware
> hosted platform with 0 issues.
>
>> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0" 200 26813
>> "" "iPXE/1.0.0+ (09c5)"
This is the iPXE version that comes bundled with qemu as the default
qemu boot rom.
-------------- next
2013 Jun 06
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On 06/06/2013 01:25 AM, Thomas B?chler wrote:
> Am 06.06.2013 07:00, schrieb Gene Cumm:
>> iPXE details. My testing was with an Intel PXE OROM in a VMware
>> hosted platform with 0 issues.
>>
>>> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0"
>>> 200 26813 "" "iPXE/1.0.0+ (09c5)"
>
> This is the iPXE
2013 Jun 06
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
Am 06.06.2013 22:42, schrieb H. Peter Anvin:
> On 06/06/2013 01:25 AM, Thomas B?chler wrote:
>> Am 06.06.2013 07:00, schrieb Gene Cumm:
>>> iPXE details. My testing was with an Intel PXE OROM in a VMware
>>> hosted platform with 0 issues.
>>>
>>>> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0"
>>>> 200 26813
2013 Jun 06
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On 06/06/2013 01:56 PM, Thomas B?chler wrote:
>>
>> With *which version* of Qemu?
>
> As Gerardo posted already, 1.5.0.
>
OK. Sorry, that came across stronger than I meant it to.
-hpa
2013 Jun 06
1
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On 06/06/2013 02:00 AM, Gene Cumm wrote:
> On Wed, Jun 5, 2013 at 8:29 PM, Gerardo Exequiel Pozzi
> <vmlinuz386 at yahoo.com.ar> wrote:
>> Hello,
>>
>> First, this setup works fine without any error in syslinux 4.06 as show
>> below.
>>
>> For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2]
>> directories (~2MB each) are uploaded
2013 Jun 07
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Wed, Jun 5, 2013 at 8:29 PM, Gerardo Exequiel Pozzi
<vmlinuz386 at yahoo.com.ar> wrote:
> [#1]
> https://dl.dropboxusercontent.com/u/88891866/archiso_syslinux_406.tar.xz
> https://dl.dropboxusercontent.com/u/88891866/archiso_syslinux_406.tar.xz.sig
>
> [#2]
> https://dl.dropboxusercontent.com/u/88891866/archiso_syslinux_510.tar.xz
>
2013 Jun 07
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Wed, 05 Jun, at 09:29:58PM, Gerardo Exequiel Pozzi wrote:
> dnsmasq-tftp: file /run/archiso/bootmnt/arch/libcom32.c32 not found
> dnsmasq-tftp: file /run/archiso/bootmnt/arch//libcom32.c32 not found
> dnsmasq-tftp: file /run/archiso/bootmnt/arch/libcom32.c32 not found
> dnsmasq-tftp: file
> /run/archiso/bootmnt/arch//arch//boot/syslinux/libcom32.c32 not found
OK, here's the
2013 Jun 07
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
>
> Right, basically the internal PATH variable that keeps a list of
> directories in which to search for files doesn't play well when it
> encounters TFTP-style paths.
>
> The entire problem stems from the fact that colons (':') are used to
> separate entries in the PATH directive and they're also used in
> TFTP-style paths. While I see that you don't
2013 Jun 08
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Jun 8, 2013 11:48 AM, "H. Peter Anvin" <hpa at zytor.com> wrote:
>
> On 06/07/2013 03:34 PM, Ady wrote:
> >
> > If I may...
> >
> > Most Linux distros are not using 5.xx yet. From the point of view of
> > the final user, there are still few new features in 5.xx in
> > comparison with 4.xx. Before this issue affects more users, and
>
2013 Jun 09
0
Some documentation suggestions as of v.5.10
On Jun 8, 2013 7:32 PM, "Ady" <ady-sf at hotmail.com> wrote:
>
> Hello,
>
> Here are some humble suggestions for 'doc/menu.txt' and
> 'doc/syslinux.txt'. They might be relevant for other documentation
> sources too.
I'm pretty sure Matt Fleming has been considering moving to my AsciiDoc
rewrite which may render these moot.
--Gene
2013 Jun 10
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Sat, 08 Jun, at 11:57:34AM, Gene Cumm wrote:
> To minimize impact and convey the extent of the change, perhaps change to
> ';' immediately and make another release, probably 5.20 and this week.
This chunk of ftp_readdir() caught my eye,
} else if ((p = strchr(buf, ';'))) {
/* VMS/Multinet format */
if (p > buf+4 && !memcmp(p-4, ".DIR",
2013 Jun 10
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On 06/10/2013 06:35 AM, Matt Fleming wrote:
> On Sat, 08 Jun, at 11:57:34AM, Gene Cumm wrote:
>> To minimize impact and convey the extent of the change, perhaps change to
>> ';' immediately and make another release, probably 5.20 and this week.
>
> This chunk of ftp_readdir() caught my eye,
>
> } else if ((p = strchr(buf, ';'))) {
> /*
2013 Jun 10
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Mon, 10 Jun, at 07:24:21AM, H. Peter Anvin wrote:
> VMS pathnames with semicolons are the same as in iso9660 -- version
> numbers that are extremely rarely used. However, since file listings
> display them, they have to be stripped off.
>
> So it is probably OK for the four people in the world that might have a
> VMS server.
Next thing I see is HTTP paths. Problem? We
2013 Jun 10
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On 06/10/2013 07:53 AM, Matt Fleming wrote:
> On Mon, 10 Jun, at 07:24:21AM, H. Peter Anvin wrote:
>> VMS pathnames with semicolons are the same as in iso9660 -- version
>> numbers that are extremely rarely used. However, since file listings
>> display them, they have to be stripped off.
>>
>> So it is probably OK for the four people in the world that might have a