similar to: Announcing CentOS 7 support for the boot.centos.org ipxe service

Displaying 20 results from an estimated 400 matches similar to: "Announcing CentOS 7 support for the boot.centos.org ipxe service"

2014 Jul 09
0
CentOS-announce Digest, Vol 113, Issue 4
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
2015 Jun 12
3
Last few days in CentOS
Hi, Its been a while since I did the last update post - so this one is going to be a bit longer. Distro ---------- * Updates for CentOS Linux 5/6/7 : All updates from upstream are released into the CentOS mirror network. * Rolling ISO media for CentOS-7 for May 2015 was released : http://lists.centos.org/pipermail/centos-announce/2015-June/021160.html ; this is media rebuilt with the last
2015 Feb 06
0
lost at 'repository' entry installing centos7
On 02/05/2015 01:03 PM, g wrote: > > On 02/02/2015 02:15 PM, Tim wrote: >> Am 1. Februar 2015 21:30:52 MEZ, schrieb g <geleem at bellsouth.net>: >>> >>> greetings. >>> >>> while attempting to install c7, i got lost at 'repository' entry. >>> i canceled, loaded centos.org, looked for help for installing c7, >>> but did
2015 Feb 05
3
lost at 'repository' entry installing centos7
re-sending to list. other attempt got addressed wrong. On 02/02/2015 02:15 PM, Tim wrote: > Am 1. Februar 2015 21:30:52 MEZ, schrieb g <geleem at bellsouth.net>: >> >> greetings. >> >> while attempting to install c7, i got lost at 'repository' entry. >> >> i canceled, loaded centos.org, looked for help for installing c7, >> but did not
2002 Sep 13
4
logging on client side on NT
Hi, I would like to log whatever happens with rsync on client side when it runs with Cygwin on NT4. First, I just did a redirect of the screen output to a log-file: rsync -rtv --delete --modify-window=2 --stats /cygdrive/g/users/bco/test/ bee2bs01::d/test/ >>c:\rsync\log\%FDATE%.log The problem with this method is that it does not redirect whatever Rsync reports as errors; because they
2012 Jun 03
0
still seeking way to recover card after cursor
> Date: Wed, 30 May 2012 13:24:55 +0200 > From: Arvydas Sidorenko > To: "Robert M. Riches Jr." <rm.riches at jacob21819.net> > Cc: nouveau at lists.freedesktop.org > > On Wed, May 30, 2012 at 6:25 AM, Robert M. Riches Jr. > > http://lists.freedesktop.org/mailman/listinfo/nouveau > > I very doubt that rmmod and modprobe will help you in any way since
2013 Oct 09
0
[ipxe-devel] Remove gpxe or replace with ipxe?
> The gPXE in the Syslinux tree is ridiculously old. We could either > replace it with iPXE or just drop it, giving people a recipe for how to > integrate with iPXE themselves. > > What do people think? My vote is replace with iPXE. I've manually replaced gPXE with iPXE for years, works like charm. I suggest updating the Makefile to use undionly.kkkpxe because of the change
2014 Mar 14
0
[ipxe-devel] iPXE boot from both ports (from diferent subnets) not working
On Mar 14, 2014 3:37 AM, "Wissam Shoukair" <wissams at mellanox.com> wrote: > > Hi, > > I'm having a similar problem to the one mentioned earlier by "Laborde Louis", but in this case I'm trying to boot in PXE mode and not iSCSI. > > The problem here is this: > > 1 - DHCP from net0 is successful > > 2 - pxelinux.0 is downloaded from
2014 Mar 14
0
[ipxe-devel] iPXE boot from both ports (from diferent subnets) not working
On Fri, Mar 14, 2014 at 7:09 PM, Wissam Shoukair <wissams at mellanox.com> wrote: > Hi Gene , > > I will try to use 4.07 or 4.05 and update. Did you tried it on the VMWare > workstation on which you saw the issue? > > One more question, shouldn't iPXE reassign the correct parameters to the > "new" image its executing? I mean isn't it the responsibility
2014 Mar 17
0
Fwd: [ipxe-devel] iPXE boot from both ports (from diferent subnets) not working
From: Gene Cumm <gene.cumm at gmail.com> Date: Mon, Mar 17, 2014 at 7:39 PM Subject: Re: [ipxe-devel] iPXE boot from both ports (from diferent subnets) not working To: Wissam Shoukair <wissams at mellanox.com> Cc: "ipxe-devel at lists.ipxe.org" <ipxe-devel at lists.ipxe.org> On Mon, Mar 17, 2014 at 4:43 AM, Wissam Shoukair <wissams at mellanox.com> wrote: >
2013 Oct 18
1
[ipxe-devel] Remove gpxe or replace with ipxe?
On Thu, Oct 10, 2013 at 10:00 AM, Michael Brown <mbrown at fensystems.co.uk> wrote: > On 09/10/13 10:45, Robin Smidsr?d wrote: >> >> On 09.10.2013 02:56, H. Peter Anvin wrote: >>> >>> The gPXE in the Syslinux tree is ridiculously old. We could either >>> replace it with iPXE or just drop it, giving people a recipe for how to >>> integrate
2011 Mar 28
0
[ipxe-devel] Manual IP config does no pass 209:string to chain pxelinux.0
On Friday 25 Mar 2011 21:21:18 Marcus Grando wrote: > >> Script is something like that: > >> > >> #!ipxe > >> ifopen net0 > >> set net0/ip 192.168.0.10 > >> set net0/netmask 255.255.255.0 > >> set net0/gateway 192.168.0.1 > >> set net0/dns 8.8.8.8 > >> set 209:string pxelinux.cfg/default > >> set 210:string
2013 Jul 16
0
pxechn.c32: passing options to iPXE
On Mon, Jul 15, 2013 at 11:57 PM, Alexandre Blanchette <blanalex at gmail.com> wrote: > In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to use > pxechn.c32 to call iPXE (undionly) with option 67 set to call an iPXE > script. > > The relevant portion of my PXELinux config looks like this: > > LABEL MDT > MENU LABEL ^B - MDT 2012 SP1 >
2013 Jul 16
0
pxechn.c32: passing options to iPXE
On Jul 16, 2013 2:01 PM, "Alexandre Blanchette" <blanalex at gmail.com> wrote: > > On Tue, Jul 16, 2013 at 6:26 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > > On Mon, Jul 15, 2013 at 11:57 PM, Alexandre Blanchette > > <blanalex at gmail.com> wrote: > > > In PXELinux 4.06 (the vanilla version, not gpxelinux.0), I'm trying to >
2013 Oct 09
0
Remove gpxe or replace with ipxe?
"H. Peter Anvin" <hpa at zytor.com> writes: > The gPXE in the Syslinux tree is ridiculously old. We could either > replace it with iPXE or just drop it, giving people a recipe for how to > integrate with iPXE themselves. > > What do people think? Do you mean a recipe for creating [gi]pxelinux.0 or for deploying iPXE and using pxelinux on top of that? Is there any
2013 Oct 09
1
Remove gpxe or replace with ipxe?
For me the motivation for gpxelinux.0 was the HTTP support. If this would work reliably in newer versions then I could happily live without a iPXE-based pxelinux. On 9 October 2013 13:36, Ferenc Wagner <wferi at niif.hu> wrote: > "H. Peter Anvin" <hpa at zytor.com> writes: > > > The gPXE in the Syslinux tree is ridiculously old. We could either > >
2013 Oct 22
0
Boot iPXE from syslinux/isolinux
On Tue, Oct 22, 2013 at 5:41 AM, Christian Hesse <list at eworm.de> wrote: > Hello everybody, > > iPXE builds an ISO image by default. (The build system has to be updated for > new paths and to integrate ldlinux.c32, but that's not my problem.) > > With the binary syslinux files from kernel.org booting fails with > latest version 6.02: > > Loading ipxe.krn...
2013 Oct 22
0
Boot iPXE from syslinux/isolinux
Christian Hesse <list at eworm.de> on Tue, 2013/10/22 12:56: > Gene Cumm <gene.cumm at gmail.com> on Tue, 2013/10/22 06:35: > > On Tue, Oct 22, 2013 at 5:41 AM, Christian Hesse <list at eworm.de> wrote: > > > Hello everybody, > > > > > > iPXE builds an ISO image by default. (The build system has to be updated > > > for new paths and to
2013 Nov 11
0
Boot iPXE from syslinux/isolinux
Christian Hesse <list at eworm.de> on Thu, 2013/10/24 10:09: > Christian Hesse <list at eworm.de> on Tue, 2013/10/22 13:14: > > Christian Hesse <list at eworm.de> on Tue, 2013/10/22 12:56: > > > Gene Cumm <gene.cumm at gmail.com> on Tue, 2013/10/22 06:35: > > > > On Tue, Oct 22, 2013 at 5:41 AM, Christian Hesse <list at eworm.de> >
2013 Nov 11
0
Boot iPXE from syslinux/isolinux
"H. Peter Anvin" <hpa at zytor.com> on Mon, 2013/11/11 08:09: > On 11/11/2013 04:09 AM, Christian Hesse wrote: > >> > >> Let be know if you need any more info. > > > > Is anybody working on this? Is there a bug tracker I should report > > this to so it does not get forgotten? Could not find one for > > syslinux. > > > >