interesting. i thought this was a netscape issue.
In reply:
If you are still running current, please cvsup the newest sources. This
problem has been solved in the past few days. It showed up on saturday
evening after a commit on McKusick and most of the problem area's have
been identified
In reply:
On Sat, 3 Jul 1999, Greg Lehey wrote:
I personally think that, in such a case, you'd be justified to commit
it as a temporary measure. Due to the difference in time zones, this
has hit people while I've been asleep. That doesn't mean the commit
would stay, of course, but at
Just for kicks, while waiting for my phones to be hooked up at the new
address, I ran some heavy duty benchmarks to see if the systems
transported fine. i think they did arrive undamaged in the move, but
i ran pitest at the maximum rated precision.
apparently, this is not a /usr/bin/time issue,
In reply:
On Sat, 23 Oct 1999, Matthew Dillon wrote:
I found a copy of the C version of trek73 in my Amiga archives. This
is the trek73 originally written in HP-2000 Basic that was rewritten
by Dave Pare and Chris Williams in C and seriously enhanced by a bunch
of
In reply:
On Sat, 23 Oct 1999, Matthew Dillon wrote:
I found a copy of the C version of trek73 in my Amiga archives. This
is the trek73 originally written in HP-2000 Basic that was rewritten
by Dave Pare and Chris Williams in C and seriously enhanced by a bunch
of
In reply:
On Mon, 25 Oct 1999, Jim Bryant wrote:
"unauthorized" things for keeping Trek alive in the first place... If
it came out that Paramount ever tried litigation over such things,
they would lose a LOT of fans, and the money in their pockets! What
would come nex
In reply:
I've finished cleaning up the trek73 code but haven't created a port
out of it yet.
Anyone interested in messing with the game can obtain it from
my web site:
http://www.backplane.com/FreeBSDPorts/
It should compile and run just fine.
after several months, I decided to re-sync to -current...
i cannot build a kernel due the the following errors.
how do i get around this?
i am not going to hack the vm code that uses this.
cc -c -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes
After being informed of the paragraph in UPDATING on this topic, I went to
/usr/src/etc to see what the settled-upon UID/GID of
bind is...
Ummm... Did someone forget to commit changes to the /usr/src/etc/group and
/usr/src/etc/passwd baseline files?
What UID/GID should be used?
jim
--
ET
Okay, please don't say it... I'm blind...
Boot to the head!
I see it now, as GID 53...
Jim Bryant wrote:
After being informed of the paragraph in UPDATING on this topic, I went
to /usr/src/etc to see what the settled-upon UID/GID of bind is...
Ummm... Did someone forget to commit
FreeBSD wahoo.kc.rr.com 5.0-CURRENT FreeBSD 5.0-CURRENT #26: Sat Aug 25 02:25:41 CDT
2001
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/WAHOO i386
1). I shut down properly [shutdown -r now] about an hour ago to boot into winblowz
[yeah, but it's the only thing morpheus works in]...
2). When I
Julian Elischer wrote:
John Baldwin wrote:
On 27-Aug-01 Julian Elischer wrote:
I am ready to do my megga-commit to add the first stage of KSE-threading
support
to
the kernel. If there is any argument as to the wisdom of this move,
then this is the time to speak up!
At this stage a commit
Matt Dillon wrote:
: and preferably on more than the i386 platform. If we are going to
: be serious about supporting more hardware platforms, then we have
: to start treating them more seriously when major changes like this
: come along. If we can't get some broader testing of this done
Garance A Drosihn wrote:
At 1:49 PM -0700 8/27/01, Sean Chittenden wrote:
If there are grave concerns about having KSE and SMPng in
5.X, then why not push back the release date? The value far
outweighs the extra months needed to get it finished and out
the door,
Bosko Milekic wrote:
On Mon, Aug 27, 2001 at 03:09:53PM -0700, Julian Elischer wrote:
On Mon, 27 Aug 2001, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Peter Wemm writes:
My personal check list before committing it to -current is:
- an honest shot at getting the Alpha working.
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Julian Elischer writes:
I am ready to do my megga-commit to add the first stage of KSE-threading support
to
the kernel. If there is any argument as to the wisdom of this move,
then this is the time to speak up!
I say No, not yet.
Garance A Drosihn wrote:
5.0 (or whatever name it will go by) is slated for November, right?
And the plan was that a new 6.0-current branch wouldn't even be STARTED
until sometime next year, because we'll be concentrating on the
reliability of 5.x. These kernel changes have to go in before
Sean Chittenden wrote:
I am ready to do my megga-commit to add the first stage of KSE-threading support
to
the kernel. If there is any argument as to the wisdom of this move,
then this is the time to speak up!
I have one system that I've been maintaining/updating since the
2.X days
Garance A Drosihn wrote:
At 5:02 PM -0500 8/27/01, Jim Bryant wrote:
Garance A Drosihn wrote:
We can't just keep pushing back the release date because some
very important enhancements could be made. It will ALWAYS be
true that there are more very important enhancements on
the horizon
Garance A Drosihn wrote:
At 6:28 PM -0500 8/27/01, Jim Bryant wrote:
The patches seem relatively benign, and after some basic
immediate testing, they should be committed to -current.
That's all I'm trying to say.
Then shut up and help test it. That's what KSE needs,
some people who
David O'Brien wrote:
On Mon, Aug 27, 2001 at 03:13:19PM -0500, Jim Bryant wrote:
Count my vote as a go-for-it.
Blah. You're vote doesn't mean jack in this.
Unless you are one actively working on the 5-CURRENT kernel (SMPng
specifically), or are funding 5-CURRENT kernel development; you
Like I said... Count me in...
Julian Elischer wrote:
Pleas guys,
cut it out...
Take a copy, run it, beat on it..
let me know if it fails..
thanks..
(p.s. I'll need to put a new patch up because -current has changed.. :-)
jim
--
ET has one helluva sense of humor!
He's always
I'm in the process of getting set up for testing KSE too, but I was wondering, how are
you capturing the panic dump? Do you run a
serial console or something to do it?
Carlo Dapor wrote:
can you try the same with a matching -current?
I heard that msdosfs is bombing there too.
(just to
In progress... You aren't joking about it taking a while... Been half an hour now...
Mike Smith wrote:
My motherboard is a Tyan S1696-DLUA dual P2-333. I am using the latest known
bios updates. ACPI is enabled, and APM disabled in
the BIOS. This happens regardless if PnP is on or off in
Duh!!! No wonder it was taking so long... Seems we both forgot that would have never
come up with anything...
doing a:
hexdump -C /dev/mem | grep RSD PTR
now...
Mike Smith wrote:
My motherboard is a Tyan S1696-DLUA dual P2-333. I am using the latest known
bios updates. ACPI is enabled,
I would have waited for the re-run of hexdump to finish, but checking right after I
sent the last message produced:
DING! wahoo(102): hexdump -C /dev/mem | grep RSD PTR
000716d0 67 72 65 70 20 22 52 53 44 20 50 54 52 22 27 00 |grep RSD PTR'.|
000719d0 67 72 65 70 20 22 52 53 44 20 50 54
I'm going to double-check my config against GENERIC, but I've been seeing this since
before the new changes.
Because of that one problem with the missing file the other day, I simply blasted and
re-synched my /usr/src/sys, so I am definitely
running the latest sources.
My motherboard is a
I sent it in a private message to you to keep from spamming the list with a 60k file...
I was wondering why the address was so high, and it was still catching matches of
anything...
Mike Smith wrote:
I have a question, does /dev/mem wrap lgoically back to address once
it's reached
I have a question, does /dev/mem wrap lgoically back to address once it's
reached the end of physical memory?
I left the hexdump -C running all night and just checked and it's still running, and
the output file shoes that it's somewhere past
address:
110779f460 7c 7c 52 53 44 20 50
I recall reading the explanation somewhere on the KDE site on why artsd will hold a
lock on the sound device, but as I recall the
lock is like for 30 or 60 seconds... Reading the explanation I seem to recall
thinking it was a lame hack solution to the problem
of dealing with multiple opens
John Baldwin wrote:
On 04-Sep-01 David W. Chapman Jr. wrote:
On Tue, Sep 04, 2001 at 09:40:44AM -0700, John Baldwin wrote:
In fact, am doing so right now inside of KDE (with arts or whatever their
sound
daemon is called also running). Granted, it sounds rather weird. :-P
915 john -8
David W. Chapman Jr. wrote:
I haven't looked at the code, but does a value of 0 for vchans mean
infinite, I know this is a standard use for the value of zero in some
instances...
What what I gather, 0 means none, only use how many channels the
sound card has. I'm assuming that John has
Dave Cornejo wrote:
I apologize for not having any idea where to start on this. I am not
whining for someone to fix something, merely reporting an odd behavior
that I have now seen on multiple machines in cae it means something to
anybody.
I am tracking current almost daily on three
David O'Brien wrote:
On Wed, Sep 05, 2001 at 12:04:49PM -0700, Terry Lambert wrote:
Samuel Tardieu wrote:
Or why is BSD make used when the vast majority of Free Software developpers
use GNU make?
1)It actually works
You forgot the syntax is nearly the same as GNU Make.
(or rather
Julian Elischer wrote:
On Wed, 5 Sep 2001, Daniel C. Sobral wrote:
David O'Brien wrote:
On Tue, Sep 04, 2001 at 09:48:24AM -0300, Daniel Capo Sobral wrote:
When I first wrote the loader.conf thingy, I couldn't get the value
of environment variables from the FICL environment.
...
Dave Cornejo wrote:
you wrote:
And just for the record: PERL is right out (of space) for this purpose...
as I assume emacs would be too? :-(
Hey now! Them's fightin' words! :^)
Emacs makes the sun shine,
Emacs makes the birds sing,
Emacs makes the grass grow green!
chsh -s
Jim Bryant wrote:
Dave Cornejo wrote:
you wrote:
And just for the record: PERL is right out (of space) for this
purpose...
as I assume emacs would be too? :-(
Hey now! Them's fightin' words! :^)
Emacs makes the sun shine,
Emacs makes the birds sing,
Emacs makes the grass
John Polstra wrote:
In article [EMAIL PROTECTED],
KSrinivasa Raghavan [EMAIL PROTECTED] wrote:
For some reasons I was unable to checkout sources from cvs server of
FreeBSD sources. I have been using anoncvs.FreeBSD.org to fetch the
files.
I believe the administrators have been upgrading
Kris Kennaway wrote:
On Wed, Sep 05, 2001 at 08:42:39PM -0500, Jim Bryant wrote:
I doubt if the bootloader will ever change from FORTH, but if it
does, I suggest LISP as the preferred choice on a short-list of
potential replacements.
Show us a suitable LISP interpreter, then.
Kris
Bakul Shah wrote:
I doubt if the bootloader will ever change from FORTH, but if it
does, I suggest LISP as the preferred choice on a short-list of
potential replacements.
Show us a suitable LISP interpreter, then.
I don't know what size constraints the bootloader has to have
but the
FreeBSD Fanatic wrote:
Show us a suitable LISP interpreter, then.
$ cd ~/lang/Scheme/tinyscm-1.27
$ size scheme
textdata bss dec hex filename
6134244763480 69298 10eb2 scheme
Is that statically-linked? I'm curious to know the size of the bootloader
forth
Jordan Hubbard wrote:
Are you guys on crack? Scheme is just a dialect of LISP, where LISP
could also just as easily be any one of MacLisp, InterLisp, Franz
Lisp, Common Lisp or one of many other possibilities. The very
acronym lacks specific meaning without an additional qualifier.
Scheme
I was just checking something out in top, and noticed a big discrepancy in the core
usage for mozilla, and XF86 looks a bit heavier
than normal...
The mozilla in use is the linux netscape 6.10 dist direct from netscape [i avoided
installing the -port, because it was using some
kinda hacked
Faulty battery monitor?
If it's a NiCad, consistant recharging when the cell isn't discharged to the
recommended discharged voltage can cause what is
known as memory effect, where the battery will never charge above that
partially-discharged state at which it been consistantly
recharged
Jonathan Love wrote:
jim
--
ET has one helluva sense of humor!
He's always anal-probing right-wing schizos!
POWER TO THE PEOPLE!
_
Do You Yahoo!?
Okay, from -CURRENT fetched at approximately 1320 CDT today, buildworld/installworld
were successful, building the kernel was
successful, booting failed with the following [copied by hand]:
trap 12: page fault in kernel mode
cpuid = 1 lapic id = 0100
virt. addr = 0x0
code = supervisor
Brian Fundakowski Feldman wrote:
After updating my system I can't burn CD-Rs successfully. Can anyone else?
What happens is pretty simple:
{/home/green/toxicity}$ burncd -s 8 -d audio /dev/null $(ls | trackclassify
burncd: ioctl(CDRIOCINITWRITER): Input/output error
acd0:
This doesn't indicate that you were cracked if it was anonymous FTP.
You may have been scanned for open ports, and it appears that they took advantage of
your FTP being open.
Set up logging via the inetd.conf line (man ftpd for options). Then you can at least
use ipf or ipfw to ban the
I am getting intermittant communications initialization errors involving DCOPSERVER
upon starting KDE. The thing is that it seems
to be random. So far it will happen 2 out of every 3 times you attempt to login via
KDM... So far, the only cure is to keep
logging in until it doesn't produce
I believe at least one version of the SanDisk one is supported, and I recently helped
test and get committed the Microtech
CameraMate I personally recommend the CameraMate, as it has support for all known
CompactFlash devices, including IBM
Microdrives, as well as the fact that it also
This is from -current as of about 1am or so CDT today.
2:51:10pm wahoo(112): burncd -s 12 -f /dev/acd0c data StarOffice52.iso fixate
burncd: ioctl(CDIOCSTART): Device busy
I was under the impression that if the kernel and world were in sync that this would
work based on a message I read
Kris Kennaway wrote:
On Wed, Oct 03, 2001 at 01:56:11PM -0500, Jim Bryant wrote:
This may sounds strange, but as I don't actually recall seeing any actual changes to
burncd unless i missed something in my cvsup
early this morning CDT...
I just decided to give it another try before booting
Heheh... Just to clarify for some... my standard practice involves following
buildworld with installworld...
Jim Bryant wrote:
Søren Schmidt wrote:
Kernel and burncd must be in sync again, a make kernel followed
by a make world should do it.
-Søren
acd0: CD-RW Hewlett-Packard
Søren Schmidt wrote:
Kernel and burncd must be in sync again, a make kernel followed
by a make world should do it.
-Søren
acd0: CD-RW Hewlett-Packard CD-Writer Plus 9500 at ata1-master PIO4
This is from -current as of about 1am or so CDT today. I did a make buildworld
instead of a make
I got the following eariler, and thinking I was out of sync, I cvsupped everything
from scratch, and still got it.
---
cc -c -g -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -f
format-extensions
Is anyone else seeing this problem? I posted a message the other day to this list,
and have yet to see a single response.
This is from a completely fresh cvsup of everything.
buildworld succeeds, but the kernel build fails on atomic.c with the following message
about the ATOMIC_ASM macros in
PIIX4, and I do think it's running under uhci.
Daniel O'Connor wrote:
On 10-Nov-2001 Jim Bryant wrote:
I have a [secondary] USB Keyboard with a mouse port on it's side installed,
as well as a cameramate CompactFlash reader hooked up.
Both work.
What chipset though?
The OHCI stuff
I have a [secondary] USB Keyboard with a mouse port on it's side installed, as well as
a cameramate CompactFlash reader hooked up.
Both work.
Michael Class wrote:
Hello,
just a question. Has anyone usb-devices working on a current-smp
(very recent current, but problem exists since I can
I am in the process of switching to a USB keyboard with a PS/2 to USB mouse port on
the KB [freeing IRQ 12].
The keyboard works, the mouse works.
My problem here is in getting past the BTX loader WITHOUT the AT keyboard attached.
How would I keep BTX from freezing when it
can't see the AT
It's not the BIOS failing it...
The BTX bootstrap loader V 1.00 detects the keyboard, and refuses to proceed without
it.
Chris Dempsey wrote:
Try changing the BIOS options regarding failing on all
errors. After changing my Tyan Thunder K7 to not fail
on keyboard failures, it was able to
John Baldwin wrote:
On 16-Nov-01 Jim Bryant wrote:
It's not the BIOS failing it...
The BTX bootstrap loader V 1.00 detects the keyboard, and refuses to proceed
without it.
Err, no. BTX cares zero, zilch, nada about keyboards. Can you please provide
the error message you get
John Baldwin wrote:
On 18-Nov-01 Jim Bryant wrote:
John Baldwin wrote:
On 16-Nov-01 Jim Bryant wrote:
It's not the BIOS failing it...
The BTX bootstrap loader V 1.00 detects the keyboard, and refuses to proceed
without it.
Err, no. BTX cares zero, zilch, nada about keyboards. Can you
John Baldwin wrote:
On 19-Nov-01 Jim Bryant wrote:
anyhow, now that this is working, i'm kinda pissed to have lost use of my
mouse wheel. apparently the keyboard was made before
wheels became popular.
anyone know a good usb keyboard with a ps/2 mouse port built-in that will
translate
I recently [this week] had to revert to a tape backup of an out-of-sync /var because
yet again, /var got mangled on 'shutdown -r
now', this time, and I reported this to the list the first time this happened, is the
second time I have had to do this, so this
seems to be an ongoing issue.
I
VESA is broked. Remove VESA from your config. Been this way for months.
It also will panic once in a VESA mode, such as my favorite and yours, 132x60, when
switching from vty to vty.
Peter Jeremy wrote:
Having installed a new kernel and userland from sources about a day
old, my vidcontrol
Andrew Kenneth Milton wrote
+---[ Peter Jeremy ]--
| Having installed a new kernel and userland from sources about a day
| old, my vidcontrol command now causes a panic:
[snip]
| The command I used was vidcontrol 132x60 after confirming that
| this was listed in
): burncd -s 12 -f /dev/acd0c data StarOffice-x86.iso fixate
next writeable LBA 0
addr = 0 size = 587956224 blocks = 287088
writing from file StarOffice-x86.iso size 574176 KB
written this track 574176 KB (100%) total 574176 KB
fixating CD, please wait..
Jim Bryant wrote:
Heheh... Just to clarify
I know this is probably a minor issue, as it is only an annoyance, and doesn't impact
operation or performance, but still..
Ever since I concatenated some old drives to make a more reasonable capacity out of
them, I have been noticing the following
whenever vinum is loaded at startup [Note:
After upgrading -current, then reverting back to the previous [more stable] kernel,
upon rebooting after reverting, I noticed the
oddest thing on ttyv0. Apparently, after /etc/rc took over in init all of the text
was still in the kernel color scheme.
FreeBSD wahoo.kc.rr.com 5.0-CURRENT
Oh yeah, I immediately did a shutdown with reboot, and the problem did not duplicate
itself.
Jim Bryant wrote:
After upgrading -current, then reverting back to the previous [more
stable] kernel, upon rebooting after reverting, I noticed the oddest
thing on ttyv0. Apparently, after /etc
Yeah, I'm also using the SMP kernel.
Dan Nelson wrote:
In the last episode (Jan 28), Jim Bryant said:
Oh yeah, I immediately did a shutdown with reboot, and the problem
did not duplicate itself.
Jim Bryant wrote:
After upgrading -current, then reverting back to the previous [more
stable
Hi, this has happened twice now, and I think it's about time to report
it.
I'm running -current Tue Oct 17 00:02:26 CDT 2000, and have noticed
that under this and a -current from a few weeks ago that while
printing in netscape, the whole system will lock. no panic, just
big-red-button-time..
hmmm... I just got a message from chris, he said he will be adding
AES/Rijndael to the kernel ASAP...
According to the Rijndael spec, it seems to also function as an
excellant pseudo-random number generator...
You can find this info at:
http://www.esat.kuleuven.ac.be/~rijmen/rijndael
Section
#include sys/malloc.h
needs to be added to the top of if_fddisubr.c
-current pukes on the first instance of MALLOC() without it...
jim
--
All opinions expressed are mine, if you| "I will not be pushed, stamped,
think otherwise, then go jump into turbid | briefed, debriefed, indexed, or
I've been getting a hard panic/page fault whenever attempting to print
for a few weeks now.
it always shows that it is hung in the irq7 process.
does this have to do with the /dev/random wierdness? if so, any idea
on when it will be fixed?
jim
--
All opinions expressed are mine, if you|
Hi, it looks like if_fpa.c has been modified again, but was checked
into CVS untested.
from a basic GENERIC, with nothing other than the fddi and fpa devices
added to the config, I get the attached messages on compile.
also, i noticed that in pdareg.h, that the full duplex options are
included
Is this a known problem?
Running -current.
options MSDOSFS #MSDOS Filesystem
6:17:42pm wahoo(111): kldstat
Id Refs AddressSize Name
11 0xc010 35ccd8 kernel
6:20:27pm wahoo(112): d /dev/da0s1
crw-r- 1 root operator 13, 0x00020002 Jul 7
This is a new issue [was not present in -current a few months ago].
Attempting a dump to an HP C1533A DDS-2 drive, dump seems to freeze the tape at EOT.
Inserting the next volume of the dump and typing yes only produces write errors.
Performing an `mt rewind`, prior to typing yes clears the
of tape. I've had real trouble reproducing this situation. I've
had some reports, but I've not been able to really make it happen for me, and,
yes, I use DDS tapes also.
Are you in set in fixed block or variable block mode?
-matt
On Thu, 12 Jul 2001, Jim Bryant wrote:
This is a new
Harti Brandt wrote:
On Fri, 20 Jul 2001, Yoshihiro Koya wrote:
YKI CVSuped at Thu Jul 19 11:33:58 UTC 2001, and did make world.
YKThen Xwrapper always exits on signal 11, and I cannot use X11 now.
You need to recompile all ports using pam. See /usr/src/UPDATING.
Is there any extensive
Vincent Poy wrote:
On Wed, 18 Jul 2001, Dima Dorfman wrote:
Vincent Poy [EMAIL PROTECTED] writes:
linking kernel.debug
linprocfs.o: In function `_linprocfs_mount':
/usr/src/sys/compat/linprocfs/linprocfs.c:748: undefined reference to
`pfs_mount'
You compiled in linprocfs
I don't know if this belongs here, in the database list, or in the ports list...
Under -current from early Sunday morning [CDT], a build of mysql-server-3.23.39 hangs
forever at:
---
=== Building for mysql-server-3.23.39
.
. [snip]
.
./gen_lex_hash
I did an archive search of this list, and found a post from April from a guy who had
some diffs to scsi_da.c and the umass driver to
get this thing working. I sent him an email on Friday, but haven't heard back yet.
He said he had it working under -current.
Does anyone have a copy of these
I forgot to add:
I am using the make option: `make WITH_LINUXTHREADS=yes`
Jim Bryant wrote:
I don't know if this belongs here, in the database list, or in the ports list...
Under -current from early Sunday morning [CDT], a build of mysql-server-3.23.39
hangs forever
Okay, I just built it successfully without WITH_LINUXTHREADS=yes.
I also noticed that my linuxthreads lib was linuxthreads-2.1.2, and I'm rebuilding it
with the linuxthreads-2.2.3_1 sources.
Afterwards, I'll try the compile again.
Jim Bryant wrote:
I forgot to add:
I am using the make
Okay, AFTER rebuilding linuxthreads with the most recent port, IT DID make it past
gen_lex_hash.
Word to the wise, if you haven't rebuilt linuxthreads, I suggest you do to avoid the
problems I have had.
Again, I am running -current of the early hours [CDT] of Sunday morning.
Jim Bryant wrote
I've never had this before, and I have traced the message to ufs/ffs/ffs_vnops.c on
line 634.
I have recently noticed [since my last svsup] that this is happening on boot and
shutdown [in which case, the messasge is also in
the same file, but for umount conditions].
I am not a filesystem
Jim Bryant wrote:
I've never had this before, and I have traced the message to ufs/ffs/ffs_vnops.c on
line 634.
I have recently noticed [since my last svsup] that this is happening on boot and
shutdown [in which case, the messasge is also in
the same file, but for umount conditions
Am I desynched? I went to single-user, tried to do a fsck -s, and found there is no
such option.
Also, the /etc/fstab didn't need changed at all. It is already proper.
Needless to say, going to single-user, running just `fsck -y /dev/ad0s1g` fixed the
problem, although it noted no errors.
Gordon Tetlow wrote:
On Sat, 4 Aug 2001, Gordon Tetlow wrote:
Sure enough, that fixed the kernel panic, but here's the next odd piece,
my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940
dmesg reports that ahc0 is there. The lines from the dmesg are (hand
Andrew Kenneth Milton wrote:
+---[ Gordon Tetlow ]--
| On Sat, 4 Aug 2001, Gordon Tetlow wrote:
|
| Sure enough, that fixed the kernel panic, but here's the next odd piece,
| my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940
| dmesg
I did an archive search of this list, and found a post from April from a guy who had
some diffs to scsi_da.c and the umass driver to
get this thing working. I sent him an email a couple of weeks ago, but haven't heard
back yet.
He said he had it working under -current.
Does anyone have a
/shells and chsh root, then I really question if they should be the kind
of people that dictate the future of FreeBSD.
0n Sun, Aug 12, 2001 at 04:32:55AM -0500, Jim Bryant wrote:
IMHO, all widely accepted shells should be put in /bin
jim
--
ET has one helluva sense of humor!
He's always anal
The Anarcat wrote:
[Foul-mouthed anti-gummint drivel deleted]
Actually, it is up to us to resolve this. I don't think you understand how
DOD operates. The vendor makes the changes, not DOD. Not the admin.
And FreeBSD is the *vendor*? I don't think so. At least I don't hope so.
If I'm
Steve O'Hara-Smith wrote:
On Sun, 12 Aug 2001 17:04:01 -0500
Jim Bryant [EMAIL PROTECTED] wrote:
JB I said I'd drop it, but apparently there are people that don't understand the
dinosaur mentality of certain organizations such as
JB DOD, DISA/DECC, OSD, DARPA, USA, USN, USAF, and USMC
DOD/DFAS, as well as DOD/DISA.
I find it amazing that the CIA has a more lax policy than DFAS and DISA.
David O'Brien wrote:
On Mon, Aug 13, 2001 at 04:13:52AM -0500, Jim Bryant wrote:
from what i've read here, not many undrestand the actual mindset of the
military when it comes
Joseph Mallett wrote:
On Mon, Aug 13, 2001 at 07:23:26PM -0500, Jim Bryant wrote:
DOD/DFAS, as well as DOD/DISA.
I find it amazing that the CIA has a more lax policy than DFAS and DISA.
The only person I've ever talked to from the CIA was in charge of network
security to some degree
This is pretty wierd...
I'm running -current as of 7am this morning, and am listening to Black in Black in
XMMS at this moment.
SB-Live! Value, I am running SMP.
Richard Todd wrote:
In servalan.mailinglist.fbsd-current Daniel M. Kurry writes:
On Wed, Aug 15, 2001 at 07:01:46PM +0200,
Søren Schmidt wrote:
It seems Alexander Leidinger wrote:
On 19 Aug, Søren Schmidt wrote:
Yups, reverting this, even in a newer kernel makes sound work again,
well the VIA support is still not sounding proberly, but it didn't
before as well so thats not related to this bogon...
Perhaps
I am getting this with regularity now.
The one time I was available to see the panic, I forgot to go into the debugger and do
a traceback, but it had something to do with
a mwrite, and had a line concerning [maybe a buffer is?]...
I know this isn't much to go on, but that's what I have.
1 - 100 of 127 matches
Mail list logo
