search for: vandeputte

...ut what? Does a howto, similar to the one below, exist? Another problem I get is that pxelinux doesn't find the disk image file as soon as it's 94371840 bytes large. 94370816 bytes is fine. The amount of allocated memory in VMWare doesn't seem to affect this. Best regards, Pascal Vandeputte ******************************************************************************** How to create a PXE-bootable disk image of the FreeBSD "bootonly" install ISO ============================================================================= Based on an e-mail by Shaun Reitan on the SYSL...

...cts). Find more info about the conference, travel, accommodation and more, at the conference website http://2008.euroBSDCon.org/. The conference program is in the capable hands of: * Mathieu Arnold * Emmanuel Dreyfus * Philip Paeps * Ollivier Robert * Thierry Thomas * Wim Vandeputte * Robert Watson -- Mathieu Arnold

Good morning. I am trying to do a dhcp/pxelinux network install for redhat linux. I have a new Dell computer with a Broadcom NetXtreme 57xx Gibabit controller. I am getting the following errors: Getting Kickstart file. ASSERT: no network device in ChooseNetworkInterface No network drivers for doing kickstart unable to bring up network. I've searched this lists archives for the word ASSERT

Hi i want to add the FreeBSD 6.2 release to our installserver according to the manual http://syslinux.zytor.com/archives/2007-April/008420.html But if I type FreeBSD-6.2 at the pxelinux boot prompt the created image load but nothing happens. ?boot: FreeBSD-6.2 Loading memdisk.... Loading

>Forwarding a message from Steve \"Stevers!\" Coile: >> This is already possible. Create the file then unlink it. The file >> contents aren''t deleted and i-node isn''t released until the file is >> closed. > >Without kernel support, unlinking the file at creation time requires >a code change in the process which creates the file. And this

I reported the following vulnerability to AUSCERT, but they weren''t interested. People on this list might be, though! GNU tar is lazy about file creation modes and file owners when unpacking a tar file. Because GNU tar defaults to creating files owned by the userid running tar when the username is not found on your system, it can be possible to inadvertantly create setuid root