SCIENTIFIC-LINUX-DEVEL Archives

May 2008

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Troy Dawson <[log in to unmask]>
Reply To:
Troy Dawson <[log in to unmask]>
Date:
Tue, 6 May 2008 16:44:09 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (81 lines)
We have not taken vnc out of the installer.
I have not ever done a vnc install.
In looking through TUV's installation manual, the only place it talks 
about doing vnc installs is with the IBM system-z.  That's a bit odd 
actually, maybe I'm looking in the wrong place.
Where in the installation manual is the instructions?

Troy
Andrew Elwell wrote:
> Hi folks,
> 
> I see from TUV's installation manual I should be able to launch a vnc
> server as part of the install procedure.
> 
> however I don't seem to get this working - perhaps because I force
> text mode anyway? or is it disabled in the SL version of anaconda?
> 
> I have (in the pxe config)
>         append initrd=initrd-sl-5x-i386 keymap=uk lang=en_GB ks=http://master.beowulf.cluster/alt/autokick.php
>   ksdevice=eth0 vnc
> 
> 
> and in the generated kickstart config:
> 
> install
> url --url http://master.beowulf.cluster/linux/scientific/5x/i386
> network --device=eth0 --bootproto dhcp
> lang en_GB.UTF-8
> langsupport --default en_GB.UTF-8 en_GB.UTF-8
> keyboard uk
> mouse none
> skipx
> text
> rootpw --iscrypted [REMOVED]
> authconfig --enableshadow --enablemd5
> timezone --utc Europe/London
> bootloader --location=mbr
> reboot
> vnc
> clearpart --initlabel --all --drives=hda
> part /boot --fstype "ext3" --size=200 --ondisk=hda
> part pv.4 --size=0 --grow --ondisk=hda
> volgroup linuxvg pv.4
> logvol / --fstype "ext3" --size=1024 --grow --maxsize=4096 --
> name=rootlv --vgname=linuxvg
> logvol swap --fstype swap --size=1024 --grow --maxsize=4096 --
> name=swaplv --vgname=linuxvg
> logvol /opt --fstype "ext3" --size=1024 --grow --maxsize=4096 --
> name=optlv --vgname=linuxvg
> logvol /var --fstype "ext3" --size=4096 --grow --maxsize=8192 --
> name=varlv --vgname=linuxvg
> logvol /home --fstype "ext3" --size=1024 --name=homelv --vgname=linuxvg
> logvol /tmp --fstype "ext3" --size=8000 --name=tmplv --vgname=linuxvg
> 
> 
> I'm not doing the 'connect to listening client' voodoo - but I was
> under the impression this would still work if I connect a client at
> the right time on the right (unspecified!) port
> 
> 
> If anyone has experience of this could they let me know?
> 
> Many thanks
> 
> Andrew
> 
> 
> Andrew
> --
> Andrew Elwell
> [log in to unmask]
> Tel: +44 141 330 6439
> Mob: +44 7952 922263


-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/CSS  CSI Group
__________________________________________________

ATOM RSS1 RSS2