> On Tue, 18 Dec 2001, Gerhard Sittig wrote:
>
> > bzip2 has been around for a while and has been shipped since
> > 4.4-RELEASE. :) When I see the constant "who put another
> > three KB into the kernel and thus broke release?" against the
> > "9KB plus for the loader versus 40KB gain for the
> This is the message that popup just before the kernel load, and at the beginn
> ing of the boot process,
> there is another strange message "no /boot/loader".
>
> Do you know what does it mean?
It means you deleted, renamed or moved /boot. Don't do that.
--
... every activity meets with op
>
> Just got my hands on a brand new DL360 from compaq. (Dual 1G Procs with
> a gig of ram). Loaded FreeBSD 4.4 on it from the CD and made a custome
> SMP kernel and low and behold it hangs at the APIC_IO.
"hangs at the APIC_IO" doesn't mean anything. Copy the last few lines of
kernel output
> However, when the computer boots with the new kernel, even though it
> recognizes the chip, it tells me:
It's recognising the chip because you've told it to. But it looks
like there are more differences than just the ID.
> rl0: port 0x6000-0x60ff mem 0xe000-0xe000
> 00ff irq 11 at device
I haven't been able to do any testing for the 4.4 release, unfortunately; time
simply hasn't been available.
However, the controller should work. Make sure that it's not in I2O mode,
and that the array is not degraded or rebuilding.
> I'm attempting to install FreeBSD-stable on a Micron NetFRA
> >> Because not all i686'es support SSE.
> >
> >So detect it automatically based on the CPU feature bits.
> >
> >Needing a kernel compile option for this is unforgivably lame. If you
> >want to be able to disable it, use a tunable.
>
> Perhaps; the "gist" I get is that the compile option is for
>
> --R+My9LyyhiUvIEro
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> On Thu, Aug 16, 2001 at 04:20:35PM -0400, Kenneth W Cochran wrote:
>
> > Assuming CPU_ENABLE_SSE is a Good Thing, why not make it
> > "default" with the "cpu I686_CPU" kernel config directive
>
> Hope this helps others on Dell, it would be great to get Dell to
> offers these controllers instead of those crappy PERC controllers, but
> these I guess are too expensive???
There's not much more subjective than RAID controllers, except perhaps
text editors. 8) I'm glad you're happy with th
> What's mean "pnpbios: Bad PnP BIOS data checksum" ?
It means that your PnP BIOS data has a bad checksum.
We don't trust it in this case. Some vendors don't bother to compute the
checksum for this structure; we are more conservative than Microsoft, and
refuse to use the PnP BIOS in this case
> So, someone wanting to implement this in FreeBSD isn't starting from
> square one?
That depends on how you number your squares.
> Can the NetBSD stuff be fairly easily ported to FreeBSD, or is their VM
> system too funky?
It's just different. But no, the NetBSD work doesn't immediately
tr
> Hi,
> I am following 4.3-stable since I did a CD-ROM install of 4.3-release. A
> few weeks ago I did build the world which succeeded in my opinion.
> Additionally I upgraded to XFree86 4.1.0_4 and KDE 2.1.1. The problem is
> that now sometimes the x-server takes ages to come up after 'startx' an
> On 11-Jun-2001, Jordan Hubbard wrote:
> > Hmmm. It seems like this thread has degraded to simple
> > project-bashing so I'll not be a party to keeping it on life support
> > any longer.
>
> I don't think this is the case at all. For whatever it's worth, it
> doesn't appear that the stability
> I've been waiting for a FORTH-geek to pop his head up; I
> have most of "nextboot" reimplemented... I've added "fwrite"
> and "flseek" verbs. I've thought about kidnapping an
> astronomer. 8-).
>
> The current problem is that the biosdisk.c doesn't contain
> "write" code, and that the libstan
>
> If I specify
>
> device pcm0 at isa? port 0x534 irq 7
>
> I get:
>
> mss_detect, busy still set (0xff)
> pcm0 failed to probe at port 0x534-0x53b irq 7 on isa0
>
> with
>
> device pcm0 at isa? port? irq? drq1 flags 0x15
You *should* just be able to use the PnP BIOS. However:
> pnpbi
In fielding a question from someone regarding what appears to be
SIGVTALRM sniping on their system, I noticed that the pstats structure
(which holds the p_timer fields which are used to track interval timers)
is outside the bzero-on-allocation region of the proc structure.
Thus it seems to m
> Mike Smith writes:
> > >
> > > I recall something about this on another FreeBSD list a week or so ago.
> > > Supposedly there is a firmware update available that fixes this problem.
> >
> > It's not clear whether Raymond is talking abou
> I have been reading the instructions for tracking stable and what is
> recommended in the way of procedures. It seems from this that it would be
> extremely hard to follow these recommendations for a remote POP. IE moving
> to single user mode and on the whole messing with the machine for seve
> :: The risk is the same in Linux; they both use gcc, and it's gcc which
> :: has the optimizer bugs. It's more common to use absurd gcc
> :: optimizations in the Linux community for some reason (perhaps they're
> :: used to code misbehaving, so additional brokenness from the gcc
> :: doesn't ad
> Hmm, I just went through all of the mlx related files and none of them
> changed between 4.2-RELEASE and 4.3-RELEASE. So it looks like there is
> something more sinister going on.
This is a known problem. I don't know what's up, and I can't reproduce
it (as I don't have any of these cards).
This is a known bug in the SRC-U21 and SRC-U31 BIOS, for which there is
no solution. You cannot use these controllers with FreeBSD.
> There is a problem booting 4.3-RC1 on server with Intel Server RAID
> Controller U2-1(SRCU21) with logical volumes created (without
> logical disks everything i
> Thomas> there are some hints how to install and to run the 3dmd under
> Thomas> FreeBSD? I'm able to run the program, but nothing happen when
> Thomas> using a browser to get information about the RAID controller.
>
> Mike> I suspect you haven't made the /dev/twe0 device node;
>
> You know, t
> The first time I did this I thought something was broken when I
> watched the newfs output those duplicate super block locations. It was
> about 10 seconds between each block! After a search of the FreeBSD
> lists I found a reference to initializing the array, and just waited.
>
> On ttyv1 the
> I have not been able to find any reference to this card in any compatibility
> documentation for FreeBSD. Is it supported by 4.2, and if not, will 4.3
> support it?
man 4 sis
See also HARDWARE.TXT, which explicitly lists this card.
--
... every activity meets with opposition, everyone who ac
> :: Actually, on the same note, I'm planning on flying a 747 jet later
> :: this evening, anyone know what I should watch out for? Any tips
> :: for a smooth ride?
>
> Yeah, don't pack the AK-47 and Semtex in the hand luggage. ;-)
>
> Thanks Alfie, I'll make sure to ask you next time I need so
> At least from looking at the Linux 2.2.18 code, if you get EROFS back
> from the Linux server, the actual set of access bits you get back won't
> have the right bits set; "nfsd_access()" just jumps to "out:" if it gets
> a "read-only file system" error, and that doesn't set "*access" to the
> re
> > I strongly suspect its an IRQ conflict. Every problem of this sort
> > that I've seen with the A7V has been an IRQ conflict, including the
> > problem I had with my own. Specificly I had to hard set the IRQ on my
> > NIC through the PCI management section of the bios.
...
> It certainly is an
> harddrive while running FreeBSD. The controler reacts on this with a wild
> beeping and beeping does not stop until the array has been rebuild or
> checked on consistency. But there was no message of any kind of error or
> drive failure or that the controler moans due some drive failures. Is thi
> On Thu, 30 Nov 2000, Peter Lai wrote:
> > So use ext2 or some other FS for your freebsd slices!
>
> Has anyone actually validated this as a solution?
Installation using this as a technique would be very difficult. You'd
also need a -current loader with ext2 support.
I do not consider it a s
> > I'm stuck in a compiler error (signal 4) while trying "make buildworld" in a
> > fresh 4.2-RELEASE installation. I sent a PR already, but I would like to
> > know if anyone here has gotten 4.2-RELEASE fresh installed (I mean, not
> > cvsup'd) and build world'd.
>
> It seems very much to me as
> As the PC architecture requires, just use an fdisk partition rather
> than a disklabel slice (slices are what UNIX vendors call them). For
> that matter I'd be happy if we removed disklabel from the picture
> entirely. I think that should be our goal. The architecture requires
> an fdisk
> i'm not entirely sure i understand. "pnp o/s = no" causes the bios
> to assign an irq to the pcic controller, meaning the pcic controller
> raises that interrupt on insertions/removals, but the driver,
> operating in polling mode, never clears the interrupt so the machine
> wedges trying to ser
> I'm going to install a new FreeBSD server and I'm looking into an
> Ultra-ATA 100 RAID solution.
You should be more worried about functionality than buzzword-compliance.
ATA-100 isn't really all that important in the scheme of things here.
> So far, my searches on Dejanews seem to
> indicate
> > On the other hand, there *is* an easy workaround to turn them off, so in
> > the worst case we would have an escape route.
> >
> > Jordan, what's your feeling on this? I don't have a 450GX board to test
> > with. 8(
>
> I feel it looks like a small but smelly hack and I also have bad
> fe
> Forwarding this to stable, as I've sent it to current by mistake..
>
> At Fri, 03 Nov 2000 06:14:49 +0900,
> I wrote:
> >
> > Would someone take a look at i386/20379, which adds support for Intel
> > 450GX chipset?
> >
> > The fix is simple enough to get into 4.2-RELEASE. Intel 450GX used to
> On Tue, Oct 31, 2000 at 10:26:12PM +0100, O. Hartmann wrote:
> > On Tue, 31 Oct 2000, John Baldwin wrote:
> > All right, I saw I was false in using bootp ... :-(
>
> One question about diskless booting. How to boot FreeBSD > 4.0, with out
> /boot/loader to have properly libkvm working ?
Typica
>
>
> Hi,
> I just got a new batch of 3Ware 6200s I plan to deploy for RAID1
> systems. I installed the card and 2 Quantums into an existing test system
>
> 4.1.1-STABLE FreeBSD 4.1.1-STABLE #1: Mon Oct 30 13:42:15 EST 2000
>
> i.e. post twe commits. At boot up time, I get
>
> tw
>
> There are some things which are broken in -stable that need to be
> fixed (alpha booting, e.g.). We'll try to leave the world a better
> place for our efforts.
-stable world builds, installs and boots on my pws433 as of earlier
today (with dfr's ata fix).
--
... every activity meets with
> > Its a shorter PCI card than the others, single channel, SCSI
> > LVD. It has OK performance. I am currently using it in a
> > RAID0+1 type config.
>
> Where can I learn more about the pitfalls? I have a model 466
> waiting to get employed (RAID5 config with three IBM drives) and
> get very
> I just compiled Gimp on the same system without any hitches. Other
> programs as well. I also ran memory tests and verified the
> motherboard's temperature via the BIOS and visually checked the fans.
>
> It's my belief that within the last three weeks new code was inserted
> into STABLE that
Please press the 'scroll lock' key to scroll upwards and report the real
error message. Before you post it, take a few minutes to check the
handbook section on kernel debugging and try giving us enough
information to actually help you.
You wouldn't ring your doctor up and say "Hey doc, I hur
>
> I don't change change my mind (this change is not needed), but here is
> yet another aspects.
>
> jkh> Agreed - vnconfig is supposed to load the vn module and does,
> jkh> at least, in -current.
>
> However, this commit maybe assumes that if somebody want to do "make
> release" of 5-current
> At 10:03 AM -0700 2000/9/21, Mike Smith wrote:
>
> >>4) Add the line
> >> controller asr
> >>to your kernel configuration file and rebuild/reinstall your kernel.
>
> When doing a "config -r KERNEL", I was told:
I've had a lot of requests for something to be done about this, and I've
finally gotten a few minutes to make it happen.
The fix for this has been committed to -stable, and there's a kit for
4.1-RELEASE users wanting to install on these adapters at
http://people.freebsd.org/~msmith/RAID/mylex/
>
> Since someone clued me in about using the PNPBIOS option to automate
> some isa resource allocations I have been experimenting with it. I've
> managed to remove most of the irq stuff from my kernel configuration
> file, apart from a few culprits. The main one is the keyboard and
> mouse. The
> > If you want a supported ATA RAID solution, see www.3ware.com.
>
> I'm curious how well the 3ware cards work under FreeBSD feature-wise? Can you
> hot-swap drives (assuming you have an IDE hot-swap frame and cartridge like
> Promise cards support)?
The 6x00 series cards support hotswap. Yo
--- Blind-Carbon-Copy
X-Mailer: exmh version 2.1.1 10/15/1999
To: [EMAIL PROTECTED]
Subject: Mylex 160/170/352/2000/3000 driver available
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 26 Jul 2000 03:18:38 -0700
From: Mike Smith <[EMAIL PROTECTED]>
I'm
--- Blind-Carbon-Copy
X-Mailer: exmh version 2.1.1 10/15/1999
To: [EMAIL PROTECTED]
Subject: Driver for Adaptec/Dell/HP PCI:SCSI RAID adapters available
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 23 Jul 2000 15:53:40 -0700
From: Mike Smith <[EMAIL PROTEC
> On Tue, Jul 18, 2000 at 05:31:47PM -0700, Mike Smith wrote:
>
> > Yes. Any program that expects colour to work.
>
> In what sense? The color codes are absorbed by xterm and it
> looks like it probably does without doing color stuff. Do you
> know of a program whi
> On Wed, Jul 19, 2000 at 01:08:41AM +0100, Josef Karthauser wrote:
>
> > joe@cuddy[503]: export TERM=xterm-color
> > joe@cuddy[504]: vi
> > xterm-color: Unknown terminal type
> > Visual needs addressable cursor or upline capability
> > :q
> > joe@cuddy[505]: uname -a
> > SunOS cuddy 5.6 Generic_
> >
> > This is a pet peeve of mine. Freebsd-stable is supposed to be the mailing
> > list that is required reading for anyone tracking stable, where all useful
> > information related to tracking stable is to be found.
> >
> > However, the list is increasingly such a high-volume, low signal-to
> We are wondering if we should expect any problems with the chipset
> in subject?
You will need 4-stable to run correctly on this chipset in SMP mode,
4.0-release has problems with APIC initialisation.
> How about the Adaptec 7892 SCSI?
Should be fine.
--
... every activity meets with opposi
ck-and-forth handshaking, which you don't get
with IDE disks. If you have the WCE bit set on the drive in question, it
will go faster.
The fact that SCSI commands are more expensive than IDE commands is also
significant given that dump I/O is performed one page at a time.
--
\\ Give
> * Mike Smith <[EMAIL PROTECTED]> [000605 16:58] wrote:
> >
> > > Well, it would be nice to auto-load or unload any module that is needed.
> > > not just ethernet and fs types. That's basically the idea. Say, if you
> > > load a driver that uses so
rmatting your drive
There are no tools to do this.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail
>
> - Original Message -
> From: "Mike Smith" <[EMAIL PROTECTED]>
>
> | > I'm missing where the end result of
> | > diff/patch differs from the files themselves. It's a nice exercise, but
> | > kind of a PITA when you're not
>
> - Original Message -
> From: "Mike Smith" <[EMAIL PROTECTED]>
>
> | 1) Get the diffs.
> |
> | You will need a CVS repository, or use the cvsweb interface
> | at http://www.freebsd.org/cgi/cvsweb.cgi to extract the diffs.
> | Note that ml
t that won't fail in
the same fashion that the earlier syscons probe did.
There have been some changes in syscons in 4.0 which may make it more
generous in dealing with your video adapter, but if syscons is not
attaching to your vide hardware, or the keyboard controller in these
systems is failin
a little
> while to implement, unfortunately.
(Just to continue talking to myself) - The reason I never ran into this,
I realised, is that I did all my work on the 2.x firmware in Alpha
systems which have an 8k page size. With a 64k d_maxio, you'll never see
more than 9 segments.
(
Ok. I know how I'm going to have to deal with this; the problem is that
we only use 16 of the 17 available S/G segments (so I can pack the S/G
tables without crossing page boundaries). This is going to take a little
while to implement, unfortunately.
--
\\ Give a man a fish, and you fe
y supports a very small number of scatter/gather
segments (17). It looks like someone's trying to do a non-page-aligned
64kb transaction there and we're overflowing. Addressing this is
probably going to require a driver patch. 8(
--
\\ Give a man a fish, and you feed him for a d
>
> - Original Message -
> From: "Mike Smith" <[EMAIL PROTECTED]>
>
> | If that's what they say, I'd be inclined to believe them. Since I've
> not
> | encountered any fatal problems with the 2.x firmware, I can't suggest
> | t
> On Sat, 29 Apr 2000 13:13:37 PDT, Mike Smith wrote:
> >
> >You leave out "how well you want it to perform" as well. All other
> >things being equal, the PCI:SCSI adapters will give you better bang for
> >your buck.
>
> Out of curiosity, how w
> * Mike Smith <[EMAIL PROTECTED]> [000420 11:39] wrote:
> > > Hi, we're running 4.0-stable as of Sat Apr 15 18:39:08 PDT 2000
> > > which include the recent amr fixes which we were hoping would cure
> > > the lockups with amr. Unfortunatly we are now
o work correctly.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "uns
the kernel on kern.flp, which
> you can mount as a normal floppy.
Don't forget to gzip it first, as it probably won't fit otherwise.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and h
> >>>>> "MS" == Mike Smith <[EMAIL PROTECTED]> writes:
>
> MS> Regardless of what you think, the only correct way to divvy up a disk on
> MS> a PC is to start with an MBR and work down from there. There is no other
> MS> way to do this pr
to start with an MBR and work down from there. There is no other
way to do this properly, and to think otherwise merely demonstrates your
ignorance.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\
oot_ddb" managed to break into a
> debugger where I would be able to at least try to have a closer
> look at this problem.
> Does somebody have any ideas what I could try out?
Sounds like you've got BIOS problems. Look for an upgrade from your
vendor, and then start breaking do
ested them and discovered they didn't work?
At any rate, you're encouraged to talk to the author/maintainer of the
code, Brian Feldman (copied). If you can make it work, wonderful.
> > On Mon, 6 Mar 2000, Mike Smith wrote:
> >
> > > > Well, I know that they are
the new one, or maybe some signal (a HUP?)
> > refreshes a getty.
>
> You're totally off the track. His problem is that the kernel (or the
> boot loader) decides that there is no built-in console and uses a
> serial console instead. This has nothing to do with init(8). I guess
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
>
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hat
> Hu... I can easily cram boot0, boot1 and boot2 in there, but loader
> is a bit to big at 128K bytes :-(.
You don't need the loader for most 'embedded' applications. Boot2 will
do you fine.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tel
tandards at this level, you'd have
to duplicate the unix-specific BIOS for every piece of hardware out there.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lif
you think about what BIOS code actually does, this should really
be fairly obvious.
In all reality, new BIOS features are actually directed towards the same
sort of problems that we're facing, even if the process is driven largely
by Microsoft. Take a look at eg. ACPI to see what I mean.
so far beyond a joke in most situations that we don't even want
to pretend in public that it's done, let alone talk about supporting it.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'
need to upgrade your cooling
arrangements, and you've been told _that_ already too.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL
sh, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
> Does FeeBSD/Alpha run reliably on an AXPpci33 with Quantum
> Fireball (SCSI)?
Yes; we do test installs onto one (although I think it has a 2GB Empire
in it at the moment, the furball was too small).
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he
n guessing at which device to use. Much more robust.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
> On Tue, 21 Dec 1999, Mike Smith wrote:
>
> >
> > The third update to the Mylex PCI:SCSI RAID controller driver for
> > FreeBSD-3.x-STABLE is now available at
> >
> > http://www.freebsd.org/~msmith/RAID/mylex/mlx-stable-991221.tar.gz
> >
>
&
ECTED]
> with "unsubscribe freebsd-stable" in the body of the message
>
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
also sure that this is a completely
>
> Will the 3.4 CDs be pressed with this bug?
Yes; we only just hit the this-year window last night with a few minutes
to spare. I _did_ manage to work around the "can't boot on some ATAPI
CDROMs" bug for CD #1, if that's any cons
inations. Give us something more to work
on. 8)
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAI
> Mike Smith once wrote:
>
> > > A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) would
> > > not boot from 3.3 CD if the SCSI disks are online. It would say:
> > > "Read Error" on the upper left of the screen -- where you'd
fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
no other changes in this release.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROT
> thank you,
>
> Roger
>
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
>
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to f
nk with this line.
> # pseudo-device pty 16
Taking pty's out is a bad idea too.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\
ompile the kernel, it compiles this one
> module... and this global variable is referenced. When I then search
> for this string (by lessing the kernel and searching for dgilbert), I
> can't find it in the kernel's image. What's up?
Module != kernel
--
\\ Give a man a fish, a
the source ourself?
It's not "a port from the Linux one"; Applixware builds for about a
dozen or so platforms, and the FreeBSD port has equal status with the
rest of them. As I've already stated above, it already has O2k support.
--
\\ Give a man a fish, and you feed him f
need a system drive. You will want one anyway; swapping onto a RAID5
array is a pretty lame idea. 8)
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\
I recompile the installation
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
w
ld be sent to hackers or current?
No. You haven't included anything like enough information yet for the
report to be at all useful.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\-- Joseph Merrick \\ [EM
> At 11:29 AM -0700 1999/9/6, Mike Smith wrote:
>
> > I'll say it again; read what has already been said. Most of us are
> > heartily sick of your side of the argument, and you're not likely to
> > get many useful responses while you continue to display
ear about it.
Er. In the example above you say "is broken when APM is enabled, works
when APM disabled". This is the result I expect.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\-- Joseph Merrick \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
everything works fine. I'm using a 3.3-RC SMP-Kernel and with the current
> settings I don't have any idle time displays in top and uptime.
APM and SMP are almost guaranteed not to work correctly.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man.
to get this
into -stable ASAP for obvious reasons.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\-- Joseph Merrick \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
>
> 8/31 12:00 GMT+0800 cvsup to the newest src tree, but my -stable box
> can't build a new kernel :
My bad, patch error. Should be fixed now.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\
done under other operating systems).
You might want to qualify the issue a little further; specifically with
regard to "typical memory controllers", logic families and fanout.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PR
ion
options.
--
\\ The mind's the standard \\ Mike Smith
\\ of the man. \\ [EMAIL PROTECTED]
\\-- Joseph Merrick \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
1 - 100 of 107 matches
Mail list logo
