similar to: Boot into operating system after PXE boot

Hi, I am currently using isolinux (syslinux-6.03) in a clonezilla setup. It boots fine, however I want to have a setup where the default boot selection alternates every boot. * First boot : Default is menu item 0 * Second boot : Default is menu item 1 * Third boot : Default is menu item 0 ... The idea is that when it is booted into clonezilla the clonezilla script checks if the system needs to

> Hello everyone, > > I'm using a windows PXE server and I try to upgrade a existing PXELINUX menu structure with actually with BIOS/Legacy mode to work in UEFI mode too. > > Since I have to use ZENworks tftp on the windows server I have only one TFTP-root directory not 2 different tftp-root directories like on a standard windows > deployment server. ZENworks itself uses for

I've got a user of my g4l project that is having a system that locks with my kernels, but also with hdt? The default versions are using the 5.10 version of syslinux, but build a special setup using 6.02 and it still locks with both the kernels and the hdt? He was able to get gparted i486 live iso to boot on the machine, so not clear what the issue might be. The system is a Fujitsu T734

> > Hello everyone, > > > > I'm using a windows PXE server and I try to upgrade a existing PXELINUX menu structure with actually with BIOS/Legacy mode to work in UEFI mode too. > > > > Since I have to use ZENworks tftp on the windows server I have only one TFTP-root directory not 2 different tftp-root directories like on a standard windows > > deployment

Hi, A couple months ago, I migrated our local school (two servers, 20 desktop clients) from Slackware 14.1 to CentOS 7. The desktop clients are running a customized lightweight desktop based on Xfce: https://blog.microlinux.fr/poste-de-travail-xfce-centos-7/ Home directories are all on the server, and authentication is centralized. Everything works fine so far. With Slackware I had found a

List, from the Dutch "Computable" paper ICT tabloid and daily ICT subscribable mailing-list and so-called verwittigingsbrief/ad hoc news letter, partly translated into English by me ;) Dutch readers only: http://www.computable.nl/nieuws.htm?id=524000 "Manage Windows clients from Linux servers" blahblahblah Zenworks 7, the latest release of Novell's sysadmin suite".

Has anyone used g4l (ghost for linux) with centos 4.2 or 4.X? I just tried it with RAW mode, it made the image on my ftp server, I then tried to restore it, seemed like it went ok, tried to reboot and it starts up looks like it is going to work but then something is not right? I am not even sure how to explain what is not right. can you share your steps. Thanks, Jerry -------------- next

It now been a few days, and wondering if someone might know the status? The following error was encountered while trying to retrieve the URL: http://www.hdt-project.org/wiki/hdt-0.5.0 Connection to 204.232.192.182 failed. The system returned: (110) Connection timed out Hasn't been updated in some time, but I regularly check the site.

Hi, I was wondering whether it is technically possible to go back from eg. DOS or Linux directly to the bootloader (instead of rebooting the hardware). We currently have 2 images (one DOS and one Linux) that need to be started before loading a system. They do things like disable PXE on NICs (using an Intel DOS tool), verify the correctness of the network patchings and validate if the

On Dec 8, 2014 5:24 AM, "Leenders, Peter" <Peter.Leenders at computacenter.com> wrote: > > > Hello everyone, > > > > I'm using a windows PXE server and I try to upgrade a existing PXELINUX menu structure with actually with BIOS/Legacy mode to work in UEFI mode too. > > > > Since I have to use ZENworks tftp on the windows server I have only one

I have a project G4L that has used syslinux for many years. I've upgraded the syslinux from the kernel.org builds over the years up to 6.03 and just copied the newer files, and it has worked. Saw that the new build machine I setup with Fedora 30 had the version 6.04 files. I tried the same process, and then booting the iso comes up with message that it can not load ldlinux.c32, which is

On Mon, Dec 8, 2014 at 10:44 AM, Leenders, Peter <Peter.Leenders at computacenter.com> wrote: > This look promising, if I could separate the config files for the different > boot architectures Bios and UEFI. I have 2 different boot files in 2 > different locations, but after startup they both refer to the > tftproot/pxlinux.cfg/default config file. The DHCP Option 209 may solve

Have been using syslinux for some time for my g4l project, and was just looking at the new 5.00. Normally have just copied the new files, but with version 5.00 it is missing the support files according to ldd, and even putting the missing files in the directory failes to find them. ../../com32/... Script to copy files from new syslinux directory to the projects isolinux directory that is

Wondering what the best process would be to create livecds using the newer version of syslinux. Currently my G4L project has just been upgraded to syslinux 5.10 and works fine with regular 32 and 64 bit systems using the 32bit kernels, but have seen comments about EFI and somethings about 32bit only working with 32bit and 64bit with 64bit? Since I average about 1,000 downloads per week, I

Was seeing it I could get any closer with the efi boot using the 6.0.4, and didn't have any more luck. Did a test with it in bios mode and it works for the regular kernels, but when I tried the hdt.c32 I get the following error? Undef symbol FAIL: parse_url Failed to load COM32 file hdt.c32 Only find urlparce.c in the PXE directory, and no reference to it in any files in the hdt

Hello List, Please read Tom's email below. Has some interesting findings. The affected machine I dealt with also had symantec on it. Since the repair though there hasn't been a problem. The user even re-applied the patches. This is to weird. HTH -------- Original Message -------- Subject: Re: [Samba] Drag and Drop and Crash Date: Mon, 16 Apr 2007 18:12:47 -0700 From: Thomas

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been using the standard isolinux.cfg file for some time with great success. Have it currently display a file at the beginning with a little .lss graphic file, and some basic info then with the image names and info. Also have 4 of the help files linked to the F1 - F4 keys. But I just had a number of emails back

On 16 Aug 2019 at 5:40, Ady Ady via Syslinux wrote: To: "syslinux at zytor.com" <syslinux at zytor.com> Date sent: Fri, 16 Aug 2019 05:40:45 +0000 Subject: Re: [syslinux] Question on upgrading to syslinux 6.04? From: Ady Ady via Syslinux <syslinux at syslinux.org> Send reply to: Ady Ady <ady-sf at hotmail.com> > > I've

Hello Gene, thank you for your answer > > - Is there a standard approach to use different vesamenu.c32 (and other architecture depending ) files in the pxelinux.cfg/default file depending on the boot architecture - especially for BIOS/Legacy and EFI64? > I'd say there's no standard but there are choices. Check out this page I wrote up. >

I've been using various versions of syslinux as the boot loader for the g4l project that I have been the maintainer of since 2004. It was already using syslinux, so I've just updated it over the years, and currently have it use 5.10 version, but have done test builds with the 6.x versions. Recently had request from to users about EFI support, and one suggested that virtualbox has