similar to: memdisk, memdiskfind and phram.ko

Hi, in syslinux-386, I think I've found a problem in com32/lib/syslinux/load_linux.c that leads to cmdline being truncated unnecessarily when e.g. linux.c32 is used. The patch below fixes the problem for me. But I don't know, whether the patch is safe in all cases. I tried to reproduce the logic found in runkernel.inc, but I might have missed something. So, feel free to tell me

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

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

Dear helpers, I have strange results with levelplot: The following lines of code produce a figure with a strange gray horizontal line. Changing n to 9 the line vanishes almost - it stays in the colorbar. Any ideas? The pixel geometry of the lower half of the figure is wrong? ############################## n<-8 xyz<-expand.grid(x=seq(1,n),y=seq(1,n)) z<-matrix(0,n,n)

Hi, I am using mechanize for a while now. Works great. But at the moment I have a small problem using it. The problematic file is attached. In that PHP-File you will see a formular, but mechanize doesn''t recognize it. Could somebody check this? Thanks, Bodo -- http://www.tvbrowser.org http://www.wannawork.de -------------- next part -------------- An HTML attachment was scrubbed...

After 64 prereleases, 626 commits, 52,742 lines of changes, and tons of work by many, many people, Syslinux 4.00 is now officially released. Syslinux 4.00 is the first of a set of major code restructuring releases. The single biggest new features are btrfs and ext4 support, and support for disks larger than 2 TiB. Huge thanks to: - Intel, for sponsoring mine, Alek Du's and Feng Tang's

Dear r-helpers, we have installation problems: Successful installation of R-0.63 base package on Solaris 2.5.1 with the SunSoft compilers f77, c version 4.2. We habe problems with the installation of further packages e.g. integrate from CRAN. R code works but the shared objects built from fortran code do not find the appropriate libs with functions like __pow_ii or __epx at runtime. We tried

Hi, working with R, version 0.63.0, I was successful to dyn.load fortran90 subroutines on a Solaris 2.6, as long as they are more or less in conformity with f77. It was not possible to work with statements like REAL,DIMENSION(:) :: d or x=SUM(y). REAL,DIMENSION(1:10) :: d is possible. We compiled R with f77. Is it possible with real f90 routines or is is in any conflict with the shared

----- Original Message ----- From: "Bodo Thiesen" <bothie@gmx.de> To: <ext3-users@redhat.com> Sent: Monday, August 25, 2014 8:15 PM Subject: Re: filesystem > Hello Bill. [snip] > You're trying to understand what exactly? From the user point of view, > dir_index just makes directory accesses on very big directories faster. > When creating a new file, or

Hello (and Moin Moin) ;) I have currently a straith Problem ... I have our IMAP-Server migrated from an old cyrus the the current stable Version of dovecot. In the old configuration we organized many mails (e.g. root-Stuff) in Public Folders. They structure had nearly 5 folderlevels. After the complete migration an syncronize we switch complete to the dovecot setup. At this moment we have

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 squirrel away a chunk of memory for the ISO file that the OS will be unable to use? Is using initrd to

Hello Bill again. Two things. First. I read this mailing list, so no need to send answers to me personally in copy. Second. I guessed it already, but now it got really obvious, that you didn't do your homework. Please search for your questions in your favorite search engine first. Yes, I know, that there is not much easy to understand information on ext2 (in all flavours) out there, but

* "Theodore Ts'o" <tytso@mit.edu> hat geschrieben: Hi Theodore. > That being said, it's pretty clear that portions of the inode table > and block group descriptor was badly corrupted. [...] Keith is not the first one with problems of this class and he will probably not be the last one. He later told us, that at first, mounting the file system still worked. And that

* Andreas Dilger <adilger@dilger.ca> hat geschrieben: > You can see in the ext4 superblock the amount of data that has been > written to a filesystem over its lifetime: > > Note that this number isn't wholly accurate, but rather a guideline. Is is more like a completely bogus value at best: # LANG=C df -h / | grep root /dev/root 3.7T 3.6T 73G 99% / # grep [0-9]

* Andreas Dilger <adilger@dilger.ca> hat geschrieben: > The "lifetime writes" value has not been around forever, so if the > filesystem was originally created and populated on an older kernel > (e.g. using ext3) it would not contain a record of those writes. It was created as stable ext4 in the first place. So only if there was a stable ext4 release which didn't

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 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,

On Thu, Oct 16, 2014 at 11:01:35PM +0200, Bodo Thiesen wrote: > > Since it never get's updated unless the file system is unmounted, it can > only be used for a 24 hours test by mounting the file system now, > unmounting it 24 hours from now and then taking the difference. It also gets updated if the file system syncfs(2) or sync(2) system call. But if you crash, any writes since

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

* "Bill Cunningham" <billcun@suddenlink.net> hat geschrieben: > I hope this is the right list. I have created an ext2 filesystem and > removed the dir_index feature. I don't know if this kind of experimentation > is going to help me learn something about filesystems or not. Well what is > dir_index? Then I ran e2fsck -f -v -pD and the /dev file. Now what did I >