similar to: bug in syslinux-1.71 w. large Linux-kernel

Hi all, I have 2 questions: 1)How do I calculate the mean on an imported txt file? I've imported the file below and that's what it looks like imported. How do I then calcuate the mean, median, or mode on the column LeafArea using the desktop R package? Any help would be greatly appreciated!! Thanks, Nat LeafType Leaflets LeafArea ShapeRatio LeafWeight LeafThickness 1 1

Hi Folks! I used the code below previously with no problems, but now I get: DTB3<-read.table("C:\\Program Files\\R\\R-2.7.1\\DTB3.csv",header=TRUE,sep=",") > tail(DTB3) DATE VALUE 14233 2008-07-23 1.56 14234 2008-07-24 1.62 14235 2008-07-25 1.71 14236 2008-07-28 1.70 14237 2008-07-29 1.69 14238 2008-07-30 1.67 >

Hi! We've been trying to use pxelinux to boot the Intel D815EGEW board (a sub ATX board). I've discovered what appears to be a bug in pxelinux. pxelinux versions up to 1.67 work fine, but pxelinux 1.70 and 1.71 don't. When it fails it shows this on the screen Intel Base-Code, PXE-2.1 (build 083) [loading kernel etc] Loading ready. Failed to free base memory, sorry...

ISO pulled from http://mirror.rackspace.com/CentOS/6.6/isos/i386/CentOS-6.6-i386-minimal.iso # df -h /var/distros/CentOS-6.6-i386 Filesystem Size Used Avail Use% Mounted on /var/ISO/CentOS-6.6-i386-minimal.iso 339M 339M 0 100% /var/distros/CentOS-6.6-i386 # find /var/distros/CentOS-6.6-i386 -name initr\* /var/distros/CentOS-6.6-i386/isolinux/initrd.img #

I am having difficulty understanding how I would constrain a data set by filtering out 'records' based on certain criteria. Using SQL I could query using 'select * from my.data where LithClass in ('sand', 'clay')' or some such. Using subset, there seem to be ghosts left behind (that is, all of the LithClass *.Labels* remain after subset) > dput(tcc)

Trying to use "minimal" ISOs The 64-bit CEL 7.0 and 6.6 look ok so far. but when I try to set up the CEL 6.6 i386, but I get the following - The initrd could not be found at the specified location: /var/distros/CentOS-6.6-i386/images/pxeboot/initrd.img It does have the initrd.img file in .../isolinux, but for some reason, not in .../images/pxeboot On Tue, Feb 17, 2015 at

I posted this to the group last year, but the problem was not fixed so I will give it another try. I use 3Com's PXE server to deploy the Fedora Core boot disk to my clients for an ftp install. I also have ghost boot disks, bios update disks, and a video bios repair disk all using the 3Com PXE server. The problem is when I try to boot a Linux kernel. With all versions of syslinux since 1.72

An update to the problem I reported earlier - A kind list reader, Michael K Ter Louw, suggested I try syslinux v1.67, and viola!, my problem went away completely. So something between 1.67 and 1.71 got broke with respect to isolinux. Hmm... Another kind list reader, Seth Kurtzberg, was kind enough to make and effort to send an updated initrd; although it didn't solve the problem, it was

I am a new user of R so please bear with me. I have reviewed some R books, FAQs and such but the volume of material is great. I am in the process of porting my current SAS and SVS Script code to Lotus Approach, R and WordPerfect. My question is, can you help me determine the best R method to implement the Hoaglin Outlier Method? It is used in the Appendix A and B of the fo llowing link.

When I upgrade a major revision (3.4.x -> 3.5.x ), I always get a listing from "testparm -v" before and after the upgrade to make sure that a parameter (that I didn't specify in the config) didn't change it's default setting. ---------------------------------------------- Tony Hoover, Network Administrator KSU - Salina, College of Technology and Aviation (785) 826-2660

On 2/17/2015 12:31 PM, Eero Volotinen wrote: > 2015-02-17 22:26 GMT+02:00 Eckert, Doug<doug.eckert at dowjones.com>: > >> >We have a DHCP/PXE server in a build environment, which is separate from >> >our Spacewalk v1.5 server. We direct builds to Satellite or Spacewalk based >> >as needed. It contains initrd & vmlinuz files for each version/arch we

Okay, if you have a system that works with 1.67 but not with 1.71, please send me the following details: a) Which module (SYSLINUX, PXELINUX, ISOLINUX) you're using; b) Which BIOS; c) What does your E820 memory information looks like (the Linux kernel will print this during early boot.) This information is vital for me to track down the bug in question. -hpa

I'm building a custom bootdisk that I would like to boot linux or boot memtest86 (www.memtest86.com). And I'm running into some difficulties with recent versions of syslinux. All I'm doing is making a new label in syslinux.cfg called memtest and giving it kernel memtest.bin. This has worked on and off for several recent versions of memtest. It worked in 1.67, broke in 1.70(loads

Hi Ian, can we push multiboot v2 support for Xen/ARM still into 4.3? It looks like it can coexists with zImage in the same binary - the multiboot structure can be put just behind the zImage header and the code can determine how it has been started: zImage bootloaders clears r0, multiboot one''s would set r0 to the MB magic. I will sketch a patch tomorrow, just wondering if we can have

I have released SYSLINUX 1.71 after fixing the total "brown-paper-bag" class bug in 1.70. My best guess is that I checked in the wrong verson of some code. -hpa SYSLINUX 1.70 doesn't introduce any new features, but contains a major rewrite of some of the internals. It also includes some bug fixes. SYSLINUX 1.71 is a bug fix to 1.70. Changes in 1.71: * Fix a

I''ve addressed all (I think/hope) of the review comments. The main change is to expose the guest virtual platform (e.g. memory layout and interrupt usage etc) to the toolstack via the public interface. This is then used during FDT generation. I have just codified the current defacto standard layout, it''s probably not the best layout but any change can be a separate patch/series.

Hi Xen Developers, I had tested new XenARM for Arndale board that is updated in Anthony''s tree from 2 days ago. I expected that will be working. But, I can not boot Dom0 Kernel. I used kernel and XenARM both are from Xen Wiki(http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale). It (seems) stopped after "(XEN) Freed 212kB init memory" message. When I

This patch exports to userspace the boot loader ID which has been exported by (b)zImage boot loaders since boot protocol version 2. Tested on i386 and x86-64; as far as I know those are the only architectures which use zImage/bzImage format. -hpa Signed-Off-By: H. Peter Anvin <hpa at zytor.com>

Upstream commit 4370eec05a88 "arm64: Expand arm64 image header" ended up changing the zImage magic (which was actually the initial branch instructio encoding!). The new header has a proper magic number at a fixed location. Switch Xen itself to using this format. Neither the bootwrapper nor the models care about this header themselves and real bootloaders are not widely used, so now is

2015-02-17 22:26 GMT+02:00 Eckert, Doug <doug.eckert at dowjones.com>: > We have a DHCP/PXE server in a build environment, which is separate from > our Spacewalk v1.5 server. We direct builds to Satellite or Spacewalk based > as needed. It contains initrd & vmlinuz files for each version/arch we > currently deploy for both RHEL & CEL. > > I'd like to keep the