Displaying 20 results from an estimated 1100 matches similar to: "debian/ubuntu live CDs"
2008 Jul 16
5
default64 patch?
I stumbled across the following patch and wondered if it wouldn't be a
good idea to have it included.
http://foldingcd.svn.sourceforge.net/viewvc/*checkout*/foldingcd/trunk/folding_cd/patches/syslinux-3.51-64bit.patch?revision=5
It adds a default64 keyword and detection of a 64bit processor. It could
be useful for mixed environments.
The patch is against 3.51, but looks like it would port
2009 Jul 19
3
[PATCH] tftpd.c: write a pid file in standalone mode
The default path is /var/run/tftpd-hpa.pid, which can be overridden
by the newly introduced -P option. On normal termination (SIGTERM
or SIGINT) the pid file is automatically removed.
Moved setting the umask later, right before entering the select loop,
so that it does not affect the permissions of the pid file.
Signed-off-by: Ferenc Wagner <wferi at niif.hu>
---
tftpd/tftpd.c | 38
2008 Jun 07
6
3.70 without "finished" gpxelinux.0?
Hello all,
I'm thinking about wrapping up a 3.70 release, even though gpxelinux.0
is technically not feature-complete. I'd like people's opinion on it.
-hpa
2008 Apr 25
5
Anyone interested in scripts for multiple PXELinux configs in a single TFTP directory
Dear syslinux list members,
I'm a newbie on this list. I hope I don't offend anyone by being
slightly off-topic.
I had the problem of wanting multiple Linux distros (i.c. Debian,
Ubuntu, OpenSuSE, SuSE, RedHat, CentOS, Fedora) installable from a
single PXELinux menu, so I wrote a couple of scripts that do what is
described below.
The question is whether anyone would be interested in
2010 Sep 01
1
syslinux: Please provide -m and -a options on Linux
Hi,
this is a forward from the debian bug tracking system,
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595170:
"syslinux for Windows provides the options -m (write an MBR) and -a (make
partition active). These options make it easy to provide instructions
for Windows users to make a bootable USB drive: just run "syslinux -m
-a" on the drive, then drop some files on the drive
2008 Feb 13
1
FTBFS btrfs-progs 0.12 on IA64
Hi,
since version 0.12, btrfs-progs fails to build from source (FTBFS) on
IA64. I've not looked into the issue yet, but though I'll just let you
know about it already.
The buildlog can be seen on:
http://buildd.debian.org/build.php?arch=ia64&pkg=btrfs-tools&ver=0.12-1
Regards,
Daniel
--
Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:
2010 Jan 03
1
tftp-hpa 5.0 fails to build on mips
Hi,
recently, tftp-hpa has started to fail to build on mips and mipsel with
the following error:
---snip---
[...]
make -C tftpd
[...]
gcc -g -O2 -W -Wall -Wpointer-arith -Wbad-function-cast
-Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations
-Wnested-externs -Winline -Wwrite-strings -Wundef -Wshadow
-Wsign-compare -pipe -fno-strict-aliasing -I/build/buildd/tftp-hpa-5.0
-c
2010 Oct 14
3
XCP: buitin templates (how they works?)
Good day.
I''m pretty curious, how they work with netinst (debian, suse, ubuntu,
centos)...
As I understand, at first start they downloads xen-aware kernel and
netinst initrd from repository (with one user must point with
other-config:install-repository)...
But how they do it? I means, this some kind of script, some kind of
variables...
Really, I''d like to do few more
2010 Jul 05
0
HDT & Debian ?
On 07/05/2010 08:20 AM, Erwan Velu wrote:
> I just saw you get into the mailing list ;)
heh :)
> Does debian on the road to add HDT ?
well, since hdt is included in syslinux, debian has hdt already since a
log time (within the syslinux-common package that ships the com32 modules).
however, more interestingly, hdt needs to be integrated within the
syslinux menu on the installer and live
2010 Jun 05
0
PULL: Properly cast and avoid compiler warnings, fixes build on alpha and ia64.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
please apply the following patch to fix building btfs-progs on alpha and
ia64 from:
git://git.debian-maintainers.org/git/daniel/btrfs-tools.git
- ---snip---
commit 561e811286c52f141cf4944fe219e6b61fab0ac9
Author: Daniel Baumann <daniel@debian.org>
Date: Sat Jun 5 08:53:46 2010 +0200
Properly cast and avoid compiler warnings,
2014 Mar 07
2
Syslinux EFI + TFTPBOOT Support
On 2014?03?07? 18:24, Ady wrote:
> Hi Steven,
>
> Perhaps this could be of some basic sample/help, being based on
> Debian:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720589
>
> where:
> _ if gpxelinux.0 is needed, it should probably be replaced by ipxe.
> _ lpxelinux.0 (from official Syslinux archive) could optionally be
> added.
>
> _ from the
2014 Jun 11
0
Recent (6.02) PXELINUX on Soekris net4501
> * Gene Cumm, 2014-06-10 :
>
> > If 4.05 or 3.86 acted nicely, this would mean a bug.
>
> OK, so, with unpatched official binaries:
>
> 3.86
> ----
>
> pxelinux.0
> Loads fine, assumes terminal width 15, displays menu, but then freezes
> (I suspect it does not process any input from the serial port)
>
> gpxelinux.0
> Displays:
>
2014 Jan 10
0
USB boot problems on Gigabyte GA-M55Plus-S3G
>
> Anyway, in the F12 boot menu there is no clear indication of what thing
> (or things) the BIOS thinks are or not present. (What made you think
> that there would be?)
>
In some systems, in the BIOS F12 boot menu, when I have one internal
SATA drive and one USB flashdrive connected, I could see them *both*
under HDD, while under USB-HDD there is no device listed for the
2014 Jan 11
2
USB boot problems on Gigabyte GA-M55Plus-S3G
In message <BLU0-SMTP145A44932CB6CC2DB4621568BB30 at phx.gbl>,
Ady <ady-sf at hotmail.com> wrote:
>> Is there something specific I should try? /boot/syslinux ?
>>
>
>>From the syslinux boot prompt in UBCD you could try:
>/boot/syslinux/config.c32 /boot/syslinux/syslinux.cfg /boot/syslinux/
>
>(Yes, it is the same basic absolute path, three times, all
2007 Jun 20
0
domU with no fstate lags in "xm list"
Hi all,
Anybody know what it means for a DomU to show up in the "xm list" as follows:
Name ID Mem VCPUs State Time(s)
Domain-0 0 256 2 r----- 43929.3
Clonezilla 16 512 1 ------ 6.2
The domU "Clonezilla" does not have an "r" state
2010 Jul 10
3
booting clonezilla *.iso via PXE fails
Hallo,
I'm just trying to boot a Clonezilla *.iso (live-20100521-lucid) via
PXE;
Label clonezilla
kernel memdisk
append iso raw
initrd iso/clonezilla.iso
The first step is ok - I see the boot menu of the *.iso.
When I choose "Clonezilla live" the system fails with
Isolinux: Disk error 02, AX = 4224, drive E0
when I choose "freedos" it fails with
2016 Oct 07
0
Alternating boot default entry every reboot
Not sure iso/syslinux directly has a way to do this, but I did find a
way to have a system act like you're saying.
I don't want it to automatically alternate, I want to have a command
to run that will change the default. (Remote system.)
=====
#!/bin/bash
sudo bash -c "sed -i '0,/^DEFAULT .*$/{s/^DEFAULT .*/DEFAULT
terra-snapper/}' /boot/syslinux/syslinux.cfg"
sudo
2014 Jan 19
0
USB boot problems on Gigabyte GA-M55Plus-S3G
Hi,
> Hummm... so the world has not entirely done away with the kludgy,
> antiquated and anachronistic old C/H/S addressing scheme just yet,
> eh?
It must actually have been your preparation of the USB stick which
has chosen a FAT filesystem with CHS.
I refer to this statement of yours, of Fri, 17 Jan 2014 13:48:21 -0800:
>> Furthermore, and separately, regardless of the install
2014 Jun 11
3
Recent (6.02) PXELINUX on Soekris net4501
* Gene Cumm, 2014-06-10 :
> If 4.05 or 3.86 acted nicely, this would mean a bug.
OK, so, with unpatched official binaries:
3.86
----
pxelinux.0
Loads fine, assumes terminal width 15, displays menu, but then freezes
(I suspect it does not process any input from the serial port)
gpxelinux.0
Displays:
PXE->EB: !PXE at 9E64:0060, entry point at 9E64:00F6
UNDI code segment
2014 Jan 19
0
USB boot problems on Gigabyte GA-M55Plus-S3G
In message <BLU0-SMTP48EE10402F4B5AE9EC1E078BBB0 at phx.gbl>, Ady wrote:
>After dd'ing my test.img to the USB drive, you would have one FAT32
>partition of about 700MB. So:
Someone in this thread said something about erasing or eliminating
stuff from the USB stick first, so just to be on the safe side, before
I dd'd your test.img file to my test stick (i.e. one of my 2GB