src-test2/sys/boot/common/interp.c, branch release/8.2.0_cvsFreeBSD source treehttps://cgit-dev.freebsd.org/src-test2/atom?h=release%2F8.2.0_cvs2011-02-16T16:18:46ZCopy releng/8.2 to release/8.2.0 for 8.2-RELEASE.2011-02-16T16:18:46ZKen Smithkensmith@FreeBSD.org2011-02-16T16:18:46Zurn:sha1:dec99dafe5763ba1db6950342aa80a634169c083
Approved by: re (implicit)
This commit was manufactured to restore the state of the 8.2-RELEASE image.
As reported in kern/118222, pxeboot in RELENG7 (and presumably2008-11-20T14:57:09ZLuigi Rizzoluigi@FreeBSD.org2008-11-20T14:57:09Zurn:sha1:ade303f361e674649d7f81cdca10da2af93dec00
above) exhibits some misbehaviours on machines with AMD64 CPUs,
which at least in some cases I have tracked down to a heap overflow.
It is unclear whether it depends on the CPU or on the pxe bios
itself which may use more memory on AMD machines.
Noticeably a pxeboot compiled from 6.x sources works fine on all
machines I have tried so far, while a pxeboot compiled from 7.x
sources does not.
This patch is a first step in reducing the amount of memory used
while processing the configuration files read by the loader at boot
(some of them are quite large, 1700+ lines), and it does so by:
+ moving a buffer to static memory instead of allocating in the heap;
+ skipping empty lines;
+ reducing the amount of memory used for line descriptors;
Unfortunately there are several changes between 6.x and above,
affecting the compiler, the loader code itself, and libstand,
and it is not so straightforward to
These changes fix the behaviour on one motherboard with a
single-core AMD cpu, but are still not enough e.g on an Asus
M2N-VM (with a dual-core CPU).
I need to investigate the problem a bit more before figuring
out what should be committed to RELENG_7
PR: kern/118222
Use __FBSDID().2003-08-25T23:30:41ZDavid E. O'Brienobrien@FreeBSD.org2003-08-25T23:30:41Zurn:sha1:1809be3cd462d071c04e67a2648af4ed71925153
Also some minor style cleanups.
Upper case the FreeBSD loader prompt.2001-11-19T17:30:26ZDavid E. O'Brienobrien@FreeBSD.org2001-11-19T17:30:26Zurn:sha1:03820e7a36494463a59ed6530797fb4910de6241
On OFW based machines, it is just too confusing having the firmware and
OS loader giving the same prompt. This is a nice compromise that 99% of the
users on non-OFW platforms will probably not even notice.
Change NOFORTH comment character from # to \ followed by space,2000-09-10T13:48:51ZDaniel C. Sobraldcs@FreeBSD.org2000-09-10T13:48:51Zurn:sha1:2ae7c98e2901c0772a9e214877c93e948b3b8597
to make things more interchangeable between it and the FORTH case.
Perhaps requiring the space is a bit too much, but...
Nothing in the tree seems to produce loader.rc files with comment
line, at this time.
Bring back the perform() function. However, conditionionalize it on2000-08-04T05:23:41ZJohn Baldwinjhb@FreeBSD.org2000-08-04T05:23:41Zurn:sha1:00dc3782f70347e7951be09ba310966755d43d37
BOOT_FORTH as it is only used if BOOT_FORTH is not defined.
Cleanup warnings. Most of these are signed/unsigned warnings, as well as2000-08-03T09:14:02ZJohn Baldwinjhb@FreeBSD.org2000-08-03T09:14:02Zurn:sha1:4ae4202e705cf6a12aa3cbb49efb153879a6bc2f
some added const's.
Don't call printf with no format string.2000-07-10T06:40:06ZKris Kennawaykris@FreeBSD.org2000-07-10T06:40:06Zurn:sha1:8c8970cf16d4d4ac4e11d7d7ba8b1108fadef92cRemove the setting of sourceid from bf_vm(), as bf_vm() really has2000-06-14T19:37:00ZDaniel C. Sobraldcs@FreeBSD.org2000-06-14T19:37:00Zurn:sha1:18ee60a57616434a5c49b4d75f07f57d63d1db60
no clue.
Set sourceid to 0 when booting, which is the correct setting for stdin.
Set sourceid to an arbitrary fd when include'ing, preserving and restoring
the previous sourceid. This is possibly broken(), as 0 is a valid fd. Maybe
we should +1 to this value.
This fixes the version problem widely reported.
Make the prompt look like on OpenBoot.1999-11-27T21:44:47ZDaniel C. Sobraldcs@FreeBSD.org1999-11-27T21:44:47Zurn:sha1:69c9583604c23883d35fb1a425913b1f4e03f4b0