search for: boot2

Hi, Does anyone know what the error message mean? > Boot2.Pillai <- function(x, ind) { + x <- as.matrix(x[,2:ncol(x)]) + boot.x <- as.factor(x[ind, 1]) + boot.man <- manova(x ~ boot.x) + summary(manova(boot.man))[[4]][[3]] + } > > man.res <- manova(as.matrix(pl.nosite) ~ + as.factor(plankton.new[,1]))$residu...

...(1) The typical way by generating indices in the package: boot1 <- function (data, indices) { d <- data[indices] return(d) } AA <- c(1:10) require(boot) set.seed(123) results1 <- boot(data= AA, statistic=boot1, R=100) (2) The alternative way by calculating "indices" myself: boot2 <- function (data,indices) { indices <- sample(data, replace=TRUE) d <- data[indices] return(d) } AA <- c(1:10) set.seed(123) results2 <- boot(data= AA, statistic=boot2, R=100) When I looked up using results1$t and results2$t, I had totoally different bootstrap samples. I found...

...e Cumm <gene.cumm at gmail.com> --- If, for example, you had two labels that only differed by the length of the label (a short name) or additional APPENDd parameters, this would reduce the amount of copies of the same configuration. LABEL boot1 KERNEL kernel APPEND initrd=initrd.img LABEL boot2 KERNEL kernel APPEND initrd=initrd.img extraParamForBoot2 could be shortened to LABEL boot1 KERNEL kernel APPEND initrd=initrd.img LABEL boot2 KERNEL alias.c32 APPEND boot1 extraParamForBoot2 I created this as I've got several instances of both short names and extra APPENDd parameters in a...

Hi all, A recent thread inspired me to try getting a proper serial console working on a Supermicro X9SCL motherboard with IPMI. However I find that while I see loader messages and the getty I enabled after boot I don't get any kernel messages which does somewhat limit the utility.. The BMC creates COM3 (/dev/cuau2) which works with getty. I modified /boot/loader.conf like so..

Hi all I'm looking at setting up software RAID 10, using CentOS 5.1 x64 - what is the best way todo this? I'm reading some sources on the internet, and get a lot of different "suggestions" 1 suggestion says to boot up with a Live CD like Knoppix or SystemRescueCD, setup the RAID 10 partitions, and then install Linux from there. 2. Another is to setup a small RAID 1 on the

...Peter Anvin feels it is most appropriate. If, for example, you had two labels that only differed by the length of the label (a short name) or additional APPENDd parameters, this would reduce the amount of copies of the same configuration. LABEL boot1 KERNEL kernel APPEND initrd=initrd.img LABEL boot2 KERNEL kernel APPEND initrd=initrd.img extraParamForBoot2 could be shortened to LABEL boot1 KERNEL kernel APPEND initrd=initrd.img LABEL boot2 KERNEL alias.c32 APPEND boot1 extraParamForBoot2 I created this as I've got several instances of both short names and extra APPENDd parameters in a...

...im : chr "ordinary" $ call : language boot(data = x, statistic = mean, R = 10) $ stype : chr "i" $ strata : num [1:10] 1 1 1 1 1 1 1 1 1 1 $ weights : num [1:10] 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 0.1 - attr(*, "class")= chr "boot" > x.boot2 <- boot(x, myMean, R=10) > str(x.boot2) List of 11 $ t0 : num 5.5 $ t : num [1:10, 1] 5.7 6.4 5.4 4.9 7.2 4.6 4.4 5.4 5.7 5.9 $ R : num 10 $ data : int [1:10] 1 2 3 4 5 6 7 8 9 10 $ seed : int [1:626] 403 201 106329237 1120199471 -647917002 -657447328 35548073...

...ckstart file: zerombr yes clearpart --all --initlabel bootloader --location=mbr part /boot --fstype ext3 --size 250 --asprimary --ondisk sda part swap --size 2048 --asprimary --ondisk sda part raid.01 --size 40000 --asprimary --ondisk sda part raid.03 --size 1 --grow --asprimary --ondisk sda part /boot2 --fstype ext3 --size 250 --asprimary --ondisk sdb part swap --size 2048 --asprimary --ondisk sdb part raid.02 --size 40000 --asprimary --ondisk sdb part raid.04 --size 1 --grow --asprimary --ondisk sdb raid / --level=1 --device=md0 --fstype ext3 raid.01 raid.02 raid /home --level=1 --device=md1 --f...

I'm trying to make a set of contour plots of bivariate kernel density estimates, showing three such plots overlaid, similar to this plot http://euclid.psych.yorku.ca/SCS/Private/Test/ridge-boot2.pdf except that I would like to have the contours *filled* (using transparent colors). To make this reproducible, I've saved the results of KernSmooth::bkde2D() in the following file: http://euclid.psych.yorku.ca/SCS/Private/Test/bkde2D-boot.RData From this, the essence of my plot can be...

Hello, I have a problem with loader. I recently upgraded from 6_rel to 7_rel. Now when I install world there is a problem booting. Here is what I do: cd /usr/src make buildworld make buildkernel KERNCONF=BLACK make installkernel KERNCONF=BLACK At this point I can reboot and all is good. After boot I install the new world: cd /usr/src mergemaster -p reboot into single user mode cd /usr/src make

