be similar to "rawboot" that phk
did using the old aout bootblocks).
--
Robert Nordier
[EMAIL PROTECTED] // Le monde est plein de fous, et qui n'en veut pas voir
[EMAIL PROTECTED] // Doit se tenir tout seul, et casser son miroir.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &q
I wouldn't personally be in favour of adding
this to the standard boot1.
--
Robert Nordier
[EMAIL PROTECTED] // Le monde est plein de fous, et qui n'en veut pas voir
[EMAIL PROTECTED] // Doit se tenir tout seul, et casser son miroir.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
the author/maintainer should have any special weight.
--
Robert Nordier
[EMAIL PROTECTED] // Le monde est plein de fous, et qui n'en veut pas voir
[EMAIL PROTECTED] // Doit se tenir tout seul, et casser son miroir.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hacke
. I'll probably sort it out in the next day
or two, unless someone else gets there first.
--
Robert Nordier
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
you mentioned somewhere you're generating ELF (not a.out);
if so, your compiler is not doing the right thing for external
symbols. What appeared in FreeBSD a.out libraries as "_printf" is
plain "printf" in ELF. There is no "_printf" symbol in the standard
FreeBSD libc
er not
to make silly mistakes is a different matter altogether, of course.
--
Robert Nordier
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ording all the information needed to
control a stream [7.9.1]
and elsewhere goes on to describe a stream as, for example
an ordered sequence of characters [7.9.2]
so I think it's fairly clear that a stream is not what (FILE *)
points at.
I doubt that the SUS would intentionally d
old C code I'd tend to expect it to work. C is not a
language in which you go out of your way to prevent people making
mistakes.
--
Robert Nordier
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
in %eax, depending on whether an error has
occurred. Our function maintains errno, since this is how things
are done in the C library.
If you need more info, e-mail me directly.
--
Robert Nordier
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED
David O'Brien wrote:
On Fri, Oct 27, 2000 at 01:10:56PM +0200, Robert Nordier wrote:
Just doing the disklabel -w -r followed by the disklabel -B is creating
a dangerously dedicated disk,
Actually this is a "fully dedicated" disk. (made to look like a 50MB or
so disk to M
.
Don't sysinstall work in a script mode? I've never used it, but I
thought it did.
--
Robert Nordier
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Matt Dillon wrote:
:
: Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto'
:
:If you added "auto" after the "disklabel -B", that may be your problem.
:
:--
:Robert Nordier
type-o. No auto for the -B still blows up the dos partition
Matt Dillon wrote:
Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto'
If you added "auto" after the "disklabel -B", that may be your problem.
--
Robert Nordier
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTE
on the first drive? TIA
We don't use BootEasy any longer, but something called boot0 ... which
is probably why you couldn't find anything in the archives.
Something like
boot0cfg -Bv $DRIVE
should work, though see the man page.
--
Robert Nordier
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe
. So most modern BIOSes
do translation by default, representing 6256 cyls x 16 heads as
(6256/8 x 16*8 =) 782 cyls x 128 heads. The off-by-one difference
(782 vs. 781 given as BIOS geometry for drive 0) is due to reserving
the last cylinder for diagnostics, etc., another BIOS quirk.
--
Robert
as there's been little interest till recently.
It should be fairly easy to hack boot2 to get this working in your
particular case, if you have the time and inclination.
--
Robert Nordier
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fr
1024.
So it isn't completely straightforward, but you can make use of the
whole disk.
I assume that if I set the gemoetry in fdisk to be the BIOS figures,
that I will lose the other half of the disk?
Use 2096/255/63 in sysinstall.
--
Robert Nordier
To Unsubscribe: send mail to [EMAIL PROTECTED]
wit
.
The best way to determine BIOS geometry in FreeBSD is to boot -v
(but it should be from the old boot: prompt, not from loader(8)
in 3.2R) and then check using dmesg(8) for BIOS Geometries
information.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd
, but you can make use of the
whole disk.
I assume that if I set the gemoetry in fdisk to be the BIOS figures,
that I will lose the other half of the disk?
Use 2096/255/63 in sysinstall.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers
don't know if this will work with booteasy the boot manager that comes
with FreeBSD by default, but there is a nice boot manager called
OS Select (tools/os-bs.exe in the FreeBSD distribution I think).
Both booteasy and boot0 (distributed in place of booteasy from 3.1R)
work as well.
--
Robe
off to avoid?
I think support for extended partitions is inevitable (it's now
the RedHat default), whether it really is a good idea or not.
Technically, it violates the IBM specification that deals with
fdisk partitions, though I'm not sure that matters very much.
It will break some older OS
tem set up with 2.0R, 2.1R, 2.2R and 3-current (as was) in
separate slices, when testing the new boot code.
Some people do prefer the multiple systems per slice approach,
though, which is all that used to be supported. So either can
be made to work.
--
Robert Nordier
To Unsubscribe: send mail
if this will work with booteasy the boot manager that comes
with FreeBSD by default, but there is a nice boot manager called
OS Select (tools/os-bs.exe in the FreeBSD distribution I think).
Both booteasy and boot0 (distributed in place of booteasy from 3.1R)
work as well.
--
Robert Nordier
(it's now
the RedHat default), whether it really is a good idea or not.
Technically, it violates the IBM specification that deals with
fdisk partitions, though I'm not sure that matters very much.
It will break some older OS/2 device drivers, for instance,
though.
--
Robert Nordier
, 2.2R and 3-current (as was) in
separate slices, when testing the new boot code.
Some people do prefer the multiple systems per slice approach,
though, which is all that used to be supported. So either can
be made to work.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
ebsd.org/pub/FreeBSD/tools/srcs/bteasy/
is there a newer version? this code is supposed to be compiled with
TASM/Borland C right? is there source that
can be compiled with gnu tools?
See src/sys/boot/i386/boot0 in the FreeBSD source tree.
--
Robert Nordier
To Unsubscribe: send mail
/tools/srcs/bteasy/
is there a newer version? this code is supposed to be compiled with
TASM/Borland C right? is there source that
can be compiled with gnu tools?
See src/sys/boot/i386/boot0 in the FreeBSD source tree.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
?
This is legacy code which is being kept around until loader(8) supports
equivalent functionality. For now, I suggest you use "etherboot" in
the ports collection.
--
Robert Nordier
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
this ("less
than nitems only if a read error or end-of-file is encountered"),
but mostly the present behavior just conflicts with sense and
practice.
--
Robert Nordier
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
making use of kernel configuration conventions,
where the semantics may end up being just slightly different, is
probably a less useful idea than it seems.
--
Robert Nordier
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
?
This is legacy code which is being kept around until loader(8) supports
equivalent functionality. For now, I suggest you use etherboot in
the ports collection.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
this (less
than nitems only if a read error or end-of-file is encountered),
but mostly the present behavior just conflicts with sense and
practice.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
of kernel configuration conventions,
where the semantics may end up being just slightly different, is
probably a less useful idea than it seems.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
; version -- are up to
supporting a grep without much further debugging. I don't recall
many of the problems I found when I last looked at these, though
here are two, after 5 minutes playing:
echo xx | grep '\(x\{1,2\}\)\1'
echo x | grep '[--x]'
--
Robert Nordier
To Unsubscribe: send mai
much further debugging. I don't recall
many of the problems I found when I last looked at these, though
here are two, after 5 minutes playing:
echo xx | grep '\(x\{1,2\}\)\1'
echo x | grep '[--x]'
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe
functionality, and
the framework is already in place for this.
I suggest you use etherboot in the ports collection, at least until
the loader support is completed.
--
Robert Nordier
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
functionality, and
the framework is already in place for this.
I suggest you use etherboot in the ports collection, at least until
the loader support is completed.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
The standard boot partition selection softwre also works fine
booting windoze OS's from other disks. All you need to do is set the
disk
id in the DOS MBR to the correct number, 0x81 for your second disk.
That's
the only thing that MS doesn't do correctly whe installing
to be ignored. (Needs boot0cfg.c v1.5
as well, though.)
RN
At 06:58 PM 6/19/99 +0200, Robert Nordier wrote:
Dennis wrote:
F1: FreeBSD
F2: LINUX
F3: FreeBSD
F3 is a non-bootable file system...is there a way to get the boot manager
to only display F1 and F2?
At the moment, no. Though
in
Makefile enables slices 1 and 2; use B0FLAGS=0xf to enable all four
slices.)
If worthwhile, boot0cfg(8) can later be modified to set/unset the
flags, rather than using a build option.
Note that the patch is against boot0.s rev 1.9 committed yesterday.
--
Robert Nordier
--- Makefile.orig
. (I see that at the FreeBSD Mall, they're
offering Partition Magic and System Commander with FreeBSD.)
To ignore a partition by type, see the following patch as an example
(we ignore type 0x42).
--
Robert Nordier
--- boot0.s.origSat Jun 19 19:50:23 1999
+++ boot0.s Sat Jun 19 19:50
from those.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
have booted Linux with the freebsd boot
manager.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
hard drive 0, which is all IBM/Microsoft
officially support. It'd probably make life a bit easier to allow
booting from any hard drive.
--
Robert Nordier
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
44 matches
Mail list logo
