similar to: Using pxelinux mboot.c32 to jumpstart a Solaris host

Hi All, Now that we have multiboot capable pxelinux, thanks to mboot.c32, I decided to try and remove pxegrub from my x86 jumpstart infrastructure since, in theory, pxelinux can now do it all. The problem I'm having is I'm not very sure I'm following Tim's documentation correctly... I'm not 100% what comes after the --- and whether the Sun kernel needs it's arguments

Hello Using pxelinux for so long time i don't want to use pxegrub to PXE boot solaris 10 on x86 . So i would like to use pxelinux to do this jobs . I use ipappend and mboot.c32 however i don't success to have the kernel argument appended with BOOTIF : here is what i use : LABEL solaris MENU DEFAULT MENU LABEL Solaris Jumpstart KERNEL mboot.c32 APPEND multiboot kernel/unix

I'm having some difficulties pxe booting Solaris. So far I have tried the mboot.c32, and the pxegrub shipped with Solaris. At first I had some problems with blksize, but this disapeared when I changed from atftpd to tftpd-hpa. The point at which I'm stuck now is, the kernel and x86.microroot/x86.miniroot is loaded but then VMWare crashes. I might try with real hardware, but I thought

Hello, I am trying to boot x86 solaris 10 8/07 via a system running fed7 and syslinux 3.62. If I use pxelinux I get the kernel to boot but it doesn't load my network drivers for the Broadcom II nic. I rebuilt the kernel (x86.miniroot) for solaris with the Broadcom nic drivers but it still didn't work. I read some stuff where people were using pxegrub and booting pxegrub.0 but

I understand that currently, at least under Solaris 10u6, it is not possible to jumpstart a new system with a zfs root using a flash archive as a source. Can anyone comment as to whether this restriction will pass in the near term, or if this is a while out (6+ months) before this will be possible? Thanks, Jerry

Hello, I don't know how off the wall this question will be, but first let me say that I've found your buildpkg.sh script very useful in creating an OpenSSH package for use on my Solaris systems. Currently I'm trying to set up a fully automated JumpStart system at my workplace, and I'm realizing that the 'postinstall' script (and possibly some of the other install scripts)

Let me thank everyone in advance. I''ve read a number of posts here and it helped tremendously in getting the install done. I have a couple of remaining issues which I can''t seem to overcome. Here are the basics: dom0 - CentOS 5.2 32-bit Xen 3.2.1 compiles from source domU - os200805.iso The install config: [root@internetpowagroup oshman]# cat opensolaris.install name =

Hi everybody, Today I tried the latest Solaris on Xen build. I downlaoded all files and created the iso. Then I wanted to run setup_install_server , but this failed: bash-3.00# ./setup_install_server /export/sol_xen/ -bash: ./setup_install_server: cannot execute binary file -bash-3.00# So I create a tar file to copy over all files to export/sol_xen/ Then I tried to start and install via

Not that I''m much of a Solaris guy, and definitely not a Solaris 10 guy, but since nobody else had posted anything yet: http://reductivelabs.com/trac/puppet/wiki/PuppetSolaris#Solaris10 The good news is that it appears to be a completely hands-off puppetd installation. Just sign the client key afterwards on the puppetmaster and you''re set. The bad news is that it''s

Anyone have idea how to create ZFS pool and volumes during jumstart instalation ? (I''m using JumpStart Enterprise Toolkit) kloczek

I have zfs on my base T5210 box installed with LDOMS (v.1.0.3). Every time I try to jumpstart my Guest machine, I get the following error. ERROR: One or more disks are found, but one of the following problems exists: - Hardware failure - The disk(s) available on this system cannot be used to install Solaris Software. They do not have a valid label. If you want to use the

Hi Some time ago I wrote this mailing list about some extra time that it takes for my system to boot and I don't know where it came from.I'm using a custom BIOS which loads at 1 second and now I've found out that it takes for the bootloader and OS an extra 1 second to load when keyboard is disconnected.I got from the BIOS engineer the following explanation and steps to take: In

Warning: WINE Newbie Alert. Proceed with caution.... Background: I don't want to fork up $$$ for a separate Windows machine for my kid so I've decided to see if I can run any of the popular brain-rot software under WINE (Is it "WINE" or "Wine" or "wine"?) on a Linux 2.4.18 kernel. My first project is a vintage 1995 version of JumpStart Kindergarten. Seeing

I'm trying to get Knowledge Adventure's Jumpstart Preschool to run under wine 0.9 on debian stable. According to <http://appdb.winehq.org/appview.php?appId=801> this program works flawlessly. But when I try it, it runs until I get just past the introduction and then a sudden crash. Fortunatly it keeps a log and the log says: MIDI driver error processing MENU\MID\MM000_.WSB So my

Hello, we have the following problem: - a new Dell Optiplex 740 boots pxelinux.0 - loads the kernel - start to load the miniroot.gz and crashs after loading about 1/5 of the miniroot The tftpd messages are: Feb 21 14:48:32 srv006 atftpd[26225]: Advanced Trivial FTP server started (0.7) Feb 21 14:48:32 srv006 atftpd[26225]: Serving /linux/pxelinux.0 to 10.10.100.113:2070 Feb 21 14:48:32 srv006

Hi, I am currently trying to replace our companies elilo UEFI PXE boot with syslinux. I compiled all the needed files and the DHCP distributes them fine to the requesting client. However when I try to boot our companies miniroot the DHCP serves the file, but it seems like it never finishes. The image is generated with the following command: find . | grep -v 'name'.bz2 | cpio -o -H newc

I have the following problem with syslinux. With boards with same core chipset and bios, syslinux fails on some boards. The difference on boards are that the ones that succeed has standard PC components (KBC, PATA). The ones that failes have SATA only and no KBC. It does not matter if I boot from USB or Compact flash drive. I has been noted that the bootloader calls BIOS functions for a drive

I am trying to use Syslinux as my boot loader for a stripped down version of Knoppix (DSL) on a USB Pen Drive. I followed the instructions verbatim on http://rz-obrian.rz.uni-karlsruhe.de/knoppix-usb/knoppix-usb.html, but no luck. The system will start to boot to the USB, but gives a Kernel Panic. I will give all information that shows on the screen. After I select Boot from USB (which on my

On 21.09.2015 12:06, Gene Cumm wrote: > On Mon, Sep 21, 2015 at 2:38 AM, Mathias Radtke <m.radtke at uib.de> wrote: >> >> On 18.09.2015 16:35, Gene Cumm wrote: >>> 1) This is actually a critical cusp size. Watch what tftpd you use or >>> you'll never get it all. The tftpd needs to support rollover. >>> Consider HTTP as it should be more capable

************************ Installation profile ************************ [root@ServerRHL51 vm]# cat snv85.install name = "Solaris85pvm" vcpus = 1 memory = "1024" kernel = "/usr/lib/xen-solaris/unix-85" ramdisk = "/usr/lib/xen-solaris/x86.miniroot-85" extra = "/platform/i86xpv/kernel/amd64/unix - nowin -B install_media=cdrom" disk =