of it. I'm not sure I'll get all the way, but in
conjunction with some small changes in the loader it *should* make
problems like yours history.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is lon
ory,
> or by hunting all such occurrences of the code ?
I engaged in part of a sweep of this sort with Andrzej a while back,
but he never committed any of the changes. I'm not quite sure why.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\
> Quoth Mike Smith on Wed, 5 May:
> :
> : Insufficient content. Please add more and try again.
>
> Insufficient for what purpose? (Trying to understand what
> additional information you would like...)
In one place (one message), you need:
- what hardware
- what firmware
27;t get crash
> dumps. I should be able to get a null modem cable tomorrow, so I can try a
> serial console and remote gdb.
I wonder if there are problems running the APM requests on an AP?
Daniel, are you running with the most recent MTRR/SMP fixes?
--
\\ Sometimes you're ahead,
o majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's
the pcic module. Don't do that.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@cdrom.com
To Unsubscribe: send mail to majord.
> Won't fbsdboot.exe be able to boot /boot/loader? (maybe I am just naive)
> (or could it be modified to do so with little effort?)
We've had this discussion. No.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.n
d seems to have
> NULL entry for a pentium.
>
> dave adkins
>
>
>
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ some
aren't working on this,
nobody else is. We don't have enough people manning the trenches
because they're all sitting back in the chateau waiting for the
afternoon dispatches. This doesn't work. 8)
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you'
e fact
doesn't help anyone, least of all yourself.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@cdrom.com
To Unsubs
aise Nicolas lately,
so I'm starting to fear that we're going to need a new maintainer.
That bites, given how well things were going.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the
y Packet Filter. Be
> # aware of the legal and administrative consequences of enabling this
> # option. The number of devices determines the maximum number of
> # simultaneous BPF clients programs runnable.
> #pseudo-device bpfilter 4 #Berkeley packet filter
>
>
> # USB
anymore and... that's
> all. ESS still can't be detected. :(
You need to set 'PnP OS' in your BIOS to _off_, and may possibly need
to explicitly enable the device using userconfig.
This is a FAQ, and does not belong on this list.
--
\\ Sometimes you're ahead,
--+---+
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \
sure how we go about making that one tidy.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@cdrom.com
To Unsubscribe: se
>Is there any way I can help in getting the atapi-fd driver to work with
> LS-120's?
Unless it was just recently broken, it works fine (I have one).
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The rac
o stupid as to think that DOS had anything to
do with the loader.
The loader's keyboard interface code uses the BIOS, like it always has.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \
nths (ie. travel to/around the USA), and the third is that you need
to be able to negotiate and sign legal agreements on behalf of your
organisation.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long,
tack
That doesn't help; there is no guarantee that your stack or your
alternate stack have been mapped.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ en
lating to remote
health monitoring are all off.
I'd fire the one here up to be more specific, but it trips the breaker
on this row of offices...
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and
n information, and rc.conf.site can be rdist'ed
around.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@cdrom.com
lesystem itself.
I'm not sold, sorry. This isn't sufficiently automatable, nor does it
remove the room for massive user error that I for one fear greatly.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The rac
> >> I pass "foo" from 1:foo(2s1a)kernel in my version of the old boot blocks.
> >
> >And you determine "foo" how?
>
> I type it into the config file or the command line.
And you submit that this is an acceptable solution?
--
\\ Sometimes y
to entertain any alternate solutions.
> I pass "foo" from 1:foo(2s1a)kernel in my version of the old boot blocks.
And you determine "foo" how?
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is
t of people).
> >
> > Use the "last mounted on" field to find and mount filesystems.
>
> Again, same objections... :-)
Same solutions. Plus we'd be likely to place some metadata somewhere
on a FAT filesystem, so it'd be trivial to put such a field there.
--
om cards? (Any test
> drivers out there for it?)
No.
You might have some success with a commercial bootprom (eg. from
www.incom.de) and a tftp'able boot image.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\
system itself? Just have it read the node entry for /dev/$rootdev
> (or similiar).
This doesn't solve the BIOS : FreeBSD unit numbering problem,
unfortunately, and it would make moving from one driver to another very
difficult (you'd have to override the search).
It's a neat
However, there's another technique which would work quite well, and one
I'm actually moderately enamoured of (modulo it's ability to confuse
the heck out of people).
Use the "last mounted on" field to find and mount filesystems.
--
\\ Sometimes you're ahead,
ented in the CAM framework will make your life easier, not
harder. It's not necessary to write a translation layer at all, if
such a thing offends your sensibilities.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ Th
call it).
The *only* way for this to work is for the kernel to hunt for the
root device, possibly with some helping hints from the loader.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the
; >with "unsubscribe freebsd-current" in the body of the message
> >
>
> --
> Poul-Henning Kamp FreeBSD coreteam member
> p...@freebsd.org "Real hackers run -current on their laptop."
> FreeBSD -- It will take a long time
> It seems Robert Nordier wrote:
> > 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 som
>
> It seems to work fine except it core dumps on exit for some reason.
>
Marcel fixed that one a while back; update your system. 8)
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long,
t;
> >
> >To Unsubscribe: send mail to majord...@freebsd.org
> >with "unsubscribe freebsd-current" in the body of the message
> >
>
> --
> Poul-Henning Kamp FreeBSD coreteam member
> p...@freebsd.org "Real hackers run -curre
'd need to study how KLD currently works, then go back
over the discussions that Peter, Doug, I and others have had about how
we might identify modules within a file, and implement it. I fear that
it will result in binary incompatability (again).
--
\\ Sometimes you're ahead,
> Mike Smith wrote:
> >
> > The only configuration which currently works correctly is to remove the
> > kldload of the pcic module from /etc/rc.pccard and compile everything
> > else statically into the kernel.
> >
> > Every other variation is *broken*
uot;unsubscribe freebsd-current" in the body of the message
>
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@cdrom.com
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
ad the disklabel. If they couldn't read the disklabel, you
wouldn't be mounting the disk in the first place.
Is your disk dedicated in some way?
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, an
> On Sun, 7 Mar 1999, Mike Smith wrote:
>
> #
> # >From the context I've seen, the 'ufs_dirbad' panic is almost certainly
> # due to corrupted disk input.
>
> I definitely can't rule that out as a possibility, but it does make
> it difficult to e
y
> > good reason an application should care whether the drive is ATA or SCSI, as
> > long as the functionality is provided does it matter how?
>
> The boot code might be distressed... :-)
Not as long as the ordering matched the BIOS ordering. The boot code
would love it.
--
was actually wd1 that
> didn't probe and what is now visible as wd1 is what you used to know as
> wd2? If the disks are identical, you have to look carefully at the boot
> messages. If that isn't a POLA violation, what is?
Talk about "bike shelter" material.
--
\\
he few times I've tried to use it, I would get different
> results from the same actions on my part, so I gave up.)
"DOS compatibility" is irrelevant. What is at issue here is _firmware_
compatability.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you&
least its > 4x bigger. 8)
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@cdrom.com
To Unsubscribe: send m
to pack unit numbers; the 'wd' driver was our sole exception (the BIOS
and the SCSI code both pack unit numbers). Since it's now consistent
with everything else, it should stay as-is.
Wiring ATAPI units down is of limited utility, but should probably be
supported for people that li
s with them.
Order the systems with FreeBSD preinstalled from Gateway. 8)
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\
not following the instructions. The PCI device will be
assigned to the 'ed' unit one greater than the highest number shown in
the kernel config file, and this number can be clearly seen when the
system is booting.
Please do not send trivial questions like this to the -current lis
ontext in which you need to
get at the suspended PC.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@cdrom.com
To Unsubscribe: s
bsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself.
rc.nasa.gov
> ---
>
>
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes
me; do we have a utility to reference wmesg strings back
> to the code that sets them, a la TAGS? Would this be useful?
No, and yes respectively.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in
ou
>
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
>
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race i
ly stuck.
> Are there some switches I should try? I assume (without testing) that
> 4-current would also show the same problems as 3-stable. Which is why I
> posted here.
There have actually been some changes in 4.0 which might affect this,
if I understand correctly.
--
\\ Sometimes you&#
infrastructure - on the
Alpha you're just using SRM for the network, wheras on i386 there's
somewhat more work to do. It sounded like another week or so would see
some preliminary results.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind.
of atleast a couple people netbooting ELF kernels, starting to think
> people
> don't care about netbooting anymore.
I'm just waiting for you to finish the job; the loader needs network
support too (there is actually WIP on this, let me know if you need
more information).
--
2 without some help.
For 3.0 and earlier systems, you would use
1:wd(2,a)kernel
at the boot: prompt. For 3.1 and later systems, use:
set root_disk_unit=2
at the loader prompt.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smit
oo. -O3 does not. We'll probably see the newer version
> of compiler before this is fixed.
No, -O2 does not work fine; we've seen reports of it breaking things
before.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.
hard drive while leaving it cabled to the controller).
Yuck. That's extra-bad.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself.
to misapply this name to the loader
proper.
> The prompt isn't OF Forth, I stated that the prompt TAKES Forth; perhaps I
> could have said that better.
You "meant" that the prompt takes Forth, perhaps. 8)
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ some
pt, and the prompt is not written in Forth (yet).
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@cdrom.com
To Unsubscribe: send m
ever get to "BTX", you end up the loader.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@cdrom.com
To Unsubscribe: send ma
ored; it does nothing. You should have
nothing in /boot.config or /boot.help (delete them both). Use the
'help' command in the loader, or read any of the dozens of posts I've
made on this topic to date.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes y
oing it via my printer port sounds cool. Know anything like that?
ppi(4)
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm..
g a modem it should have
one of the "compatibility" fallback IDs as well. You may need to
explicitly enable it if your BIOS is not set for "non PNP OS".
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race
t goes into
/etc/defaults, and the "local changes" stay in /etc. The next big
candidate for this is make.conf, but that will require careful testing
first.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The
> Mike Smith wrote:
> >In a situation like that, you would just tune the dhcp client not to
> >ask for a lease on that interface. You know you've done something
> >silly; there's a mechanism to stop it breaking things. What more could
> >you ask for?
&g
gt; since 3.x-STABLE still has some problems which makes it impossible
> for me to use it on production machines.
What crippiling disability prevents you from adding the driver yourself?
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@sm
rfaces''. So it just happily sits there. IMHO we
> shouldn't try to dhcp configure it. It will just fill up logs as it
> continues to try to get a lease which it can't.
In a situation like that, you would just tune the dhcp client not to
ask for a lease on t
at happens if your lease expires and doesn't get renewed, or gets
> > renewed with a different IP address?
>
> You will get "no route to host" type messages.
Yup. That's just the way it is - I can't imagine what alternative the
original poster thought they co
> > haven't tested.
> >
>
> Cheapbytes.
Buying the Cheapbytes disc doesn't support the project, and there's a
pretty good chance that the DHCP client won't be on the first disk.
Steve; face it, DHCP client functionality is needed by other people.
It won&
ed.
That's not "VERY BAD". Bpf imposes a slight performance, hit, but
that's about all. Don't start whining about the "security issues";
they're so trivial to be beyond worry.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you
There are any number of reasons for going with the ISC client,
including an involved ISC developer that's keen to help it happen.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...
uring stack usage (or simply on how to increase the kernel
stack allocation...).
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \
him for a while now, but I know he had some very
happy beta-testers in the field.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yoursel
image, but the typical cause
of a double fault is running out of kernel stack.
Are you running any custom kernel code?
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
> Mike Smith writes:
> > > Take the following scenario:
> > >
> > > compiled in: module A
> > >
> > > kldstat -v shows module 'A'
> > >
> > > kldload A
> > > damned thing succeeds.
> >
> > That&#
tablished conventions as well as POLA.
> Perhaps the problem is that we are simply naming these things badly.
> Frankly, I would rather get rid of rc.conf.site entirely and just leave
> rc.conf and rc.conf.local -- and have sysinstall mess with rc.conf.local.
That's no be
ed" error message
> can generally be fixed by low-level formatting the disk.
Hmm, mea culpa; I didn't see/register that message. It would, indeed,
indicate that a low-level format was required. Daren, my apologies.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ somet
eating rc.conf.site which is quietly included *after*
everything in rc.conf (so that when someone changes rc.conf, the change
is overridden).
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and
without a preceeding virtual removal?
Just to be clear, I have no objections to that approach, but it's
something that we would want to make very clear if we're going to make
this change.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind.
am_lookup_pass: No such file or directory
> > > cam_lookup_pass: either the pass driver isn't in your kernel
> > > cam_lookup_pass: or da0 doesn't exist
> > > rover#
> >
> > --
> > -- David(obr...@nuxi.com -or- obr...@freebsd.org)
> >
>
ed it via UFS.
> But unfortunately the machine panic'd really fast during filesystem activity.
> My tests on this are 3-4 months old though, I will give it another try.
Definitely, since we cache ACCESS RPC results now.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes
tigate that somewhat.
If you can demonstrate that they work and have the desired effect, you
could make a good case for this. If you have the time, a lot of people
would appreciate the effort.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\
e best solution would be hardwiring the names, but in that case it
> > doesn't matter what are the default names.
>
> Yes. Hardwiring is the only appropriate solution.
Hardwiring is nonappropriate in a non-static environment.
--
\\ Sometimes you're ahead, \\ Mike Smith
emains de1
( ) de0 becomes de1, de1 becomes de0
( ) you discover a new device, de-1
Having a single linear namespace for interfaces would, actually, make
life somewhat easier for the administrator. You can simulate it buy
only buying one type of ethernet card.
--
\\ Sometimes you're ahe
o chain to another disk, that's
definitely preferable...
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@cdrom
x27; stuff enabled, then talk to Robert
Nordier (in that order 8).
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@cdrom.com
ght person, or it's not that easy. I can't see a "right" way of
fixing it short of completely separating "files" and "modules".
Here's another scenario guaranteed to flummox the current code; link A
and B together in a single file, name it after A. Then
Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@cdrom.com
To Unsubscribe: send mail to majord...@freebsd.org
with "unsub
;ve had about four flakes so far).
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@cdrom.com
To Unsubscribe: send mai
ys tries to mount partitions on wd1. Is this a known issue or am I
> doing something wrong?
>
> Thanks in advance!!
>
> -
> Santiago Perez-Cacho
> san...@pcfa.es.eu.org
>
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with
rnelname=kernel
@read -t 5 -p "Enter kernel name [kernel] : " kernelname
@load $kernelname
@include /boot/modules.default
-include /boot/modules.$kernelname
@autoboot 5
The 'include' commands make it easier to keep your module sets
organised, should you want to do that.
--
\
> sendit() and recvit() for socket I/O), will anyone complain?
I'd second Garrett on this; as long as it's documented somewhere
that the *1 routines are the "backends", it sounds eminently sensible.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometime
omputers communicate with A.
This usually means that you have the netmask wrong, so broadcasts don't
work (wrong destination address). When someone else talks to the
misconfigured machine, they create an ARP cache entry, which allows the
victim to "see" them (until it times out).
ve *always* done myself, so I don't mind those warnings either.
This comes straight from elementary boolean algebra. Not doing this
would be unthinkable.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is lo
t; Source is at http://iclub.nsu.ru/~semen/ntfs/
Sounds like a good idea. Do you have a reviewer?
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with
it to
> RELENG_3 instead of -current, and has not corrected that yet.
Gah. Thanks for the PR reference.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's onl
x27;s not
> that easy.
Install it in $PREFIX/compat and then make a symlink from /compat to
${PREFIX}/compat. This only fails if you then install the SVR4 stuff
with a different ${PREFIX}, which will screw you anyway. 8)
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ some
haven't tried this yet, and since without the warnings you'd
never know about the problems in the first place, at least we have an
improvement over the status quo.
If it sucks, we can back it out. If not, then we can keep it.
Relax, both of you. This is -current, remember?
--
\\ S
avorite text editors; it's no harder to install the Fortran
support.
--
\\ Sometimes you're ahead, \\ Mike Smith
\\ sometimes you're behind. \\ m...@smith.net.au
\\ The race is long, and in the \\ msm...@freebsd.org
\\ end it's only with yourself. \\ msm...@c
701 - 800 of 860 matches
Mail list logo
