Do you own a Harley? Do the Mosh Pit? You definitely like riding the edge of
insanity...
-current is always in a state of flux... I say you lucked out...
FreeBSD is killer stuff, but, I personally wouldn't risk a job on the odds of getting
a stable -current when I needed one...
Chris Knigh
last cvsup, less than an hour ago.
cc -c -O -g -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../../.. -I../../../dev
-I../../../contrib/de
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:
>>
>>
>>
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. Apparent
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 FreeBS
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: Th
John Baldwin wrote:
> On 27-Nov-01 Jim Bryant wrote:
>
>>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.
>>
>
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
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 vidcontro
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 hav
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
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 d
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.
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
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 ke
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 w
I'll give it a try next time I build a kernel. Thanks for the info on the
optimization option info, adding -O was successful in
compiling atomic.c.
John Baldwin wrote:
> On 08-Nov-01 Bruce Evans wrote:
>
>>On Fri, 2 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.
Michael Class wrote:
> Hello,
>
> just a question. Has anyone usb-devices working on a current-smp
> (very recent current, but problem exists since I c
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
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
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...
>>
>>
.
1:46:59pm wahoo(110): 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:
&g
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ø
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 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 world, but I would assume that
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 yest
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 re
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 t
Jim Bryant wrote:
> 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 |
>>
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: MODE
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 rea
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 domain
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!?
G
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 f
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
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.
>
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 b
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 hav
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.
>>
>
&
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
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
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 fi
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 /u
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
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
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 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
>>>
>
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 on
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 reache
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 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
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 ena
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 of
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 Tya
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
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 alwa
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
> s
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 h
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 ALW
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
Jim Bryant wrote:
>
>
> 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 v
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
>> > > t
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 thi
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
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 be
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 sa
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!
>>>
>>
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
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...
>
>
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
Terry Lambert wrote:
> I was still grumpy about the change, but that at least was
> enough to mollify me into not objecting loudly and persitantly
> up to the import.
>
> Let me get this straight, though: _now_ you are saying that
> the system wide defaults and account template defaults will
>
Nate Williams wrote:
>Wow. Why not use xdm? 8)
>
Too lazy?
>>>Heh. You just uncomment one line in /etc/ttys and HUP init. It's not
>>>compilicated.
>>>
>>Indeed. However, there are some differences in startup of which to be
>>aware (.xinitrc vs. .xsession).
>>
>
> I just
David Wolfskill wrote:
>>Date: Sun, 26 Aug 2001 02:43:56 -0400 (EDT)
>>From: "Brandon D. Valentine" <[EMAIL PROTECTED]>
>>
>
>>On Sat, 25 Aug 2001, Jim Bryant wrote:
>>
>
>>>>Wow. Why not use xdm? 8)
>>>>
>
&g
Mike Smith wrote:
>>* Jim Bryant <[EMAIL PROTECTED]> [010823 01:33] wrote:
>>
>>>i noticed this after a build from -current of about 24 hours ago:
>>>
>>>due to problems getting kde-2.2 to compile under -current, I am
>>>currently using windo
Peter Wemm wrote:
> Jordan Hubbard wrote:
>
>>>Because of certain differences, it cannot be used wholesale as a
>>>replacement for csh.
>>>
>>Then please enumerate them so that they can be given due attention.
>>This is exactly the sort of detailed feedback that was requested when
>>we first rai
sentance: "..., but it's not a drop-in replacement for csh."
Kris Kennaway wrote:
> On Thu, Aug 23, 2001 at 05:03:29PM -0500, Jim Bryant wrote:
>
>>Why is csh tcsh?
>>
>>There are differences...
>>
>> 4:52:48pm wahoo(6): cmp /bin/csh /bin/tcsh
Why is csh tcsh?
There are differences...
4:52:48pm wahoo(6): cmp /bin/csh /bin/tcsh
4:59:12pm wahoo(7):
jim
--
ET has one helluva sense of humor!
He's always anal-probing right-wing schizos!
_
Do You Yahoo!?
Get your free @yahoo.
Please DISREGARD my previous message on this topic...
I have issued myself a severe boot to the head in the true tradition of tai-kwan-leap
as a result of sending that, so if you must,
please remember that I booted myself in the head first, and was enlightened by the
experience.
jim
--
ET ha
i noticed this after a build from -current of about 24 hours ago:
due to problems getting kde-2.2 to compile under -current, I am currently using
windowmaker and doing a `exec startx >&/dev/null` to
get into X without leaving a console shell open...
the problem i have is that when i switched b
This seems to solve the problem. Thank you.
How soon before VESA will be stable? I do prefer a 132x60 text-mode console...
Kazutaka YOKOTA wrote:
> Would you please remove the vesa driver from the kernel and
> do not try loading the vesa module either, and see if things work?
>
>
>>Actuall
Same thing here, started with the build this morning...
I know of one change that had been done in the past 36 hours to usb, but it should not
have done this, as the patches I was using
didn't produce this before the committer committed the patches.
Maybe something else got changed as well?
V
Actually, I have tried to get the VESA splash thing going, but never can get anything
to display... I can try removing that... I
believe it is still set up this way...
What are the limitations on image size and color-depth for the boot splash thing?
Kazutaka YOKOTA wrote:
> Do you by any ch
Kris Kennaway wrote:
> On Mon, Aug 20, 2001 at 11:52:07AM +0100, Josef Karthauser wrote:
>
>>I'm having strange problems with -current on a laptop with 64mb of
>>memory. Periodically "things go strange" [tm].
>>
>>Because of the lack of memory I'm using a fair amount of swap.
>>
>>Everything
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. I
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 thi
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
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 fr
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
>&
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&g
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.
> I
ake assumptions about an operating environment without understanding the
problems of living within that environment.
>
> On Sun, 12 Aug 2001, Jim Bryant wrote:
>
>
>>I said I'd drop it, but apparently there are people that don't
>>understand the dinosaur mentality of
out cp `which bash` /bin and then how to add it
> to etc/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 shell
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 copy
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
> | > d
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
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.
C
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
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 exper
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
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 t
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
1 - 100 of 139 matches
Mail list logo
