search for: mylabeler

Hi All, I'm working on a class example that demonstrates one way to deal with factors and their labels. I create a function called myLabeler and apply it with lapply. It works on the whole data frame when I subscript it as in lapply( myQFvars[ ,myQFnames ], myLabeler ) but does not work if I leave the [] subscripts off. I would appreciate it if anyone could tell me why. The program below works up until the final two statements. Thanks,...

Hi, llvm-gcc 4.2 generates warnings when I compile inline assembly code that contains used labels with -Wunused-label. The generated code seems to work yet. gcc 4.2 doesn't generate those warnings. I haven't found any bugs regarding this issue in the llvm bug database. Does anyone know if this is a known llvm issue? Is it a warning that I can ignore and does not affect the generated

I have to deal with data frames that contain multiple entries of the same (based on an identifying collumn 'id'). The second collumn is mostly corresponding to the the id collumn which means that double entries can be eliminated with ?unique. a <- unique(data.frame(timestamp=c(3,3,3,5,8), mylabel=c("a","a","a","b","c"))) However

In Syslinux 5-6.02, the "global append" directive is being (unintentionally) ignored in some cases. Updating Syslinux from prior versions, when using a "global append" directive, will cause unexpected results. For example, take the following simple configuration file: *** DEFAULT mykernel APPEND root=/dev/sda2 *** Note that the 'append' line is a global

This is fixed in TOT (rev 107051 for C, 108732 for C++) On Jul 23, 2010, at 2:20 AMPDT, Alexandre Colucci wrote: > Hi, > > llvm-gcc 4.2 generates warnings when I compile inline assembly code > that contains used labels with -Wunused-label. The generated code > seems to work yet. gcc 4.2 doesn't generate those warnings. I > haven't found any bugs regarding this

> On 03/19/2017 04:03 PM, David Christensen wrote: > > [ 0.600883] ---[ end Kernel panic - not syncing: VFS: Unable to mount > > root fs on unkonwn-block(0,0) > > Similar kernel panic when booted on Intel DQ67SW i7-2600S. > > > David > That's because your syslinux.cfg is "wrong", but the behavior just proves that SYSLINUX is indeed

I''ve got a block of code that''s turning out.. well - just plain ugly. So i know I must not be doing it the Ruby way. The main problem I''m having is in dealing with handling errors - and just not finding much Rails documentation that gives a deeper understanding of how to handle errors in Rails (outside of several docs on the catch-all''s) the main method

I have a set of labels arranged along a timeframe in a. Each label has a timestamp and marks a state until the next label. The dataframe a contains 5 such timestamps and 5 associated labels. This means, on a continious scale between 1-100, there are 5 markers. E.g. 'abc' marks the timestampls between 10 and 19, 'def' marks the timestamps between 20 and 32, and so on. a <-

Hello Almighty All, I am trying to get the LoMAC module revoke user's privileges. In my test setup, the user with a higher clearance tries to open a lower clearance file for reading. After that the process label of the user's process is checked. As a final test, the user's process tries to write to a file with the higher integrity label. And he succeeds. Please find my test setup

Hallo, linux-btrfs, please delete the option "-L" (for labelling) in "mkfs.btrfs", in some configurations it doesn''t work as expected. My usual way: mkfs.btrfs -d raid0 -m raid1 /dev/sdb /dev/sdc /dev/sdd ... One call for some devices. Wenn I add the option "-L mylabel" then each device gets the same label, and therefore some other programs

On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???

When using the CLI and calling a LABEL "mylabel", specifying "mylabel options" does not pass "options" through to the kernel's command line. -- -Gene

On Fri, Nov 30, 2018 at 9:56 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > @Carl, > > I have a proposal for you here (in the Syslinux mailing list): let's > first find out _what_ exactly is required in order to boot in UEFI > mode, and then you can take the info downstream. Whether "downstream" > means your own personal customized boot.img, or

Here is another, perhaps trivial, plotting question. I am making a filled contour plot and have almost everything dialed in the way I want it. The last hurdle (that I can foresee) is adjusting the look of the key. I'm plotting the 25%, 50%, 75%, and 95% quantiles and I want the key to be evenly spaced, e.g., the width of the 25% and the 95% should look the same on the key. They are labeled

I am resending this, as I believe it has not arrived on the mailing list when I first emailed. I have a set of labels arranged along a timeframe in a. Each label has a timestamp and marks a state until the next label. The dataframe a contains 5 such timestamps and 5 associated labels. This means, on a continious scale between 1-100, there are 5 markers. E.g. 'abc' marks the timestampls

Dear R users, I am encountering a x axis labeling problem on quite basic plots... I use the following code which displays the labels on the x-axis with a 45 degrees angle: p <- plot(myobject1, type="b", col="red",cex=1, lwd=2, axes=FALSE, ann=FALSE, ylim=c(0,70)) title(main="title", font.main=4) axis(side=1, lab=F) text(axTicks(1), par("usr")[3] - 2,

Hello - and sorry for what might look like a simple graphics question. I am building an interaction plot for d: d=data.frame(xx=c(3,3,2,2,1,1),yy=c(4,3,4,3,4,3),zz=c(5.1,4.4,3.5,3.3,-1.1,-1.3)) d[[1]]<-as.factor(d[[1]]) d[[2]]<-as.factor(d[[2]]) print(d) interaction.plot(d$xx, d$yy, d$zz, type="b", col=c("red","blue"), legend=F, lty=c(1,2), lwd=2,

Hello, At the boot prompt ALLOWOPTIONS 0 is only applied to implicit kernels and not to labels. For configuration which want to allow selection, but prevent customization of the kernel command line, this behaviour is bad. Also the IMPLICIT 0 is applied to both the boot prompt and configuration setting (like DEFAULT); but one could argue that only the command supplied at the prompt make sense to

On Wed, Oct 4, 2017 at 11:10 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > FWIW, the _need_ to use linux.c32 is becoming more common (in the sense > that other loading methods are not always capable of loading > newer/current kernels+initrams+additional_files, considering their > sizes). Unfortunately, only a minority of users seem to be aware of > Syslinux's

> > When booting in UEFI x64 mode in your next test, you should see a boot > > menu. > > Nope: > > *** Press enter to boot the default label *** > Failed to load libcom32.c32 > Failed to load COM32 file SYSLINUX/EFI64/vesamenu.c32 > boot: > > > I'd like to ask you to test all the entries in the menu and > > report the results for each. If,