It'd be interesting to see where FreeBSD stacks up
-- Forwarded message --
Date: 25 Jun 1999 17:00:02 -0400
From: Ramana Juvvadi <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: NT vs Linux benchmark saga continues
http://www.zdnet.com/pcweek/stories/news/0,4153,1015266
> >>Why have splr semantics? That is, it raises to splsoftclock if current
> >>priority is lower, else doesn't fiddle with it.
>
> splsoftclock() has always had spllower() semantics, and its main users
> (kern_clock.c and kern_time.c) depend on this.
Okay. Then Justin's suggestion of splcallout
panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
>
> >
> > panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking
> >
Sorry- -current as of today, alpha. rebooting. Likely an NFS lock.
>
> It might be if you supplied some additional information, like what
> sources your kernel was built from, as a minimum. UP or SMP? What
>
> On Friday, 2 July 1999 at 15:26:35 -0400, Brian F. Feldman wrote:
> > On Fri, 2 Jul 1999, Brian F. Feldman wrote:
> >
> >> Here's the fix. I'm sure it's not absolutely the same as what Greg will have,
> >> but if anyone wants to commit it, it will fix world.
> >
> > I know I _could_ commit it,
Let me add to this:
> opinion:
>
> If it's really blocking folks because things don't compile, it is always
> acceptable to do what you need to do- the tree should always compile even
> if -current. If the system doesn't boot because of change, then that's an
> obvious one too. If things work d
> > >
> > > If it's really blocking folks because things don't compile, it is always
> > > acceptable to do what you need to do- the tree should always compile even
> > > if -current. If the system doesn't boot because of change, then that's an
> > > obvious one too. If things work differently or
while this is happening, what does 'iostat 1' and 'vmstat 1' tell you?
On Sat, 3 Jul 1999, Alex Povolotsky wrote:
> About a week ago, I've posted a message here and didn't got positive replies.
>
> The problem is:
>
> when I use soft-updates on IDE disks (disk on primary master, disk on
> sec
I'll fix it, but not this way. It's time to prepare for handling
larger than terabyte disks that still have a 512 byte sector size as
well. The actual calculation should be:
(((u_int64_t) dp->secsize) * ((u_int64_t) dp->sectors)) >> 20LL and the
format statement should be %qdMB for the Megabyte
Sorry, I pooched it. I'll fix.
On Mon, 5 Jul 1999, Kenneth D. Merry wrote:
> Vallo Kallaste wrote...
> > Hello
> >
> > I just cvsupped the src-all, built the world, kernel and noticed that:
> >
> > changing root device to da0s1a
> > da0 at ncr0 bus 0 target 5 lun 0
> > da0: Fixed Direct Acc
>
> On Wed, 29 Dec 1999 15:31:38 GMT, Jonathon McKitrick wrote:
>
> > As of right now, which would that be? The august CD snapshot release or
> > the one available on the cvs servers right now?
>
> If I were you, I'd hold out for 4.0-RELEASE, since it's just around the
> corner (January some
Uh, Karl, sometimes majordomo will get rampant and pull one w/o warning if
there was a mail bounce.
It may be a stupid mail robot problem, not a human out to get you. If so,
you've directed your vituperation at the wrong ip address/port combo- try
port 9 instead of port 25.
On Sun, 2 Jan 2000,
Yes, this is a very good point. Jordan, which is it?
On Fri, 7 Jan 2000, Peter Jeremy wrote:
> On 2000-Jan-07 01:43:09 +1100, Steve Ames <[EMAIL PROTECTED]> wrote:
> > _FEATURE_ freeze is January 15th.
>
> Not quite - Jordan specifically stated _CODE_ freeze (see the Subject:).
>
> Maybe I
Hmm! Better hold the 4.0 Code Freeze until this sorts out!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Umm- I know I've done this before, but maybe this is something stupid I've
forgotten I went home to my shiny new 400Mhz intel with the 40GB IBM
drive in hand.. I'd pulled a couple of the 4.0 snapshot floppy sets off
off current.freebsd.org... boot the floppies- they see the de0 card I have
in
This shouldn't be a PNP-OS issue because this is a PCI card- the card is
seen during booting- which means it's getting detected. I don't know why
'ifconfig -l' doesn't see it though.
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the messag
ksys card.
>
> Tom Veldhouse
> [EMAIL PROTECTED]
>
> On Fri, 7 Jan 2000, Matthew Jacob wrote:
>
> >
> > This shouldn't be a PNP-OS issue because this is a PCI card- the card is
> > seen during booting- which means it's getting detected. I don't
1) Alpha's don't have a trap.h...
2) Why are derived files ending up in the source tree? Yes, this is after a make
obj.
--
>>> stage 1: bootstrap tools
--
cd /usr/src; MAKEO
Has been fixed, approx 1700 EST.
On Mon, 17 Jan 2000, bush doctor wrote:
> >From sources cvsup around 14:00 EST ...
>
> cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src/secure/usr.bin/openssl -DNO_RSA
>-DNO_SSL2 -I/usr/obj/usr/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o
>ciphers.o c
> On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
> > fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Agreed. For a PCI card all I want to know is what it is, and what IRQ it
> was assigned. A single line should b
>
> What would be nice would be to have the normal version displayed and
> the verbose stuff go to a seperate buffer and logged seperatly..
>
> ie so you don't clutter your boot screen with junk, but if you have a
> problem you can get at the verbose info :)
>
> .. and no I don't have any patc
On Tue, 18 Jan 2000, David O'Brien wrote:
> On Tue, Jan 18, 2000 at 06:10:00PM -0800, Matthew Jacob wrote:
> > > Agreed. For a PCI card all I want to know is what it is, and what IRQ it
> > > was assigned. A single line should be suffient.
> >
> > Do
> The IRQ is useful to me at least, since the ISA/PCI irq distribution is
> rather hackish and non-trivial to get right at times.
Note that I'm not saying that IRQ is not useful - I'm just asking whether it's
important to see when bootverbose == 0.
To Unsubscribe: send mail to [EMAIL PROTECT
> On Sat, Jan 22, 2000 at 09:01:36PM +0100, Jeroen Ruigrok/Asmodai wrote:
> > -On [2122 15:22], Nick Hibma ([EMAIL PROTECTED]) wrote:
>
> > > - update HARDWARE.TXT
>
> Urgh...
>
> > doing them or mdoc if someone wrote the bare text. But if someone takes
> > this task from my shoulders,
>From a kernel built over the last day or so, alpha, ata disk:
Debugger() at Debugger+0x2c
panic() at panic+0x100
initiate_write_inodeblock() at initiate_write_inodeblock+0x40
softdep_disk_io_initiation() at softdep_disk_io_initiation+0xac
spec_strategy() at spec_strategy+0x48
bwrite() at bwrite
>
> It will only work at Ultra2 speeds right now, Ultra160 support is coming,
> though.
To be fair, the sym driver already supports Ultra3. And Qlogic Ultra3 support
is coming too.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It crashes for me a lot. There's some deal about fonts, oddly enough, which
causes it to crash right away- see the installation instructions that come out
when you install communicator-47- it said something about mkfontdir.
It still crashes or wedges for me a lot, though. I tried mozilla, and th
>
> :It crashes for me a lot. There's some deal about fonts, oddly enough, which
> :causes it to crash right away- see the installation instructions that come out
> :when you install communicator-47- it said something about mkfontdir.
> :
> :It still crashes or wedges for me a lot, though. I tr
> This patch is the first step towards the stackable BIO system as
> sketched out on http://www.freebsd.org/~phk/Geom/
>
> Please test & review.
There's no code to test- it's just a sketch. It's fine as a start, but it's
important that you clarify the role of node device drivers in informing the
On Mon, 13 Mar 2000, Matthew Jacob wrote:
> > This patch is the first step towards the stackable BIO system as
> > sketched out on http://www.freebsd.org/~phk/Geom/
> >
> > Please test & review.
{ as Poul reminded me, I missed the header line that had the patch
> On Wed, Sep 15, 1999 at 09:16:03AM +0100, Doug Rabson wrote:
> > I will be there and I'm happy to support anyone's presentation by
> > answering the 'hard' questions. I don't think I have enough time to
> > prepare anything myself but since the schedule is full, that isn't a
> > problem :-).
>
I just ran across this:
Debugger("isp_attach")
Stopped at Debugger+0x37: movl$0,in_Debugger
db> cont
whoa, other_cpus: 0x0002, stopped_cpus: 0x
panic: stop_cpus() failed
mp_lock = 0002; cpuid = 0; lapic.id =
Automatic reboot in 15 seconds - press a key on the c
Thanks, that did the trick.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I don't seem to see (after not looking very hard) any ASSERT macros for
the kernel in FreeBSD. It'd be pretty easy to add them, and they're
awfully useful. They're different from INVARIANT support in that they
encapsulate (and panic if the assertion is triggered) more inline types of
conditions.
> :I don't seem to see (after not looking very hard) any ASSERT macros for
> :the kernel in FreeBSD. It'd be pretty easy to add them, and they're
> :awfully useful. They're different from INVARIANT support in that they
> :encapsulate (and panic if the assertion is triggered) more inline types of
While I don't dispute that the change rolling/rollout fixed what you see,
I'd have to say that if they're related there are *far* more serious
problems in there.
> (da0:ahc0:0:0:0) data overrun detected in Data-In phase. Tag = 0x8
> (da0:ahc0:0:0:0) Have seen Data Phase. Length = 0, NumSGs = 1
I have a very wierd case of a Dual PPRo SuperMicro board (two PCI
busses) and when running -stable, I/O through boards on the second PCI bus
is *really* delayed.
Any notion on this? -verbose boot stuff below...
-matt
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 19
This just started happening over the last day... It's blowing up during
probing because the frame pointer is getting nuked... this is a 2xPPro
machine.
The code in question is:
static u_int64_t
isp_get_portname(isp, loopid, nodename)
struct ispsoftc *isp;
int loopid;
int
Huh?
I'll check it out..
On Sun, 10 Oct 1999, Andy Farkas wrote:
>
> Just a reminder I guess,
>
> # uname -v
> FreeBSD 4.0-CURRENT #0: Sun Oct 10 16:16:34 EST 1999
>
> # mt retension
>
> console emits (in bright white):
>
> WARNING: driver sa should register devices with make_dev() (dev_
This is a harmless message for the moment. I took a look at the new
make_dev stuff- it's more than a no-brainer to add because there's a lot
of stuff about supported device nodes, etc... I'll try and get back to
this after FreeBSDcon.
On Sun, 10 Oct 1999, Andy Farkas wrote:
>
> Just a reminder
On Tue, 12 Oct 1999, Daniel C. Sobral wrote:
> Matthew Jacob wrote:
> >
> > This is a harmless message for the moment. I took a look at the new
> > make_dev stuff- it's more than a no-brainer to add because there's a lot
> > of stuff about supported device n
> "This time of the year" == "This time in the release cycle"
>
> If we want to have a somewhat clean line before 4.0 now is the time
> to push it through, not after the code freeze.
And could you mention when the code freeze might be so that some of us
could plan our work? Perhaps I've missed s
On Tue, 12 Oct 1999, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Matthew Jacob
>writes:
> >> "This time of the year" == "This time in the release cycle"
> >>
> >> If we want to have a somewhat clean line before 4.0
Just a followup question on my question from a week ago or so ther was
indeed a stack overflow I'd guess- I check the code path more carefully
and there was a 2KB stack buffer there (oof)- and removing it seemed to
make the problem go awaySo the question here is "Shouldn't this have
been
Uh, no, don't do that. There are still a lot of 386/486 machines out
there. And perhaps stronger enforcement (and I'm a culprit at this) of
drivers being quite unless bootverbose is set would be better.
On Thu, 14 Oct 1999, Alexey Zelkin wrote:
> hi,
>
> I propose to increase default value of
Well, a DDB traceback would help. Failing that, at least what does
0xc101891b correspond to otherwise, it's all ENOGUESS
On Sun, 17 Oct 1999, Michael Reifenberger wrote:
> Hi,
> I got the following crash since a couple of time since upgrading one machine to
> -current as of today. It s
Doesn't tell *me* a lot maybe a broken driver that's a KLD? It looks
like something from spec_strategy is being called that's not in the
/kernel space- could be a KLD- are your KLDs up to date for the new
kernel? Like, is this vinum perhaps?
> On Sun, 17 Oct 1999, M
Try it w/o vinum, procfs and nfs kernel objects.
On Mon, 18 Oct 1999, Michael Reifenberger wrote:
> On Mon, 18 Oct 1999, Bernd Walter wrote:
> ...
> > What kind of modules were you running?
> (nullum)(root)# kldstat
> Id Refs AddressSize Name
> 17 0xc010 1eb518 kernel
> 2
Odd you should mention this. I have two cards and a plea from a customer
to port it...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Of all the gin joints in all the towns in all the world, John Reynolds~
> had to walk into mine and say: >
>
> > A friend just passed this along:
> >
> > http://www.newsalert.com/bin/story?StoryId=Coa6pWbKbyte0mtu
> >
> > Intel PRO/1000 Gigabit support for Linux. Source code too (non-GP
853 ?? Is 0:00.02 /bin/sh -c $HOME/bin/Nightly-FreeBSD-Build
855 ?? I 0:00.01 /bin/sh /home/mjacob/bin/Nightly-FreeBSD-Build
857 ?? I 0:00.02 sh ./DOMAKE buildworld
858 ?? I 0:00.03 make buildworld
861 ?? I 0:00.00 /bin/sh -ec cd /usr/src; make -f Make
On Sat, 23 Oct 1999, Matthew Dillon wrote:
> :It really is vgring hanging on a file:
> :
> :vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms
> :
> :A plain vgrind -f on this file also hangs. Anyone have a clue on this?
> :
> :This happens for me on an alpha.
> :
> :-ma
On Sat, 23 Oct 1999, Matthew Dillon wrote:
> :It really is vgring hanging on a file:
> :
> :vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms
> :
> :A plain vgrind -f on this file also hangs. Anyone have a clue on this?
> :
> :This happens for me on an alpha.
> :
> :-mat
You know, I noticed this also yesterday, but with a current as of
yesterday. It wasn't a complete hang. Eventually it recovered and went
into sbwait. The filesystem in question was a 32k/8k fs. I remade the
filesystem into 8k/1k, and things went better, but also then went onto
other things (the
I have the following setup for an alpha PC164 running a current -current
(as in a kernel from the last day):
farrago.feral.com > mount
/dev/da0a on / (ufs, local, writes: sync 608 async 3306)
procfs on /proc (procfs, local)
mfs:30 on /tmp (mfs, asynchronous, local, writes: sync 2 async 7)
bird:/
Hmm. Could be. That's a good thing to try. The connection is a Full Duplex
100BaseT to a 3com switch (both alpha/freebsd && Solaris) so what you
suggest Just Didn't Occur To Me (tm). Thanks
On Thu, 28 Oct 1999, Matthew Dillon wrote:
> :Okay- I went home and left a cvs update going on /usr/
UDP. Local network. Very puzzling.
On Thu, 28 Oct 1999, Andrew Gallatin wrote:
>
> Matthew Jacob writes:
> >
> > Hmm. Could be. That's a good thing to try. The connection is a Full Duplex
> > 100BaseT to a 3com switch (both alpha/freebsd && S
WARNING: / was not properly dismounted
start_init: trying /sbin/init
swapon: adding /dev/ad0b as swap device
Automatic reboot in progress...
/dev/rwd0s4a: 2199 files, 38154 used, 209893 free (277 frags, 26202
blocks, 0.1% fragmentation)
[HANGS...]
^Cfsck in free(): warning: page is already free.
On Sat, 30 Oct 1999, Poul-Henning Kamp wrote:
>
> This has nothing to do with blockdevs. It is an old standing bug in fsck
> which only happens when you interrupt it. "Uncle Milt" from vicor has a
> set of fsck patches in for review with Kirk where this should be fixed
> as well.
>
> In all
The design phase for FreeBSD 4.0 is coming to a close. There are a couple
of things I'm planning on (belatedly) for the SCSI tape driver. I'd like
feedback and suggestions about these and other things, so pass 'em my way.
One change I'm thinking about is probably controversial, so I'd like to
get
>
> There seems to be a great amount of confusion about the 2 EOF marks on
> tapes. It has nothing to do with physical EOT, even the 556BPI 1/2"
> tape drives on an IBM 1401 can detect physical EOT. The problem is
> with LOGICAL EOT, most tape drives do not have a logical EOT write
> command, e
Reread/reresponse, sorry- ENOCOFFEE:
> >
> > 1 filemark can not be used for EOT, it is EOF, you can't tell if what you
> > read next is another file or not that may have been left by a previosly
> > longer usage on the tape.
> >
Well, read until *BLANK CHECK* seems to be what the driver can
On Mon, 15 Nov 1999, Rodney W. Grimes wrote:
> >
> > Reread/reresponse, sorry- ENOCOFFEE:
> >
> >
> > > >
> > > > 1 filemark can not be used for EOT, it is EOF, you can't tell if what you
> > > > read next is another file or not that may have been left by a previosly
> > > > longer usage on
Okay- I hear you both.
What do you do with QIC drives which cannnot write 2FM then?
On Mon, 15 Nov 1999, Bob Bishop wrote:
> Hi,
>
> At 11:01 am -0800 15/11/99, Matthew Jacob wrote:
> >I repeat what I said in other mail- can you actually show me a tape drive
> >where
On Mon, 15 Nov 1999, Rodney W. Grimes wrote:
> >
> > Okay- I hear you both.
> >
> > What do you do with QIC drives which cannnot write 2FM then?
>
> Can you give me a model of a QIC drive that has the ``can't write 2 FM's''
Just about all. For that matter, it isn't just QIC drives- see all
>
> Every night, I do a partial backup, one file on tape for each file
> system, about 12 in all. Subsequently I read the tape and list
> contents until I hit EOT. OK, the first time I use a tape, there will
> be nothing behind it. But the next time, the total length of tape
> written may be s
> >
> > Sorry, no. When you write a tape with these devices there's always a
> > leading erased area. That's why if you overwrite the front a tape you
> > can't skip past this area to recover data you really need. A misfeature of
> > modern technology.
>
> Is this anchored in the standards? Wha
Too many people have objected. I didn't make my case clearly enough, but
because enough people of have raised issues, the default won't be changed.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, 16 Nov 1999, Greg Lehey wrote:
> On Tuesday, 16 November 1999 at 8:04:05 -0800, Matthew Jacob wrote:
> >
> > Too many people have objected. I didn't make my case clearly enough,
> > but because enough people of have raised issues, the default won't
>
On Sat, 20 Nov 1999, J Wunsch wrote:
> Matthew Jacob <[EMAIL PROTECTED]> wrote:
>
> > Too many people have objected. I didn't make my case clearly enough,
> > but because enough people of have raised issues, the default won't
> > be changed.
>
&
Well, I'm *almost* there getting this driver to work well (it's now
*just* managing to run without barfing all over memory). It's been a
humiliating experience- I'm just not that hot with Network drivers as I
spend most of my time in mass storage. This chipset is, uh, interesting
too (as best as
Well, I am truly f*cked now. I read enough of this thread, saw nothing new
in UPDATING, and did the following:
alpha
kernel from today
MAKEDEV from today
(but not a make world install- the binaries/libs are ~week old)
cannot get out of single user mode. fsck core dumps.
> Can't you boot from the old kernel? Or have you already wiped the
I can boot the old kernel. A MAKEDEV using the new MAKEDEV has now wiped
all block devs, so swapon, etc. ,fail.. However, this is the conundrum-
it's not safe to do a 'make installworld' on a two week old kernel, but
the new ke
s to feature freeze for 4.0 it is very hard for some of us who attempt
to make sure things we deliver actually work on both platforms if the
second platform is broken. I'm plenty pissed off, but, c'est la vie...
-matt
On Thu, 2 Dec 1999, Matthew Jacob wrote:
>
> Well, I am t
(removed from general list)
> Slow down. You are getting screwed by a combination of things. It
> isn't all phk's fault.
>
> The bdev elimination is one factor, but the most important one (the
> fsck/mount segv) is due to int/long breakage introduced version 1.85
> of mount.h. This happened
> Well, I wasn't back in town until last night with 5000 messages to catch
> up on. Sorry for not getting your questions first.
>
> There are other things broken too. Oh well- I really shouldn't get wired.
> *BSD will get taken as a serious effort as much as it deserves based upon
> what actual
I realize that I have been much more upset and unpleasant about this than
the situation warranted, and I would like to extend my apologies to all
and sundry for venting my frustration so publicly.
-matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
> In message <[EMAIL PROTECTED]>, Matthew
> Jacob writes:
> >
> >Well, I am truly f*cked now. I read enough of this thread, saw nothing new
> >in UPDATING, and did the following:
> >
> >alpha
> >
> > kernel from today
> > M
> In message <[EMAIL PROTECTED]>, Matthew
> Jacob writes:
> >
> >Sorry- maybe more of an edge case. It really has to do with 'ad' support
> >seemingly vanishing from the alpha. Or, rather, it's hard to say exactly
> >what has happened:
>
With todays' build, the previous problems went away. Other problems have
replaced them (sio's wierd again for alpha), but that's a different
story.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
What is beast? I was happily able to build -current at about 5 this
morning on a pc164.
On Fri, 3 Dec 1999, Jordan K. Hubbard wrote:
> cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/reader.c
> cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/s
Q'uelle strange- what I have... well, we'll see what my nightly build
brings...
On Fri, 3 Dec 1999, Jordan K. Hubbard wrote:
> > What is beast? I was happily able to build -current at about 5 this
> > morning on a pc164.
>
> It's an Aspen systems DEC Durango PC164 motherboard based system.
>
> As Matthew Jacob wrote ...
> >
> > Q'uelle strange- what I have... well, we'll see what my nightly build
> > brings...
>
> Mine fell over in 'truss'. I already reported it to Marcel, looks
> like something was changed in kdump/mkioctls, a sc
It seems that in the latest running around with things, disklabel -W
doesn't seem to quite work, at least on the alpha- it seems to set the
label writable, but the next attempt to open the disk sets the label area
non-writable again.
Before I go tracking this down as a bug, is it?
Secondly, how
Wow. Okay.
On Mon, 6 Dec 1999, Bruce Evans wrote:
> On Sat, 4 Dec 1999, Matthew Jacob wrote:
>
> > It seems that in the latest running around with things, disklabel -W
> > doesn't seem to quite work, at least on the alpha- it seems to set the
> > label writable,
Good, but like just having popcorn for dinner, somehow unsatisfying...
On Sun, 5 Dec 1999, Garrett Wollman wrote:
> < said:
>
> > So, what's the answer about what to do?
>
> exec 3 dislabel -W xx0
> spam /dev/xx0
> exec 3<&-
>
> -GAWollman
>
> --
> Garrett A. Wollman | O Siem / We are al
Sorry- I missed it. I was in Kaui.
On Sun, 5 Dec 1999, David O'Brien wrote:
> > It seems that in the latest running around with things, disklabel -W
> > doesn't seem to quite work, at least on the alpha- it seems to set the
>
> This was the topic of my "Fscking disklabel crap" mail to freebsd-
Well, there *are* workarounds, but I agree that this is broken. I think we
had better fix disklabel somehow. I'm just wary of leaping in to 'do it',
because I'm sure I'll break more than I fix.
On Sun, 5 Dec 1999, David O'Brien wrote:
> On Mon, Dec 06, 1999 at 02:50:43AM +1100, Bruce Evans wrot
>
> How do we fix this problem? I keeps from from
> ``dd if=/dev/da1 of=/dev/da2'' ?? I was very peeved at having to put the
> disks on a Solaris box to do such a normal Unix task.
this will fix your dd
Index: dd.c
===
RCS file
Happens to me every boot. And I'm up to date with all binaries and kernel.
I don't have softupdates on the root filesystem.
On Mon, 6 Dec 1999, Mike Smith wrote:
> > On Mon, 6 Dec 1999, Nick Hibma wrote:
> >
> > > Most probably this is exactly the problem I was describing to you a
> > > couple
On Tue, 7 Dec 1999, Luoqi Chen wrote:
> > I've seen this exact same thing before too. In fact it was two rather
> > annoying things, one being a single solitary last buffer that wouldn't
> > sync and thus left the whole fs marked dirty, and then fsck would check
> > it, see it was fine, but moun
> On Wed, Dec 15, 1999, George Michaelson wrote:
> > Why do we have to make FreeBSD more like HP-UX? the most sucky UNIX ever
> > invented apart from AIX?
Hmmph. When FreeBSD has a fully SMP-ized kernel, including filesystem and
network stacks and device drivers, and when it has something that
On Wed, 15 Dec 1999, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Daniel C. Sobral" writes:
> >"Rodney W. Grimes" wrote:
> >>
> >> Yea... been hearing that for 4 years... one of it's big short comings is
> >> that it needs a persistent backing store for this. Sounds like this C
>
> I would really like to see the devd functionality to live in init
> and at the same time I wouldn't mind if init were taught to keep
> important programs running, things like sshd, inetd, syslogd and
> similar should be restarted if they die.
>
> No, I don't want sysV runlevels or the weird
> >Isn't this throwing an awful lot onto init?
>
> Not really...
>
> The meta-daemon part is no different from keeping gettys in the air...
>
> The devd thing consists of selecting on some magic fd and running a
> program when something happens. This could be done with a getty
> like daemon to
> >
> >I was just thinking it could get tricky and have subtle ordering bugs of
> >new tty devices, changes to ttys and signals all about the same time.
>
> Well, they are no less subtle by having them in different processes...
No, but possibly easier to track and debug. Just a minor nit. N'mind
> But lets say you add a pccard on which you want a getty, so devd will
> have to tell init to run a getty on that port wouldn't it ?
Of course- but this lays out very clearly where breakage
could occur and leads to be better flexibility. Let's assume this is devd
and leave to the side whether d
Huh? What about the impact on all ntp.conf files? Or is this seamless?
On Thu, 16 Dec 1999, Ollivier Robert wrote:
> This is a HEADSUP message to warn all current users that tha following is
> being done:
>
> - disable xntpd build
> - enable ntp build
> - removal of old xntpd/xntpdc binaries
fyi
-- Forwarded message --
Date: Thu, 16 Dec 1999 12:15:48 -0500 (EST)
From: Paul B. Brown <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Linux vs. OpenBSD vs. FreeBSD vs. NetBSD
Resent-Date: 16 Dec 1999 17:15:54 -
Resent-From: [EMAIL PRO
Thanks for the very clear writeup of what we can expect. I'm happy.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
1 - 100 of 610 matches
Mail list logo
