search for: sysl

Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 (with an optional Syslinux menu containing multiple entries). Problem (solved) #1: The default directory location for both syslinux.efi is the same. Solution #1: Rename each syslinux.efi to bootx64.efi and to bootia32.efi. Problem (solved) #2: Each syslinux.efi needs at least its respective ldlinux module. Solutio...

Op 2014-08-01 om 20:35 schreef Ady: > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > (with an optional Syslinux menu containing multiple entries). What I would like to have is the same thing for network boot. So having one topdirectory on the TFTP server that can serve several "architectures". > Problem (solved) #1: The default directory location for both > syslinux.efi is the same. &g...

Hello Ady, On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > (with an optional Syslinux menu containing multiple entries). > > Problem (solved) #1: The default directory location for both > syslinux.efi is the same. > > Solution #1: Rename each syslinux.efi to bootx64.efi and to > bootia32.efi. > > Problem (solved) #2: Each syslinux.efi needs at least...

> Hello Ady, > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > (with an optional Syslinux menu containing multiple entries). > > > > Problem (solved) #1: The default directory location for both > > syslinux.efi is the same. > > > > Solution #1: Rename each syslinux.efi to bootx64.efi and to > > bootia32.efi. > > > > Problem (solve...

...now it crashes later ... > > What crash are you seeing? > >> I don't have the ia64 files which are needed for a complete binary. But >> maybe that's only my special problem. > > You shouldn't need ia64 files to build ia32 and x86-64 versions of > gnu-efi or Syslinux. Just to clarify: On a x86_64 system with gnu-efi 3.0u I checked out tag "syslinux-6.01-pre5" and just run "make". It failed with make[3]: Entering directory `/tmp/sysl/syslinux/efi32/efi' /tmp/sysl/syslinux/mk/efi.mk:27: *** Missing ia32 gnu-efi header files. St...

> I really think we should not take chances; > Syslinux source should include (probably as an optional download tarball) > the gnu-efi used to build the particular Syslinux version. > > apt-get is awesome but after running > LANG=C apt-get source syslinux > on my Ubuntu 14.04 I just got Syslinux 4.05 > The sources of a package...

> Hello Ady, > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > (with an optional Syslinux menu containing multiple entries). > > > > Problem (solved) #1: The default directory location for both > > syslinux.efi is the same. > > > > Solution #1: Rename each syslinux.efi to bootx64.efi and to > > bootia32.efi. > > > > Problem (solve...

...mut Hullen wrote: > Thanks - now it crashes later ... What crash are you seeing? > I don't have the ia64 files which are needed for a complete binary. But > maybe that's only my special problem. You shouldn't need ia64 files to build ia32 and x86-64 versions of gnu-efi or Syslinux. -- Matt Fleming, Intel Open Source Technology Center

I really think we should not take chances; Syslinux source should include (probably as an optional download tarball) the gnu-efi used to build the particular Syslinux version. Pat -------------------------------------------- On Mon, 12/22/14, Ady <ady-sf at hotmail.com> wrote: Subject: Re: [syslinux] check-gnu-efi.sh: print the output...

Hello Ady & list, On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > Hello Ady, > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > (with an optional Syslinux menu containing multiple entries). > > > > > > Problem (solved) #1: The default directory location for both > > > syslinux.efi is the same. > > > > > > Solution #1: Rename each syslinux.efi to bootx64.efi and to > > > bootia32.efi. >...

...; > On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > > Hello Ady, > > > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > > (with an optional Syslinux menu containing multiple entries). > > > > > > > > Problem (solved) #1: The default directory location for both > > > > syslinux.efi is the same. > > > > > > > > Solution #1: Rename each syslinux.efi to bootx64.efi and to > >...

...ot 6 0.0 0.0 0 0 ?? DL Thu07AM 0:01.03 (vnlru) root 7 0.0 0.0 0 0 ?? DL Thu07AM 9:03.81 (syncer) root 28 0.0 0.0 212 0 ?? IWs - 0:00.00 adjkerntz -i root 134 0.0 0.0 952 528 ?? Ss Thu10AM 0:06.17 /usr/sbin/sysl root 138 0.0 0.1 6304 5608 ?? Ss Thu10AM 0:51.81 /usr/sbin/name daemon 140 0.0 0.0 988 436 ?? Ss Thu10AM 0:02.75 /usr/sbin/port root 142 0.0 0.0 572 356 ?? Ss Thu10AM 0:02.76 mountd -r root 144 0.0 0.0 368 0 ?? IWs - 0:00.00...