...; (if you know how to handle it) to create the boot logo, keep in mind that it will have (at the end) only 16 color. - make sure it has 640 width. - save it as gif <black magic> - use the tool : mogrify -colors 16 boot1.gif - Then check with giftrans the colorpalette: giftrans -l boot2.gif Pick a white entry and swap it with the palette entry 7. because 7 will be used as the text color. eg: giftrans -g 11=7 </black magic> Then use giftoppm and make a ppm file, now you can use the ppmtolss conversion program in syslinux. happy booting, Martin

...osboot/../../../../include -I/usr/src/sys/i386/boot/biosboot/../../.. -I/usr/src/sys/i386/boot/biosboot -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -N -T 0 -nostdlib -static -o boot start.o table.o boot2.o boot.o asm.o bios.o serial.o probe_keyboard.o io.o disk.o sys.o serial.o: Undefined symbol `COMBRD' referenced from text segment serial.o: Undefined symbol `COMBRD' referenced from text segment *** Error code 1 Stop in /usr/src/sys/i386/boot/biosboot. casa# Can any one please help? fe...

...is that I've never setup any kind of RAID on that old box... Is there a way to completely disable GEOM_RAID loading on boot ? Here are the obligatory blurry-cellphone-pictures of the boot messages : https://www.dropbox.com/s/wqgjsf1adhoaksb/boot1.jpg https://www.dropbox.com/s/99z1cojz22w7jn4/boot2.jpg https://www.dropbox.com/s/7hk1inrhd1k59zi/boot3.jpg The motherboard is an old GA-8IG100MK, fitted with two supplementary 3com NICs. The specs can be found here : http://www.gigabyte.com/products/product-page.aspx?pid=1655#sp Chipset : - North Bridge : Intel? 865G GMCH - Intel? 82801EB...

...sert and a test that verify r221709's fix. > > > Enable AArch64 support for FreeBSD: > > http://llvm.org/viewvc/llvm-project?rev=221900&view=rev > > Hook up FreeBSD AArch64 support > > Patch from Andrew Turner. > > > Partially fix FreeBSD boot2 size optimization regressions: > > http://llvm.org/viewvc/llvm-project?rev=222562&view=rev > > Disable header duplication at -Oz in loop-rotate pass. > > > -Dimitry >

I have been running Fedora for a number of years and have decided that for my mailserver system (which doubles as a small time web server) I want to go to an OS that has a supported lifespan of more than a year, especially since this machine has in the past been up longer than a year without reboots. The machine that it will ultimately host the OS is a dual processor P3 machine with 2GB of

...CRC 9632318a Kernel: arch/x86/boot/bzImage is ready (#5) MODPOST 1509 modules * LD [M] drivers/usb/serial/keyspan_pda.ko IHEX2FW firmware/emi26/loader.fw IHEX2FW firmware/emi26/firmware.fw IHEX2FW firmware/emi26/bitstream.fw H16TOFW firmware/edgeport/boot.fw H16TOFW firmware/edgeport/boot2.fw H16TOFW firmware/edgeport/down.fw H16TOFW firmware/edgeport/down2.fw IHEX2FW firmware/whiteheat_loader.fw IHEX2FW firmware/whiteheat.fw IHEX2FW firmware/keyspan_pda/keyspan_pda.fw IHEX2FW firmware/keyspan_pda/xircom_pgs.fw* In here we can see that these modules are getting compiled....

...CRC 9632318a Kernel: arch/x86/boot/bzImage is ready (#5) MODPOST 1509 modules * LD [M] drivers/usb/serial/keyspan_pda.ko IHEX2FW firmware/emi26/loader.fw IHEX2FW firmware/emi26/firmware.fw IHEX2FW firmware/emi26/bitstream.fw H16TOFW firmware/edgeport/boot.fw H16TOFW firmware/edgeport/boot2.fw H16TOFW firmware/edgeport/down.fw H16TOFW firmware/edgeport/down2.fw IHEX2FW firmware/whiteheat_loader.fw IHEX2FW firmware/whiteheat.fw IHEX2FW firmware/keyspan_pda/keyspan_pda.fw IHEX2FW firmware/keyspan_pda/xircom_pgs.fw* In here we can see that these modules are getting compiled....

...ives only, and an Adaptec 39160 with two internal and two external U160 channels. I have set up a software RAID config with LVM2 on top (CentOS 4) with four 36GB 15K RPM Ultra 3 drives. The internal drives are set up with /dev/sda and /dev/sdb partitioned with 100MB /boot (for sda) and 100MB /boot2 (backup on sdb), and the rest of each drive as mirrors on a RAID1. /dev/sdc and sdd have each a single RAID partition and are likewise mirrors in a RAID1. So I have /dev/md0 and /dev/md1, which are then two parts of a physical volume with the various logical volumes under that. This works an...

I can't seem to get my serial terminal to work with my new system. I had a serial terminal connected to my old system that worked great and copied /boot.config, /boot/loader.conf and /etc/ttys settings over from it. The new system has a Gigabyte GA970A-UD3 board with just a serial header on the board. I bought a serial connector backplate in an electronics store and connected it to the

On Wed, Nov 26, 2014 at 10:15:13AM +0000, Daniel Sanders wrote: > > From: Daniel Sanders > > Sent: 25 November 2014 17:39 > > To: Eric Christopher; Tom Stellard > > Cc: LLVM Developers Mailing List (llvmdev at cs.uiuc.edu) > > Subject: RE: [LLVMdev] Proposed patches for Clang 3.5.1 > > > > > > > > I'd also like to propose the inclusion of