General TC > General TC Talk
TinyCore with Symantec Ghost using PXE
tweetyhack:
WHAT!! I didn't know there was a linux version of ghost!! You just blew my mind! Haha.
At our shop, we've moved away from ghost to MS's imaging tools. Always good to have multiple tools though. Thanks!
tweetyhack:
@PTR73 I thought you can generate a menu in the PXE configuration. I can't remember now. I know for sure I was able to create a menu in DOS.
Try these, nothing fancy but should work.
http://www.linuxjournal.com/magazine/pxe-magic-flexible-network-booting-menus
http://www.syslinux.org/wiki/index.php/PXELINUX#Custom_Menu_Example_with_sub-menus
PTR73:
thanks Tweety, but the dos like menu style is familiar to me 8)
I even can manage to chainload a windows installation from there..
But this is not what i want. Beside running from pixie/tftp, i also want it to run directly from usb. (using the coretousb tool for our technician)
---
Ghost multicasting works also very smooth and fast with this solutions Funguy. thanks..
For wim files, i think we can use wine to run gimagex? and then install on the local system drives.
Only part i think of is about the 64bit part... hmmm were running on tinycore. Guess is that this is 32bit/x86 right.
This part is very new to me.
If we manage this part. then it is bye bye WinPE for deploying. ::)
for now, the solutions brought by Funguy gave me aplause at my office. 10 sec. loading and deploying in multicasting way also from a windows host (server) through tftp or pixie boot.
I think i will manage the wine part to get gimagex/imagex running. but very curious how to handle 64bit installations... ???
anyone?
funguy:
Easier way:
Scripted way to put ghost on TinyCore and use with PXE with most Proliant support added
1) Download the latest release candidate from http://www.tinycorelinux.net
*http://distro.ibiblio.org/tinycorelinux/4.x/x86/release/TinyCore-current.iso
2) Copy ghost files to your usb build folder (example f:\build\)
a. Browse to C:\Program Files\Symantec\Ghost
b. Copy the following files: gdisk, ghconfig, ghost, ghregedit, and omnifs to f:\build
3) Copy ghost.png icon (dimensions=48x48) to f:\build folder on your usb
4) Copy add_ghost_and_create_pxe_core.sh to the root of your usb
(Example: f:\add_ghost_and_create_pxe_core.sh)
5) Mount the TinyCore-current.iso
(oracle vm with at least 256mb ram and no hdd will do)
a. just press <enter> at the tinycore boot prompt
6) Run "add_ghost_and_create_pxe_core.sh"
a. mount the usb to the oracle vm by right clicking the usb plug
b. mount the usb inside your tinycore vm os using the Mount icon on the wbar (example: sda1)
c. Open a terminal using the icon on the wbar
d. cd /mnt/sda1
e. ./add_ghost_and_create_pxe_core.sh
f. close editor window when it pops open
g. wait until script finishes
7) sudo cp /tmp/ezremaster/ezremaster.iso /mnt/sda1
*sda1 is the usb
8) unmount the usb from tinycore and kill the vm
9) test the new iso in vm
10) Now take the cd to your pxe server
11) copy d:\boot\core.gz and d:\boot\vmlinuz to c:\tftpboot\tinycore\
12) use "editpad lite" to add this "c:\tftpboot\pxelinux.cfg\default" on your PXE server
DEFAULT vesamenu.c32
PROMPT 0
NOESCAPE 0
ALLOWOPTIONS 0
# Timeout in units of 1/10 s
TIMEOUT 60
MENU MARGIN 10
MENU ROWS 16
MENU TABMSGROW 21
MENU TIMEOUTROW 26
MENU COLOR BORDER 30;44 #20ffffff #00000000 #ffffffff
MENU COLOR SCROLLBAR 30;44 #20ffffff #00000000 none
MENU COLOR TITLE 0 #ffffffff #00000000 none
MENU COLOR SEL 30;47 #40000000 #20ffffff
MENU BACKGROUND menu.jpg
MENU TITLE PXE Menu
LABEL Boot from Harddisk
LOCALBOOT 0
Type 0x80
label Tinycore with ghost
kernel tinycore/vmlinuz
append initrd=tinycore/core.gz cde nozswap
*****OLD POST: Get fixed new script from Jan 3rd, 2013 post*********
tinypoodle:
Not sure if I entirely understood right, but if this is a concept which requires:
A: a running windows OS in order to create a core remaster
B: a virtual linux machine with 256MB RAM
C: a second running windows OS with a pxe server
... and all that just to be able to run the linux version of ghost...
then I really don't get the point.
P.S.: Upper are my own assumptions just based on syntax of paths, as requirements
do not appear to be explicitely mentioned anywhere.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version