DeployStudio ForumThe best location to share your DeployStudio experiences... |
You are not logged in.
Hello
I wanted to first thank the developers for creating such a useful tool for all of us to use.
Onto my situation. I'm trying to consolidate my current PXE server with DeployStudio (since we need to image Apple machines as well now). I absolutely love the automation of DeployStudio on Apple machines and was wondering what would be different about automating imaging of PCs.
Will I be able to boot diskless systems into ramdisks automatically (Such as Slax/Dos)?
In a normal PXE config, the labels would look like
MENU LABEL Dos
KERNEL memdisk
APPEND initrd=dos/flpy.img
or
MENU LABEL Slax
KERNEL slax/boot/vmlinuz
APPEND initrd=slax/boot/pxe_initrd.gz ramdisk_size=307200 root=/dev/ram0 rw max_loop=64 nfsboot=XXX.XXX.XXX.XXX:/var/lib/tftpboot/slax autoexec=startx;
I looked in the default PXE config of deploy studio and noticed that the default label is 0 for a local boot; does that mean that a user would need to physically select another label to boot into DeployStudio or any other label?
Does DeployStudio manage custom MAC address files in the pxelinux.cfg folder to automate default entries?
Thank you for your time,
/huy
Offline
The idea is to always boot the pcs on the pxe bootloader and let the user go for a local boot (default) or netboot a small maintenance system.
This maintenance system allows you to image a complete system or restore an existing one (can be automated).
That's pretty much what it does, and won't do more than that.
Offline