Hello, Attached is the environment I've been using to test the latest syslinux and nasm, booting ISO, FDD and HDD under qemu. If anyone wants to receive the output of the daily tests, send me a private message. The README: DESCRIPTION: Script for automation of syslinux and nasm tests, using qemu and a special init that just prints "BOOTED" to the console. I...

...able-cups --with-configdir=/etc/samba --with-lockdir=/var/spool/samba --w ith-piddir=/var/run --with-logfilebase=/var/log/samba --with-privatedir=/etc /samba --with-swatdir=/usr/local/share/swat --with-ssl --with-sslinc=/usr/in clude/ssl --with-ssllib=/usr/lib --with-dce-dfs --with-automount --with-sysl og --with-quotas --with-utmp --with-msdfs --with-libsmbclient --with-acl-sup port --with-dfs --with-krb5=/etc/kerberosV --prefix=/usr/local --sysconfdir= /etc The 2 lines that reference the header files are listed below: #include <dce/dce_error.h> #include <dce/sec_login.h>

> It is based on > http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/mkdiskimage.in?id=syslinux-6.03-pre1 Just a thought (FWIW). Perhaps it could be useful to base it on the syslinux4-xx branch: http://git.zytor.com/?p=syslinux/syslinux.git;a=tree;h=refs/heads/sysl inux-4.xx;hb=syslinux-4.xx http://git.zytor.com/?p=syslinux/syslinux.gi...

...test. -d Index: log.c =================================================================== RCS file: /var/cvs/openssh/log.c,v retrieving revision 1.54 diff -u -p -r1.54 log.c --- log.c 10 Jun 2008 13:01:51 -0000 1.54 +++ log.c 2 Jun 2011 03:59:56 -0000 @@ -56,6 +56,8 @@ static LogLevel log_level = SYSLOG_LEVEL static int log_on_stderr = 1; static int log_facility = LOG_AUTH; static char *argv0; +static log_handler_fn *log_handler; +static void *log_handler_ctx; extern char *__progname; @@ -260,6 +262,9 @@ log_init(char *av0, LogLevel level, Sysl exit(1); } + log_handler = NULL; + l...

...ustomer, We are pleased to confirm that you have successfully renewed the following domain that is registered at Gandi: hdt-project.org This domain has been renewed for 1 year(s), and the new expiration date is therefore 2017-05-04 20:20:51 On 8 May 2016 at 15:26, Michael D. Setzer II via Sysl wrote: To: Erwan Velu <erwanaliasr1 at gmail.com>, Pierre-Alexandre Meyer <pierre at mouraf.org> Date sent: Sun, 08 May 2016 15:26:47 +1000 Priority: normal Subject: Re: [syslinux] HDT site down?? From: "Michael D. Setzer II via...

...023 root 19218 0.0 0.0 47624 1244 ? Ss 15:26 0:00 /usr/libexec/libvirt_lxc --name system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19219 0.3 0.0 19276 1532 ? Ss 15:26 0:00 /sbin/init system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19406 0.0 0.0 177444 1332 ? Sl 15:26 0:00 /sbin/rsyslogd -i /var/run/sysl system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19420 0.0 0.0 64120 1144 ? Ss 15:26 0:00 /usr/sbin/sshd system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19427 0.0 0.0 22136 956 ? Ss 15:26 0:00 xinetd -stayalive -pidfile /var system_u:system_r:svirt_lxc_net_t:s0:c...

...023 root 19218 0.0 0.0 47624 1244 ? Ss 15:26 0:00 /usr/libexec/libvirt_lxc --name system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19219 0.3 0.0 19276 1532 ? Ss 15:26 0:00 /sbin/init system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19406 0.0 0.0 177444 1332 ? Sl 15:26 0:00 /sbin/rsyslogd -i /var/run/sysl system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19420 0.0 0.0 64120 1144 ? Ss 15:26 0:00 /usr/sbin/sshd system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19427 0.0 0.0 22136 956 ? Ss 15:26 0:00 xinetd -stayalive -pidfile /var system_u:system_r:svirt_lxc_net_t:s0:c...

...> What crash are you seeing? > > > >> I don't have the ia64 files which are needed for a complete binary. But > >> maybe that's only my special problem. > > > > You shouldn't need ia64 files to build ia32 and x86-64 versions of > > gnu-efi or Syslinux. > > Just to clarify: > > On a x86_64 system with gnu-efi 3.0u I checked out tag > "syslinux-6.01-pre5" and just run "make". It failed with > > make[3]: Entering directory `/tmp/sysl/syslinux/efi32/efi' > /tmp/sysl/syslinux/mk/efi.mk:27: **...