similar to: Memory usage with memdisk vs initrd a squashfs

On Thu, Mar 13, 2014 at 3:31 PM, Ian Bannerman <ian at internals.io> wrote: > Question, > > Some Linux distributions I support show two approaches for pxe booting them. One uses memdisk to boot an ISO file. The other uses pxelinux to boot kernel and initrd a squashfs file. > I'm unfamiliar with the impact to memory either approach has. Like, does using memdisk permanently

Hi, The method to boot an ISO using memdisk, memdiskfind and phram described in the wiki looks very promising to me. So, I looked into the sources trying to understand, how this works. Up to now, I could not find out how the memory containing the ISO image is preserved from being overwritten by the Linux kernel. Probably I'm missing something, could you please help me? Best regards, Bodo

Hi all, I am new to Syslinux and Memdisk. I setup a PXE boot server that services an image file via memdisk. This works very well. However, I am trying to figure out as to where memdisk the image puts in memory? On the wiki page it says: "MEMDISK simulates a disk by claiming a chunk of high memory for the disk and a (very small - 2K typical) chunk of low (DOS) memory for the driver itself,

Hi, I am trying to boot a server via PXE with following configured for its PXE. LABEL IMP MENU LABEL IMP LINUX memdisk INITRD linuxIso.iso APPEND iso I haven't been able to get this work, probably only because of network speed. PXE server is on RHEL 5.8 and syslinux 5.x While I was booting the server, I ran dstat on PXE server and saw the outgoing network speed was 400-500Bytes. So looks

Hi together, this is the second version of my cross-compilation patch serie. I'm sending it in the hope to get an honest review, and possibly see the patches integrated upstream. Those patches allow to build syslinux using a toolchain different from the host one by explicitely using the host toolchain for the utilities that are required at build-time / on the build machine. I am using the

>From josv on IRC: > Hi! I am on Fedora 25 and installed libguestfs (1.36.2) from the > fedora repo. It seems that the squashfs feature is missing in this > installation (guestfish add-drive /dev/null : run : available squashfs > returns "error: squashfs: group not available"). What would be the > recommended way to have the squashfs feature available? $ guestfish -a

Hello, i've been struggling hard to setup our automated PXE/kickstart system using various local mirrors but it alway hung after partitioning with no further exception. When I encountered squshfs errors on the Console (text based / kickstart installation) I re-synced (rsync) with CERN mirror afterwards with switch.ch mirror and fh-esslingen - But the squashfs image remained corrupt. To prove

I have a dovecot server running under CentOS using maildir format.? Due to the issue with minimum blocksize for files I would like to offer some kind of readonly archive using something like the compressed squashfs? where I would move messages to be archived to a maildir folder and then convert "cur" directory into a squashfs and mount it in place of the original directory so my biggest

Hello listmates, Have any of you used SquashFS? See: http://en.wikipedia.org/wiki/SquashFS We have tried it on small file sets, seems good but if you have experience using it, especially to store/archive lage volumes of files, please share your experience. Thanks. Boris.

Hello all I have squashfs file i want use as root filesystem for diskless machines (PXE boot). I can't figure out how to configure it. I was able to embed this file in initrd (builded by dracut) - but i don't know how to mount it in /sysroot automatically, and what put in 'kernel=' commandline option. Maybe there is another way to achieve this? TIA -- Over And Out MoonWolf

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

Hello, I am new to this list. We are trying to move away from our WDS server with PXElinux mods and are testing using iPXE on a linux box only. We mainly use HP but also have Dells, Panasonic, and Lenovo. On almost a dozen models tested now, everything works great. These were mostly laptops but a Dell Optiplex 360 and 380 booted fine. So far we have just had a problem with the HP 6005 Pro SFF

Op 2013-07-12 om 14:06 schreef syslinux-owner at zytor.com: > Reason: Message body is too big: 1780404 bytes with a limit of 512 KB So previous not on the mailinglist. > Date: Fri, 12 Jul 2013 23:05:05 +0200 (CEST) > From: Michael Szerencsits <szerencsits.michael at gmx.at> > To: syslinux at zytor.com > Subject: efi64 boot fail during download from kernel and initrd

Op 2014-06-21 om 21:19 schreef intrigeri: > Hi, > > Ian Bannerman wrote (21 Jun 2014 15:49:51 GMT) : > > One advantage of the Perl one for me is that I can run it on Windows. > > We at Tails rely on isohybrid.pl for installing on OSX: > https://tails.boum.org/doc/first_steps/installation/manual/mac/ > > Of course, this does not mean that the current syslinux team

Cross-posting to the Syslinux mailing-list. Joakim Schicht wrote: > But part of the question is also about "memdisk raw" vs "memdisk iso". "raw" and "iso" are not mutually exclusive. I think that perhaps you meant "HDD versus El Torito emulation." One can do: LABEL ramwin KERNEL memdisk APPEND raw iso INITRD ramwin.iso > Lets say

Hi there, I've had issue with the integration of syslinux into the buildroot project [0]. After some research, it turned out that we were wrongly using the host toolchain instead of the target toolchain to build syslinux. This gave us bigger issues (for instance) when trying to link syslinux with gnu-efi, that was built using the target toolchain. The first one forces ld to output i386

Add very basic pages for: isohybrid - It's not particularly more useful than --help, but my QA department really wants this to exist. memdiskfind - Explain what it does and its invocation. Signed-off-by: Peter Jones <pjones at redhat.com> --- man/isohybrid.1 | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ man/memdiskfind.1 | 10 +++++++++ 2 files changed, 71

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

Implement the "squash" output format, i.e. a squashfs compressed filesystem. This was implemented in diskimage-builder upstream as commit 9d13084c4183b63587e1f5e4b03395a8df6538f6. --- dib/Makefile.am | 1 + dib/output_format_squashfs.ml | 39 +++++++++++++++++++++++++++++++++++++++ dib/utils.ml | 1 + dib/virt-dib.pod | 6 ++++++ 4 files

On Thursday, 6 April 2017 00:26:26 CEST Richard W.M. Jones wrote: > > >From josv on IRC: > > > Hi! I am on Fedora 25 and installed libguestfs (1.36.2) from the > > fedora repo. It seems that the squashfs feature is missing in this > > installation (guestfish add-drive /dev/null : run : available squashfs > > returns "error: squashfs: group not