Thanks for your feedback. I agree that separating the networks and
isolating the build network thus eliminating the need for VLAN tagging
is the ideal scenario. Unfortunately, influencing those changes are
beyond my sphere of influence in this particular case.
At the end of the day, our
I thought I would follow up on this as a couple individuals expressed
an interest in it...
We have isolated the configuration in which this occurs under. It
occurs during the execution of pxeboot.bs on brocade switches with
vlan tagging enabled.
We have begun to review the pxeboot.bs source
Hi
On 14/03/2012 11:44, Rick Miller wrote:
I thought I would follow up on this as a couple individuals expressed
an interest in it...
We have isolated the configuration in which this occurs under. It
occurs during the execution of pxeboot.bs on brocade switches with
vlan tagging enabled.
From: Rick Miller vmil...@hostileadmin.com
To: Erik Nørgaard norga...@locolomo.org; freebsd-questions@freebsd.org
Sent: Sunday, March 4, 2012 3:51 PM
Subject: Re: Running OS tftp vs. pxeboot tftp
Hi Erik,
Thanks for getting back to me. The original problem is the same
issue...we are still
Hi Erik,
Thanks for getting back to me. The original problem is the same
issue...we are still working it, but we've isolated the configuration
where the issue manifests itself. It has to do with the FreeBSD
pxeboot and Brocade switches. We will continue troubleshooting in our
lab. When we've
Hi,
I've got a 9.0-R amd64 system I'm trying to netboot / pxeboot from the
network, to install other machines (and do fixups etc.)
I set this up as we setup previous versions here - but setting up a tftp
server, and nfs server - and 'dumping' the contents of the install CD to a
directory
amd64 system I'm trying to netboot / pxeboot from the
network, to install other machines (and do fixups etc.)
I set this up as we setup previous versions here - but setting up a tftp
server, and nfs server - and 'dumping' the contents of the install CD to a
directory on the dhcp server, which
--On 01 March 2012 11:53 +0100 ego...@ramattack.net wrote:
So I recomend you reading last mails of mine in freebsd-hackers...
Hope it helps,
Bye!
For what it's worth - I've resolved the issue I had (which was basically
the system booted, but failed trying to re-mount root as RW, and hence
Hi All,
Are there significant differences in the implementation between the
tftp client in FreeBSD 8.2-RELEASE and the client implementation in
pxeboot.bs?
I ask because I have encountered a scenario where pxeboot.bs is
tftp'ing boot files from a PXE server and fails in random spots while
In the new way of booting... you need to have the cd because the own
cd is the root filesystem... and in fact is live filesystem too so
unless you're booting from mfsroot... I assume you should have that line
in /etc/fstab inside the iso image but if you're using mfsroot... I
really
Hi,
I wanted to experiment a bit with pxeboot. Therefore I created a zfs clone
of a jail filesystem. The clone was shared as via nfs. Pxeboot complained
that it can't load the kernel. The pxeboot ls command gave some correct
and some really messed up filenames. I then deleted the clone and copied
On 28 July 2011 11:41, ad...@prnet.org wrote:
Hi,
I wanted to experiment a bit with pxeboot. Therefore I created a zfs clone
of a jail filesystem. The clone was shared as via nfs. Pxeboot complained
that it can't load the kernel. The pxeboot ls command gave some correct
and some really
Hi,
yes, I know, but it would be interesing to know if there is a general
problem with zfs clones shared over nfs or if it is pxeboot related.
Bye,
David Arendt
On 07/28/11 13:10, krad wrote:
On 28 July 2011 11:41,ad...@prnet.org wrote:
Hi,
I wanted to experiment a bit with pxeboot
Hi all!
I'm new in these parts, but not new to *nix. I'm trying to upgrade a
system with FreeBSD 5.4 to 7.2.
I've gotten the pxeboot to work, but somehow the network interface isn't
seen by the installer.
loader.rc:
===
include /boot/loader.4th
include /boot/beastie.4th
\ Reads
a
system with FreeBSD 5.4 to 7.2.
I've gotten the pxeboot to work, but somehow the network interface isn't
seen by the installer.
loader.rc:
===
include /boot/loader.4th
include /boot/beastie.4th
\ Reads and processes loader.conf variables
start
load /boot/kernel/kernel
load -t
put it elsewhere, but it
would mean flying 5 hours to do it. Rather just do an upgrade.
On 6/18/09, Bruce Ferrell bferr...@baywinds.org wrote:
Hi all!
I'm new in these parts, but not new to *nix. I'm trying to upgrade a
system with FreeBSD 5.4 to 7.2.
I've gotten the pxeboot to work
Bruce Ferrell wrote:
Hi all!
I'm new in these parts, but not new to *nix. I'm trying to upgrade a
system with FreeBSD 5.4 to 7.2.
I've gotten the pxeboot to work, but somehow the network interface isn't
seen by the installer.
loader.rc:
===
include /boot/loader.4th
include /boot
the pxeboot to work, but somehow the network interface isn't
seen by the installer.
loader.rc:
===
include /boot/loader.4th
include /boot/beastie.4th
\ Reads and processes loader.conf variables
start
load /boot/kernel/kernel
load -t mfs_root /boot/mfsroot
set vfs.root.mountfrom=ufs:/dev
Wojciech Puchar wrote:
I couldn't find the hostname sent by dhcp, but found a way to find the
ip address.
just use hostname command.
I did, but the answer is empty (remember this is before /etc/rc is run).
Where is kept the data received by dhcp_client during pxe boot ?
The only problem i
add second echo to /var/log/messages ;)
Hope not to forget one ;-)
But is there a system call or configuration to do that automatically ? I can
see some echo in /etc/rc without any , and their result seems to go to
/var/messages.
I wish to learn to do clean scripting :-)
actually i
Hello,
Wojciech Puchar wrote:
i already did such things but with NetBSD 1.5 for my Xterminal distro.
it's simple:
mount / readonly, put everything here.
in /etc put /etc/rc consisting only
#!/bin/sh
exec /systemrc
in /systemrc put something like that:
#!/bin/sh
echo -n Mounting workstation
Thank you very much, it is now running well after some hardware adventure.
I couldn't find the hostname sent by dhcp, but found a way to find the ip
address.
just use hostname command.
The only problem i have is that the echo done and other standard outputs
are not visible in
On 12/16/08, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote:
it's simple:
More simple when you tell it ;-) Thanks a lot, i will try it tonight !
it doesn't have chance - must work :)
I wish it's helpful, doing this doesn't just save space but saves time -
you have to upgrade
Wojciech Puchar wrote:
mount_unionfs
but i don't know how stable it is.
Thanks to fill my dreams :-) The dream is close, but still a dream :-(
http://www.freebsd.org/cgi/man.cgi?query=mount_unionfssektion=8apropos=0manpath=FreeBSD+7.0-RELEASE
BUGS
THIS FILE SYSTEM TYPE IS NOT YET FULLY
on NFS server.
Lot of root directories can be shared and mounted in fstab, after booting
process : /usr, /home...
In current solution, the minimum root directories i had to keep for managing
to boot are :
bin libexec sbin boot etc lib
i already did such things but with NetBSD 1.5 for my
Hi,
I'm working on a project to have many diskless clients PXEbooting on 1
nfs server.
This works now, but i would like to have a more efficient use of disk
space on NFS server.
Lot of root directories can be shared and mounted in fstab, after
booting process : /usr, /home...
In current
it's simple:
More simple when you tell it ;-) Thanks a lot, i will try it tonight !
it doesn't have chance - must work :)
I wish it's helpful, doing this doesn't just save space but saves time -
you have to upgrade software once.
So preserving consistency, which is the most important
Wojciech Puchar wrote:
i already did such things but with NetBSD 1.5 for my Xterminal distro.
it's simple:
More simple when you tell it ;-) Thanks a lot, i will try it tonight !
I wish it's helpful, doing this doesn't just save space but saves time -
you have to upgrade software once.
So
Paul B. Mahol wrote:
On 12/16/08, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote:
When you want to change something, you add a rw TransparentLayer :
mount -tl yournfsserver:/StationYchanges/etc /etc
So that changed or added files are only stored in this rw partition, thus
very small
MOUNT_NULLFS(8) doc is very detailled, but i can't find how to use it for my
problem : being able to go from common shared configuration to specific
you can't - nullfs doesn't do this.
use symlinks
/etc containing tons of links to /sharedetc and few files instead of
symlink - for those
On Tue, 2008-12-16 at 15:02 +0100, Bernard Dugas wrote:
Wojciech Puchar wrote:
i already did such things but with NetBSD 1.5 for my Xterminal distro.
it's simple:
More simple when you tell it ;-) Thanks a lot, i will try it tonight !
I wish it's helpful, doing this doesn't just save
On 12/16/08, Bernard Dugas bern...@dugas-family.org wrote:
Paul B. Mahol wrote:
On 12/16/08, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote:
When you want to change something, you add a rw TransparentLayer :
mount -tl yournfsserver:/StationYchanges/etc /etc
So that changed or added
Paul B. Mahol wrote:
Well, I tested unionfs on CURRENT and it did not crashed on me. Feel
free to test it on 7 STABLE and report results to developers.
Thanks for the feed-back, i will no more be afraid to test :-)
I will tell you later,
Best regards,
--
Bernard DUGAS Mobile +33 615 333 770
On 30/07/2008, David Collins [EMAIL PROTECTED] wrote:
I have been trying to get pxeboot to work, so far with no luck. I have
a dhcp/tftp server set up and I am able to push pxeboot across the
network, so I assume that is all ok. NFS is also setup, at least I was
getting nfs errors that I don't
Hi,
Thanks both for your replies. I think the top of that article applies
to me, in that I am trying to do something that I don't fully
understand!
I am fairly confident that I have the DHCP and TFTP setup correctly in
as much as I get pxeboot on the booted machine (and I have gotten it
working
to get pxeboot to work, so far with no luck. I have
a dhcp/tftp server set up and I am able to push pxeboot across the
network, so I assume that is all ok. NFS is also setup, at least I was
getting nfs errors that I don't have anymore. I copied the contents of
the 7.0 cd into the my tftpboot folder
and booting over pxe/tftp when I wanted to
reinstall. I started looking at the automated install, but it seemed
very complex. I have been looking at the freeBSD option and it seems
that the automated intall is very simple (at least from a user point
of view).
I have been trying to get pxeboot to work
/kernel
cheers,
Ruben
On Sat, May 10, 2008 at 12:12:05AM -0700, mohammad khatibi typed:
Hi, I`m new to freebsd.and?I`m using freebsd 7.0?
I want to load my diskless systems through pxeboot in the network so?follow
the instruction that mentioned in the mail about 2 weeks ago
http
Hi, I`m new to freebsd.and I`m using freebsd 7.0
I want to load my diskless systems through pxeboot in the network so follow the
instruction that mentioned in the mail about 2 weeks ago
http://www.ultradesic.com/?section=144
instruction as follow:
1.compiling pxeboot and loader using
On Thu Feb 7 19:00:11 UTC 2008, Rek Jed rekjed at gmail.com wrote:
Subject was: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
Hey,
I've been building FreeBSD jumpstart infrastructure and it mostly
works. I'm using tftp to boot off the network in to scripted
sysinstall. I compiled
-address 192.168.16.39;
filename pxeboot;
option root-path 192.168.16.5:/export/images/00A0DDEF5B7E/freebsd7_x64;
option host-name testclient1;
-- when we attempt to assign a FreeBSD client with an IP address
within the 192.168.17.x --- it is unable to mount its NFSroot export:
host
is ignorant of which version of FreeBSD you use, it
will just load whichever kernel you throw at it. I have a loader I used
for 6.1, http://www.locolomo.org/pub/pxeboot/jumpstart.tgz
Hope this helps. If you find any errors or things that have changed
since I worked with this, let me know and I
Erik Norgaard wrote:
Second, the loader is ignorant of which version of FreeBSD you use, it
will just load whichever kernel you throw at it. I have a loader I used
for 6.1, http://www.locolomo.org/pub/pxeboot/jumpstart.tgz
Sorry, wrong. This is not a pxeloader. Gosh it's long time since I
Rek Jed [EMAIL PROTECTED] writes:
I've been building FreeBSD jumpstart infrastructure and it mostly
works. I'm using tftp to boot off the network in to scripted
sysinstall. I compiled the boot loader with tftp support but every
time I boot it will first try nfs, then timeout after around
build loader files so that I can boot
from tftp instead of nfs:
boot0
boot1
boot2
loader.conf
loader.rc
mbr
pxeboot
Then I mount the stock mfsroot and copy my install.cfg over to script
sysinstall. I've actually got a script that I can use to easily update
install.cfg when needed.
The idea
for nfs to timeout?
This is how I build the boot loader:
cd /usr/src/sys/boot
sudo make clean
sudo make LOADER_TFTP_SUPPORT=YES
sudo cp i386/pxeldr/pxeboot /jumpstart/tftpd/boot/pxeboot.0
sudo cp i386/boot0/boot0 /jumpstart/tftpd/boot/
sudo cp i386/boot2/boot1 /jumpstart/tftpd/boot/
sudo cp i386
] says to compile with:
make -DLOADER_TFTP_SUPPORT=YES
I'm not sure if it makes a difference. Anyhow, the boot loader source
looks like it can't cope with both TFTP and NFS at the same time, so
there might be a bug in there after all.
Erik
[1] http://www.locolomo.org/pub/pxeboot/index.html
nfs) and finally boot from tftp. Is there any way that I
can make it boot from tftp straight away rather than wait for nfs to
timeout?
This is how I build the boot loader:
cd /usr/src/sys/boot
sudo make clean
sudo make LOADER_TFTP_SUPPORT=YES
sudo cp i386/pxeldr/pxeboot /jumpstart/tftpd/boot
Zinevich Denis wrote:
It does not work. I`ve tried. But as I found in forums and mailing lists
it randomly helps sometimes.
Please don't top-post. I have a comment in
src/sys/boot/i386/loader/conf.c v1.26 (RELENG_7) saying:
#if defined(LOADER_NFS_SUPPORT) defined(LOADER_TFTP_SUPPORT)
I tried with LOADER_TFTP_SUPPORT and LOADER_NFS_SUPPORT both enabled.
Also I tried with nfs disabled and tftp enabled. All was made under 6.2
stable, i386 arch.
Only once i`ve got it working without timeout, but I could not repeat this.
I`ll be back to this question in about one or two month
(it
cannot find nfs) and finally boot from tftp. Is there any way that I
can make it boot from tftp straight away rather than wait for nfs to
timeout?
This is how I build the boot loader:
cd /usr/src/sys/boot
sudo make clean
sudo make LOADER_TFTP_SUPPORT=YES
sudo cp i386/pxeldr/pxeboot
that /usr/obj was empty.
# cd /usr/src/sys/boot
# make -DLOADER_TFTP_SUPPORT=YES
Originally I was doing this on 6.2. I tried it again on a freshly
installed 6.3-RELEASE just now. I made sure /usr/obj was empty and
build pxeboot using the above method, then copied it over to my
jumpstart server
-DLOADER_TFTP_SUPPORT=YES
I'm not sure if it makes a difference. Anyhow, the boot loader source
looks like it can't cope with both TFTP and NFS at the same time, so
there might be a bug in there after all.
Erik
[1] http://www.locolomo.org/pub/pxeboot/index.html
I tried building it on 7.0-PRERELEASE and it builds fine for me.
Haven't tested if it works yet, but will do in a moment.
I can confirm that the same thing happens on 7.
___
freebsd-questions@freebsd.org mailing list
Rek Jed skrev:
I've been playing with thinbsd (http://www.thinbsd.org/) a while back.
It also boots from tftp without nfs and their boot loader works fine
(boots straight away). Latest thinbsd is based on 5.4 so maybe it broke
in 6.x? For a workaround I used pxeboot from thinbsd with my 6.3
Hi all,
I can't emphasise enough how useful running a TCPDUMP on the server
in question is to find out what subtle thing it is that I missed.
Generally speaking a quick-crash like that is a file not being found like
the modules directory or something silly like that. If you dump the NFS
and a snapshot of it is here:
http://www.lahaye.dds.nl/pxeboot/crash.jpg
The whole boot process in plain text goes as
follows:
--
Attempting Boot From Intel(R) Boot Agent Version
3.0.05 (PnP Device)
Initializing Intel(R) Boot Agent Version
/pxeboot/crash.jpg
The whole boot process in plain text goes as
follows:
--
Attempting Boot From Intel(R) Boot Agent Version
3.0.05 (PnP Device)
Initializing Intel(R) Boot Agent Version 3.0.05
PXE 2.0 Build 078 (WfM 2.0), RPL V2.73
Intel(R) Boot Agent
On Sun, 11 Feb 2007 17:22:22 -0800 (PST) Rob wrote:
I have a FreeBSD 6.1 PC as the server to a PXE boot
of another Compaq Deskpro EN PC.
The Compaq PC has the option of a Network Service
Boot with the F12-key during BIOS boot up. On the
server, tftpd, bootpd and dhcpd are all working well.
Rob wrote:
Is it OK to have a double kernel read at the last
two lines?
Any idea what's wrong here or what I could do to
further test what the actual problem is?
Argh. I had this same problem as recently as October, but I can't
remember exactly what caused this. When I went back and re-did
is rotating for a very tiny
while after which the system kind of implodes,
blanks the screen and reboots from BIOS.
Apparently something goes very, very wrong
when loading the text part of the kernel.
On the server, I've checked the /var/log/xferlog,
which has entries like this:
read request for //pxeboot
I'm PXE booting systems using the dhcprelay feature on a PIX 525 running
7.1(2). The TFTP process of retrieval of /tftoboot/pxeboot works fine,
however once loaded NFS mount requests to the server fail per the
following messages. In my config, all layer 4-7 packet inspection
features
Erik Nørgaard wrote:
John Pettitt wrote:
Help!
I'm trying to set up a machine to boot using pxe and have run into an
odd problem.
The box (a Soekris 4510) load pxeboot via TFTP prints a few lines of
text then reboots - the last text I see is:
Building the boot loader arguments
John Pettitt wrote:
It's fetching it - I just grabbed pxeboot from an iso image ant that one
gets a lot further so I suspect something in my build environment is not
right for the soekris box. I'm still investigating.
There is a problem building pxeboot if you have /usr/obj present
Help!
I'm trying to set up a machine to boot using pxe and have run into an
odd problem.
The box (a Soekris 4510) load pxeboot via TFTP prints a few lines of
text then reboots - the last text I see is:
Building the boot loader arguments
Relocating the loader and the BTX
Starting the BTX
John Pettitt wrote:
Help!
I'm trying to set up a machine to boot using pxe and have run into an
odd problem.
The box (a Soekris 4510) load pxeboot via TFTP prints a few lines of
text then reboots - the last text I see is:
Building the boot loader arguments
Relocating the loader
Hi All,
I've been messing about with FreeBSD 6.1-Beta#4 recently, and I'm trying to
get a server setup, so that I can pxeboot and install FreeBSD on some other
servers...
I've gotten dhcpd, tftp, pxeboot et'al to work - and, indeed the client
machine dhcp's, pxeboots - and dumps itself
--On 07 April 2006 11:40 +0100 Karl Pielorz [EMAIL PROTECTED] wrote:
What do I need to do, to turn this 'booting FreeBSD from pxeboot' into
something that will dump me into sysinstall, like booting from the CD rom?
I've searched the net - but the only stuff I've found is either for much
floppy images etc).
I have downloaded the i386 bootonly iso and I have followed portions
of several guides which has got me as far as tftp serving the pxeboot.
I assume the dhcp and tftp parts are working ok as the laptop gets
hold of pxeboot fine but then fails to load the kernel.
I have tried nfs
should be fine.
I have downloaded the i386 bootonly iso and I have followed portions
of several guides which has got me as far as tftp serving the pxeboot.
I assume the dhcp and tftp parts are working ok as the laptop gets
hold of pxeboot fine but then fails to load the kernel.
pxeboot can
On 11 Feb 2006, at 04:30, Christopher Cowart wrote:
On a not-a-show-stopper note, is there any way to get around
specifying
the hostname and/or net device? I'd rather not specify the hostname so
that I can have one generic script for many machines. Further, what if
a some other machine has a
Hello-
I'm working on a project to netboot servers and perform a custom
installation of FreeBSD. I have pxeboot working with tftp, providing an
mfs image over the network.
sysinstall runs as init and attempts to follow my install.cfg. However,
when running my mediaSetFTP command, sysinstall
Hi,
Have you had a look in /boot/device.hints?
hint.acpi.0.disabled=1
I at the moment maintain 2 diskless images, the one for older hardware has
the above setting to disable acpi(machine would hang with it enabled). I
believe setting it to 0 or commenting it out could help you.
A.
Hey-
Hey-
I've been working on a project to automate FreeBSD installations over
the network, using PXE boot capabilities. I've been following the
howtos, as documented starting here:
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/index.html
and
http://www.daemonsecurity.com/pxe/jumpstart.html
have setup pxeboot, and if I am far enough along that when I
boot off the network, it tftp's the files it needs, boots through menus,
loads the generic kernel, mounts an nfs root, then errors. The errors
are exec /sbin/init: error 70. One error for each attempt at an init
file. Then it gives
installation without
fail. I have setup pxeboot, and if I am far enough along that when I
boot off the network, it tftp's the files it needs, boots through menus,
loads the generic kernel, mounts an nfs root, then errors. The errors
are exec /sbin/init: error 70. One error for each attempt
, I can do the nfs
installation without fail. I have setup pxeboot, and if I am far
enough along that when I boot off the network, it tftp's the files it
needs, boots through menus, loads the generic kernel, mounts an nfs
root, then errors. The errors are exec /sbin/init: error 70. One
error
Netboot and Installing FreeBSD over em0 GigE link
I am having an issue with pxeboot/BTX loader mounting/contacting a
TFTP server or NFS server that is hosted on machine with an Intel
GigE em0 ethernet card.
pxeboot comes over (via 82540EM bios), loader comes over, but the
load says
are the communication between the rom pxe and the dhcp
server. The last 3 lines are the communication between the downloaded
pxeboot and the dhcp server. The downloaded pxeboot does not seem to retain
the ip address offered by DHCP. Any don't know where it got 192.168.102.110
(192.168.102.1) from.
Has
202.54.1.30, 202.54.1.18;
option domain-name xyz.com;
default-lease-time 2592000;
max-lease-time 2592000;
next-server 10.0.0.10;
server-name xyz.com;
server-identifier 10.0.0.10;
option root-path /usr/local/exports/freebsd5.4;
filename boot/pxeboot;
}
/etc/exports
/usr/local
On Mon, May 23, 2005 at 04:52:18PM +, Sunil Sunder Raj wrote:
Hi,
Was trying to install freebsd 5.3 via pxeboot. The Dhcp server leases the
Ip address, the tftp server is located fine and the pxeboot file gets
downloaded at the client end. But this pxeboot is not getting the proper
Hi,
Was trying to install freebsd 5.3 via pxeboot. The Dhcp server leases the Ip
address, the tftp server is located fine and the pxeboot file gets
downloaded at the client end. But this pxeboot is not getting the proper
server path and gateway ip.
It is always falling to the default
Sunil Sunder Raj wrote:
Hi,
Was trying to install freebsd 5.3 via pxeboot. The Dhcp server leases
the Ip address, the tftp server is located fine and the pxeboot file
gets downloaded at the client end. But this pxeboot is not getting the
proper server path and gateway ip.
It is always
Error in the memory file system caused the problem.
Cheers, Erik
--
Ph: +34.666334818 web: www.locolomo.org
S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt
Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9
Fingerprint:
Hi,
Sorry - I have no more descriptive subject because this is really strange:
I have set up a server to serve clients booting with pxeboot and
fetching kernel and a memory disk root file system with tftp. So far so
good. What is strange is this:
1) If the local harddrive (which contains an old
Hi,
I have set up a server (dhcp/tftp/ftp, no nfs configured) as a jumpstart
server for pxeboot and compiled kernel with -DLOADER_TFTP_SUPPORT=YES.
The client machine is a VIA EPIA CL1000 with a 60GB hdd with a FreeBSD
4.9, I want to reinstall to get 5.3.
Kernel is compiled with option BOOTP
Erik Norgaard wrote:
I have set up a server (dhcp/tftp/ftp, no nfs configured) as a jumpstart
server for pxeboot and compiled kernel with -DLOADER_TFTP_SUPPORT=YES.
The client machine is a VIA EPIA CL1000 with a 60GB hdd with a FreeBSD
4.9, I want to reinstall to get 5.3.
Kernel is compiled
supports pxeboot so I wanted to use this with dhcp/tftp/ftp to
reinstall the system as I have no spare cd drive.
I have succesfully set up the server for dhcp, tftp and ftp. The VIA
machine correctly loads the pxeboot file, fetches a memory filesystem
and mounts it as root. All on vr0
Hi all,
Am having trouble with pxeboot on freebsd 5.1. Am following procedure
at http://www.tnpi.biz/computing/freebsd/pxe-netboot.shtml (relevant bit
pasted at bottom). This procedure states to create an empty 25Mb file using
dd, make a fs out of it (disklabel/newfs/mdconfig), then rsync
Hi
I have used pxeboot to load freebsd 5.2.1 through tftp. It seems as the tftp
client in pxeboot fails to send an data acknowledge after the last datapacket
in each tftp transfer. (not very nice for server which resends last
datapacket several times)
BTW: Does anybody know a way to specify
a dhcp address.. It appears to tftp download the pxeboot file (which
is a big ole linux initrd created with http://pxes.sourceforge.net)
then after a short while it bombs with
tftp: too many packages
exiting intel boot agent
I searched and it seems that there is a 512K limitation for booting
91 matches
Mail list logo
