): undefined reference to `nfs_root_node'
You need to build and install libstand first.
Robert Nordier
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Julian Elischer wrote:
Robert Nordier wrote:
Julian Elischer wrote:
with newly CVSup'd sources (I cannot compile the bootblocks..)
(also with everything checked out to PRE_SMPNG)
It get's the following error:
/usr/obj/usr/src/sys/boot/i386/loader/../libi386/libi386
cases uses a small number
of sectors per track, which may push part of the 'a' partition
beyond the 1023 CHS limit.
Anyway, if some debugging code would help here, let me know.
--
Robert Nordier
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
handy.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
. And FBSDBOOT.EXE has *never* worked reliably in a
VM86 context.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
means invalid argument. The most likely cause is
that your / filesystem spans cylinder 1023 and /boot/loader is
inaccessible for this reason.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
calling convention (the
called functions pop argument from the stack), so ability to use
some arbitrary ISO compiler can't be guaranteed on principle, and
is fairly unlikely in practice.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body
-externs
-Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -c
/usr/src/sys/boot/i386/boot2/boot2.c
Revision 1.12 of the Makefile contains option changes for egcs. If you
want to use gcc, use rev 1.11 of the Makefile. (Jeez, guys!)
--
Robert Nordier
To Unsubscribe: send mail
.)
The 135168-byte loader works fine here, and I can't think of any
reason it should cause problems for you. (It's to be expected that
a more recent compiler will emit different object code, so size
comparisons are apples and oranges.)
--
Robert Nordier
To Unsubscribe: send mail to majord
to the kernel.
While not an optimal solution, this does have the virtue of adding
the ability to boot from any device not specifically provided for,
and without requiring customization of the bootblocks (or any more
work on the kernel than is presently required to add a device
driver).
--
Robert Nordier
Bob Willcox wrote:
I have an LS-120 and I'd be happy to test the new boot code with it.
Bob
Thanks very much. I'll contact you and Andrzej when the changes
are made.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body
# doesn't
relate to what was booted from, and may not even describe the
underlying technology correctly.
As the bootcode is now this wont work. If its as simple as me adding
the pair 30 ad somewhere, I'm satisfied, if not, I'm dissapointed :)
--
Robert Nordier
To Unsubscribe: send mail
with good potential for failure.
In contrast, the kernel configuration route requires commenting
or uncommenting a single statement.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
take a look at both approaches, probably later today,
and send you some diffs, hopefully relating to each way of doing
things.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Andrzej Bialecki wrote:
On Wed, 17 Mar 1999, Robert Nordier wrote:
Incidentally, while I'm in there and thinking about it, I'd quite
like to fix the boot code to boot from LS-120 drives at the same
time. So if anyone has one of these, and wouldn't mind spending
some time running a few
, though.
Also, make sure you don't have any root_disk_unit or num_ide_disks
set.
A num_ide_disks setting is used only where the major# indicates a
SCSI device, so it wouldn't affect things.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current
. :-)
If the problem is the bootblocks, why not send a message to Robert
Nordier, or if it's loader, to Mike Smith or Daniel Sobral? And
say, This is what I want to do, what are we going to do about it?
or something similar?
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
all the stuff that you would
normally type at the config prompt when you Boot: -c.
Rather
load -t userconfig_script /kernel.config
In particular, not /boot.config which is a file with a different
purpose used by the bootblocks (boot stages 1 2).
--
Robert Nordier
To Unsubscribe: send
) on
higher-numbered drives in order to boot from them.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
mirror sites, so best fetch
it as above.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
to Robert
Nordier (in that order 8).
No need to talk to me: I'll talk to you instead. :)
The new boot manager remembers last slice selected rather than
last menu option selected on each drive.
I think I prefer this behavior myself, but I'll change it for
compatibility with booteasy.
--
Robert
a few messages back).
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
(in the Makefile) as having
bit 6 (0x40) set. Though a utility for installing and configuring
the boot manager from the command line is in progress.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Ugo Paternostro wrote:
On 30-Jan-99 Robert Nordier wrote about Re: Reading a text file with BTX:
Daniel C. Sobral wrote:
Robert Nordier wrote:
Daniel C. Sobral wrote:
Y'know, in my computer that F5 is Drive 0, and the system will not
boot unless I select it first. Selecting
of the howto flags, on to either the kernel or /boot/loader.
So -D is preserved only as a backward-compatibility option (and
therefore applies only to stage two of the bootstrap), and /boot/loader
knows nothing about it.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
goes. But they don't pass RB_DUAL, as one
:of the howto flags, on to either the kernel or /boot/loader.
:
:So -D is preserved only as a backward-compatibility option (and
:therefore applies only to stage two of the bootstrap), and /boot/loader
:knows nothing about it.
:
:--
:Robert Nordier
Daniel C. Sobral wrote:
Robert Nordier wrote:
The boot manager menu, for example
F1 FreeBSD
F2 UNIX
F5 Drive 1
Default: F1
Y'know, in my computer that F5 is Drive 0, and the system will not
boot unless I select it first. Selecting it, makes the OSes
Daniel C. Sobral wrote:
Robert Nordier wrote:
Daniel C. Sobral wrote:
Y'know, in my computer that F5 is Drive 0, and the system will not
boot unless I select it first. Selecting it, makes the OSes boot and
F5 disappear.
Try the following patch. You can use the utility
dedicated) have a proper mbr.
boot1 and boot2 occupy the boot blocks (the first 8K sectors of a ufs
partition) with the default being the 'a' partition.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
:
| COMPATIBILITY
| The rm utility differs from historical implementations in that
| the -f option only masks attempts to remove non-existent
| files instead of masking a large variety of errors.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe
machine, updating the default boot disk to
the latest boot blocks is also suggested.
A /boot.config like
1:wd(2,a)
would then pass control directly to a non-default copy of /boot/loader.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current
that it has to be killed by BTX, just because of an I/O
error. Bad floppies are common and this is a reproducible bug that
needs fixing.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
the above (or hitting any
key before seeing the /boot/loader prompt, to get the old boot:
prompt instead), is a recommended workaround for any temporary
/boot/loader problems.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body
me a copy of the kernel (or put it up for ftp, if you
prefer), and I'll take a look.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
of thing.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
disklabel -B da0s3
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
-5 weeks seems
fairly promising at the moment.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
: don't know how to make machine/ansi.h. Stop
| *** Error code 2
|
| Stop.
That way, if it's not a known problem, but some form of pilot error,
you may get some useful help anyway.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body
was still using BIOS routines (with hardware handshaking), but this
was changed around late November 1998.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
shows up if you
enter
2:da(0,a)/boot/?
(to get a directory listing of /boot) at the boot: prompt?
Incidentally, do these bootblocks contain the BTX patch I sent you,
or did you find some other way around that problem?
--
Robert Nordier
To Unsubscribe: send mail
Ulf Zimmermann wrote:
On Sun, Jan 17, 1999 at 06:29:30PM +0200, Robert Nordier wrote:
Ulf Zimmermann wrote:
Incidentally, do these bootblocks contain the BTX patch I sent you,
or did you find some other way around that problem?
This are the boot loaders from last night, just after make
Ulf Zimmermann wrote:
On Sun, Jan 17, 1999 at 06:29:30PM +0200, Robert Nordier wrote:
Ulf Zimmermann wrote:
The old bootblocks have a build setting BOOT_HD_BIAS to work
around this problem. The new bootblocks rely on /boot.config.
You can have
2:da(0
/loader program rather
than boot2.
Also, it might be nice if the disklabel(8) man pages explicitely
say that the bootstrap code can be installed on each slice.
(am I wrong ?)
You're right, the bootblocks can be installed on each slice, and
this also needs documenting.
--
Robert Nordier
) is merely an installation
tool for bootstrap stages 1 2, as is install(1) for bootstrap
stage 3. Of course one does not document programs on the man pages
of their installation tools. However this does not mean that one
does not document them (or their installation procedures) at all.
--
Robert
44 matches
Mail list logo
