T********r
发帖数: 6210 | 1 【 以下文字转载自 Linux 讨论区 】
【 原文由 Terminator 所发表 】
read relevant documents at docs.sun.com, or following my steps below:
on your new system, do the following:
1. Create a directory for CD image:
# mkdir -p install_dir_path
2. Mount ISO image, (the first disk need special handling!!! read
sun.mount.sol9.iso.html for details)
# lofiadm -a /absolute_path/iso_image
# mount -F hsfs -o ro /dev/lofi/1 /mnt
3. Change to the Tools directory on the mounted disc.
If it is the first CD, execute the |
c**o
发帖数: 166 | 2 Did this one work for you?
How could you boot your client?
Where is your boot server?
【在 T********r 的大作中提到】
: 【 以下文字转载自 Linux 讨论区 】
: 【 原文由 Terminator 所发表 】
: read relevant documents at docs.sun.com, or following my steps below:
: on your new system, do the following:
: 1. Create a directory for CD image:
: # mkdir -p install_dir_path
: 2. Mount ISO image, (the first disk need special handling!!! read
: sun.mount.sol9.iso.html for details)
: # lofiadm -a /absolute_path/iso_image
: # mount -F hsfs -o ro /dev/lofi/1 /mnt
|
T********r
发帖数: 6210 | 3 yes, it worked for me. sun's doc states that it is unnecessary to have a
boot server when the client and server are in the same subnet.
【在 c**o 的大作中提到】
: Did this one work for you?
: How could you boot your client?
: Where is your boot server?
|
x*********g
发帖数: 11508 | 4 对，我也做过一次，client是boot到prompt状态，然后只要从 client 机器的prompt里用
boot network就行了。
【在 T********r 的大作中提到】
: yes, it worked for me. sun's doc states that it is unnecessary to have a
: boot server when the client and server are in the same subnet.
|
F**********e
发帖数: 2135 | 5 【 以下文字转载自 Linux 讨论区 】
【 原文由 FridayInLove 所发表 】
安装经历update:
依照这个做法，我把网络内一台无关的pc断开，然后在dns, dhcp server
把该pc的ip和网名分给了待安装机器的mac。制作install server一切顺利。
直到client boot net的时候，一直起不来。后来在install server强行执行
add_install_client -e aa:bb:cc:dd:ee:ff aaa sun4u，显示说NIS ethers map
里面的mac address与指明的不同。修改了nis ether map以后重新boot net，
一切顺利。 |
c**o
发帖数: 166 | 6 I think you should at least add the ethernet address from the command when you
add client ...
if your system is "new" or your system was on the net but ip is taken over.
Otherwise, how does tftp server know
which machine it is going to boot? Apparantly, you are not using DHCP.
【在 T********r 的大作中提到】
: yes, it worked for me. sun's doc states that it is unnecessary to have a
: boot server when the client and server are in the same subnet.
|
c**o
发帖数: 166 | 7 In fact, I think, name service should not matter. Only ethernet address
matters.
【在 F**********e 的大作中提到】
: 【 以下文字转载自 Linux 讨论区 】
: 【 原文由 FridayInLove 所发表 】
: 安装经历update:
: 依照这个做法，我把网络内一台无关的pc断开，然后在dns, dhcp server
: 把该pc的ip和网名分给了待安装机器的mac。制作install server一切顺利。
: 直到client boot net的时候，一直起不来。后来在install server强行执行
: add_install_client -e aa:bb:cc:dd:ee:ff aaa sun4u，显示说NIS ethers map
: 里面的mac address与指明的不同。修改了nis ether map以后重新boot net，
: 一切顺利。
|
F**********e
发帖数: 2135 | 8 hehe that's what i thought, so that i didn't look into nis part at first.
but the installation just wouldn't go on until i changed the nis map value
【在 c**o 的大作中提到】
: In fact, I think, name service should not matter. Only ethernet address
: matters.
|
T********r
发帖数: 6210 | 9 IP does not matter as far as there is an empty IP not taken in the subnet.
DNS name does not matter either. At boot stage, the clients use ARP and
broadcasting to discover install server. the install server can use its
hosts file to decide the client's possible IP.
The only thing possibly missed in my list of steps is the ethernet address
and client's IP. To do so, before step 6, do this:
echo "xx:xx:xx:xx:xx:xx clientname" >> /etc/ethers
echo "empty.ip.address clientname" >> /etc/hosts
wher
【在 c**o 的大作中提到】
: I think you should at least add the ethernet address from the command when you
: add client ...
: if your system is "new" or your system was on the net but ip is taken over.
: Otherwise, how does tftp server know
: which machine it is going to boot? Apparantly, you are not using DHCP.
|
l******t
发帖数: 108 | 10 i think /etc/ethers is needed by bootp, /etc/hosts will be used if no
NIS server involded.
in IRIX the default bootfile and host-specific bootfile can be configured
in /etc/bootptab. does SUN have a similar file?
/etc/bootparams is also related.
it's bootp for booting, tftp for transfering files
【在 T********r 的大作中提到】
: IP does not matter as far as there is an empty IP not taken in the subnet.
: DNS name does not matter either. At boot stage, the clients use ARP and
: broadcasting to discover install server. the install server can use its
: hosts file to decide the client's possible IP.
: The only thing possibly missed in my list of steps is the ethernet address
: and client's IP. To do so, before step 6, do this:
: echo "xx:xx:xx:xx:xx:xx clientname" >> /etc/ethers
: echo "empty.ip.address clientname" >> /etc/hosts
: wher
|
c******y
发帖数: 37 | 11 Not exactly true. You need a boot server regardless of whether the
client and the server are in the same subnet. O/w, how could a client
get it's IP address and kernel image? But in your case you
have the boot server, the install server and the sysidcfg server
all in the same host.
【在 T********r 的大作中提到】
: yes, it worked for me. sun's doc states that it is unnecessary to have a
: boot server when the client and server are in the same subnet.
|
