search for: bstrap

...ong string that is written over hundreds of thousands of lines, each of length 50 characters. I am currently doing this by first inserting a space after each character in the dataset and then using the following commands: y <- as.matrix(read.table("data.txt"), stringsAsFactors=FALSE) bstrap <- sample(length(y), 100000, TRUE) write(y[bstrap], file="Rep1.txt", ncolumns=50, append=FALSE) bstrap <- sample(length(y), 100000, TRUE) write(y[bstrap], file="Rep2.txt", ncolumns=50, append=FALSE) bstrap <- sample(length(y), 100000, TRUE) . . . and so on for 500 reps....

...ss 10.215.144.7 running DHCP, TFTP and syslinux. DHCP config contains the following: next-server 10.215.144.7; filename "/pxe/syslinux/pxelinux.0"; and the 'default' pxelinux.cfg contains: LABEL altiris ??? MENU LABEL ^7. Altiris ??? COM32 pxechn.c32 ??? APPEND 10.215.144.60::/BStrap/x86pc/BStrap.0 When a PXE client boots in my network it loads the menu from 10.215.144.7. However, when the user selects menu item 7 the following message is displayed right after the "greeting message" from the second PXE server at 10.215.144.60: PXEPreZero: Invalid PXE Server list for...

...ample-with-replacement? And where does this vector come from? Suppose I want to bootstrap a confidence interval for the mean. Do i have to write my own "mean" function to provide for this defining vector of indices? Just to clarify, I want to use the boot command to replicate this: bstraps <- c() for (i in 1:R){ bstraps <- c(mean(sample(data,replace=T,n=length(data))), bstraps)} thanks, Rob -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "he...

On Fri, Mar 7, 2014 at 2:33 AM, Vieri <rentorbuy at yahoo.com> wrote: > So I take it it's more of a DHCP hack in which: > 1- client boots and gets DHCP response from 10.215.144.7 with PXE syslinux info > 2- client loads pxelinux.0 menu and selects menu that chains to Altiris PXE menu except, instead of calling pxechain.com or pxechn.c32 with the Altiris server's IP address,

...ant an animated graphics menu, go for it) as a standalone > external module. I'll probably make available a simple menu module as > an example. > > -hpa That's all I ever dreamed of :-) I'm afraid to ask - but what's it current status? BTW I tried booting "bstrap.0" file contained in the RedHat pxe RPM, and this one has the stage2 PXE menu built-in. I'm still fighting to make my DHCP server send the right "filename" tag for the selected item, but at least this one displays the PXE menu as specified (old 3com EPROMs did the same without...

...t; DHCP config contains the following: > > next-server 10.215.144.7; > filename "/pxe/syslinux/pxelinux.0"; > > and the 'default' pxelinux.cfg contains: > > LABEL altiris >? ? MENU LABEL ^7. Altiris >? ? COM32 pxechn.c32 >? ? APPEND 10.215.144.60::/BStrap/x86pc/BStrap.0 > > When a PXE client boots in my network it loads the menu from 10.215.144.7. > However, when the user selects menu item 7 the following message is displayed right after the "greeting message" from the second PXE server at 10.215.144.60: > > PXEPreZero: Inva...

Hi, I'm trying to use pxelinux to start Linux and optionally other things, maintained by windows folks. They use the Intel pxe boot loader, bstrap.0, and when I load it with a "kernel bstrap.0" statement, it fails. The reason it fails is because it can't find the !PXE data area. I guess it doesn't get the correct pointer or something along those lines. Do you think it would be easy to preserve the structure and pass it on...

...t-solution) and WDS (on W2008Stdx32). I successfully expand WDS functionally with pxelinux (4.03).I really like how pxelinux working. Server who respond on client request is on Windows 2008 (WDS). I'm trying chain PXE server to altiris and to TPM and without success. After chain to altiris file BStrap\X86pc\BStrap.0 start loading and after this file something else still loading. Will be nice to have possibility to reset dhcp options before forward to new pxe server. Please, if somebody have solution how to forward to another PXE server (need for Altiris and TPM) from pxelinux, please let me know...

...t; DHCP config contains the following: > > next-server 10.215.144.7; > filename "/pxe/syslinux/pxelinux.0"; > > and the 'default' pxelinux.cfg contains: > > LABEL altiris > MENU LABEL ^7. Altiris > COM32 pxechn.c32 > APPEND 10.215.144.60::/BStrap/x86pc/BStrap.0 > > When a PXE client boots in my network it loads the menu from 10.215.144.7. > However, when the user selects menu item 7 the following message is displayed right after the "greeting message" from the second PXE server at 10.215.144.60: > > PXEPreZero: Inva...

