search for: remoteinstaller

Will McDonald wrote: > On 01/02/06, Plant, Dean <dean.plant at roke.co.uk> wrote: >> We are thinking of using pxe boot with a windows ris server to start >> off a Centos 4 install. Does anyone know if this is possible? > > I've never done it myself but turned up a few links a few weeks back > which imply it's feasible... > >

Dear All, First posting here... I am trying to integrate a PXELinux boot into my native-mode WDS server. I have found that making WDS boot the PXELinux is easy (see below), it is making PXELinux give control back to WDS that I have not cracked yet. -In your WDS server, copy the contents of your tftpboot folder to the Boot\x86 folder in your RemoteInstall one. -Open the Windows Deployment

Hi, I''m having difficulties getting mongrel running on my Debian Etch machine. It seems to install and is listed with my other gems, but things like... "mongrel_rails start ..." ... are not recognised. Perhaps this is something to do with the file "lib" not being found in the install process: ruby extconf.rb install mongrel --include-dependencies checking for main()

Spike White, Sent: Saturday, December 27, 2014 4:32 AM > > Luke, I have considerable experience with this. We use WDS at work > for PXE (MS-centric shop). I use pxelinux at home. > > I've got WDS working in our test lab w/ UEFI. As you state, it strongly > wishes to do proxyDHCP (port 4011). More on this in a bit. > > It's quite common to segregate the DHCP

Thanks for your email. Yes it does provide some insight into why I could hack a Linux DHCP server into providing enough PXE boot information for PXE 3 clients but PXE 2.1 were happy (ROMs under many circumstances need to use proxy dhcp 4011 - as documented by IBM on the link I shared earlier). It appears only the most latest Dell business systems have EFI 64 support, and the best you can expect

.../mongrel_rails:16:in `load'' from /usr/bin/mongrel_rails:16 ... which indicates it is getting stuck in the block of this search method: def search(gem_pattern, version_requirement=Version::Requirement.new(">= 0")) #FIXME - remove duplication between this and RemoteInstaller.search gem_pattern = /^#{ gem_pattern }$/i if String === gem_pattern version_requirement = Gem::Version::Requirement.create(version_requirement) result = [] @gems.each do |full_spec_name, spec| next unless spec.name =~ gem_pattern result << spec if vers...

Hi, I think this has been discussed previously on the list, so apologies if I''m covering old ground but I''ve been using puppet to manage a few Rails applications which have dependencies on quite a few gems, so it''s getting to be a bit of an onerous task to manage them. It looks like the command line interface to gems doesn''t really support automated

I'm using PXE booting to make operating system installations. There is one problem with it - it won't work when BIOS or NIC doesn't support network booting. Is it possible to put pxelinux somehow on a CD or on a floppy? -- Tomek http://wpkg.org

I have tackled a major bug that affected sdi.c32 especially, but might at least theoretically have affected other formats as well. It *appears* to load the SDI image I managed to stitch together with XP Embedded Studio, but it doesn't actually boot neither on my system nor in simulation; then trying to upgrade it to SP2 caused it to corrupt itself, so I'm not all that keen to trying

Having the same trouble that Mark ( http://www.zytor.com/pipermail/syslinux/2002-March/000244.html) had over a test platform I have here. Having a redhat 7.3 with dhcp V3.0rc12 and atftp (0.6.2) on a local small hub and a W2k Server with RIS installed. If I stop binlsvc on nt server my network boot run ok to pxelinux, but as soon as binlsvc is started, RIS server always respond over my local

> Date: Thu, 25 Dec 2014 07:07:52 +0000 > From: Luke Ledgerd <luke.ledgerd at niteco.se> > To: "syslinux at zytor.com" <syslinux at zytor.com> > Subject: [syslinux] Chain-loading from WDS to PXELinux on a different > tftp server > Message-ID: <17ba7ad419d54b6cab685c2cedc3de95 at NI-MAILEX.niteco.se> > Content-Type: text/plain;