...he binary string I had to use as option 43. In my case the utility reported the following data: dhcp server set optionvalue 43 BINARY 06010B0807AAAA010AD7903C00 dhcp server set optionvalue 60 STRING PXEClient dhcp server set optionvalue 66 STRING 10.215.144.60 dhcp server set optionvalue 67 STRING BStrap\X86pc\BStrap.0 So I added this in my syslinux menu and I could correctly boot and load the Altiris menu: COM32 pxechn.c32 APPEND 10.215.144.60::/BStrap/x86pc/BStrap.0 -W -o 43.x=06:01:0B:08:07:AA:AA:01:0A:D7:90:3C:00 The Altiris "DHCP server discovery" option in its "PXE server...

...gt;> >> next-server 10.215.144.7; >> filename "/pxe/syslinux/pxelinux.0"; >> >> and the 'default' pxelinux.cfg contains: >> >> LABEL altiris >> MENU LABEL ^7. Altiris >> COM32 pxechn.c32 >> APPEND 10.215.144.60::/BStrap/x86pc/BStrap.0 >> >> When a PXE client boots in my network it loads the menu from 10.215.144.7. >> However, when the user selects menu item 7 the following message is displayed right after the "greeting message" from the second PXE server at 10.215.144.60: >> >&...

...is sanitized. sanitized (no real reason to but I guess it's common practice) > I presume changing only next-server and filename results in success to > boot the Altiris NBP? Oops, I misjudged the situation. It does NOT work if I replace with: next-server 10.215.144.60; filename "/BStrap/x86pc/BStap.0"; It gives me the same error message (sorry). It starts working if I remove the whole class "pxeclient" clause, ie. I remove next-server, filename and the whole class. So where is my PXE client picking up the information? I'm guessing it may be the Altiris PXE se...

...that the Altiris server provides a PXE menu, which the PXE client is expected to interpret, display for the user, and then send an appropriate followup PXE request once the user selects an item. This happens at the PXE/DHCP protocol layer, normally before any bootstrap program is loaded. The "bstrap.0" file is a small NBP that handles the menu when booting from old PXE clients that don't implement the menu-related parts of the protocol. But even with bstrap.0, the menu stuff doesn't work if the menu-related options weren't in whichever DHCP response gets used for PXE. Unfort...

----- Original Message ----- From: Jeffrey Hutzelman <jhutz at cmu.edu> > The "bstrap.0" file is a small NBP that > handles the menu when booting from old PXE clients that don't implement > the menu-related parts of the protocol.? But even with bstrap.0, the > menu stuff doesn't work if the menu-related options weren't in whichever > DHCP response gets u...

----- Original Message ----- From: Gene Cumm <gene.cumm at gmail.com> > Any chance you could sent that as a pcap file Will do asap. Thanks Vieri

....144.60.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 698, xid 0x55d9d42f, secs 4, Flags [ Broadcast ] (0x8000) ????????? Server-IP 10.215.144.60 ????????? Client-Ethernet-Address 00:24:54:d9:d4:2f (oui Unknown) ????????? sname "INF-VM-DS" ????????? file "Bstrap\X86PC\BStrap.0" ????????? Vendor-rfc1048 Extensions ??????????? Magic Cookie 0x63825363 ??????????? BS Option 13, length 2: 46 ??????????? DHCP-Message Option 53, length 1: Offer ??????????? Server-ID Option 54, length 4: 10.215.144.60 ??????????? Vendor-Class Option 60, length 9: "PXECli...

On Wed, 2014-03-05 at 13:18 -0500, Gene Cumm wrote: > Second, I notice the Altiris server specifies _3_ options of code 43, > including one of length 253. The pack/unpack _should_ handle this but > may split it differently. That's legal, and treated as if the values had been concatenated. See RFC2131, section 4.1, and particularly the second paragraph on page 24. Unfortunately, a

...ability to add/remove/replace individual vendor-encapsulated suboptions. Unfortunately, from what documentation I could find, the Altiris server generates its menu dynamically and makes no promise about what the item "types" will be. The boot item type appearing the menu will be sent by bstrap.0 in its next request, and must match one actually known to the Altiris server in order for it to provide correct boot responses. What that means is that any time you change anything about the Altiris menu, the option 43 embedded in your pxelinux config will become out of date. :-( Also, to get...