On Sat, 5 Oct 2002, Steven G. Kargl wrote:
> I came to the same conclusion after I sent the original email.
>
> What I don't understand is how I ended up in ffs_snapshot(), because I
> don't have a snapshot of /var. I tried snapshots when Kirk first
> introduced the feature, but I removed all
In case you are foolishly tracking -current without reading the CVS logs,
you might want to be aware that the default just changed such that you get
GEOM unless you explicitly specify NO_GEOM in your kernel configuration
file. The pre-defined kernel configs in the base tree all specify
NO_GEOM,
On Sun, 6 Oct 2002, fergus wrote:
> i have a crash dump for this now if anyone is interested. it's not
> exactly the same trace as it seems to originate from a VOP_LINK request
> this time but i guess it's the same problem.
To be honest, it sounds like something is simply leaking kernel
memory
On Sun, 6 Oct 2002, Carl Schmidt wrote:
> > Mounting root from ufs:/dev/ad0s1a
> >
> > and hangs -- only a physical reset works. However, breaking into the
> > debugger, and running a trace, I get (hand-copied):
Hmm. I actually ran into this problem on some diskless booting boxes, but
it wen
On Sun, 6 Oct 2002, Seth Hieronymus wrote:
> Thanks for the pointers. Here's the trace 1:
> mi_switch(c0bb9988,14,c01bbe60,c0bb98f0,1) at mi_switch+0x290
> msleep(c03778a0,0,68,c03153d7,14) at msleep+0x477
> g_waitidle(1,c0314e10,c18f2885,c031bd64,c0b8dc20) at g_waitidle+0x8b
> g_dev_clone(0,c1
On Mon, 7 Oct 2002, suken woo wrote:
> xdm broken on current when login . i knew this is the pam module
> problem,but how could i fix it?
Chances are, you built your X11 with an old -CURRENT system, and since
then the ABI for the PAM stuff has changed in -CURRENT, so your old X11 no
longer talk
On Mon, 7 Oct 2002, suken woo wrote:
> >>xdm broken on current when login . i knew this is the pam module
> >>problem,but how could i fix it?
> >
> >Chances are, you built your X11 with an old -CURRENT system, and since
> >then the ABI for the PAM stuff has changed in -CURRENT, so your old X11 n
On Mon, 7 Oct 2002, Joel M. Baldwin wrote:
> Shouldn't ALL of the files in /bin, /usr/bin, /usr/include, /usr/lib etc
> be replaced during an installworld?
>
> I've always looked for files older than the last installworld and moved
> them aside thinking that they're obsolete.
>
> ( aside, no
On Wed, 9 Oct 2002, walt wrote:
> > ===> usr.bin/truss
> > syscalls.master: line 34: syscall number out of sync at 0
>
> I see this too. The last time it was broken awk (IIRC) that was
> responsible, though it doesn't seem likely this time.
Looks like there was a merge problem with Peter's r
Wonderful. Your work on the toolchain is much appreciated!
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
On Thu, 10 Oct 2002, Alexander Kabaev wrote:
> I am going to import a new GCC 3.2.1 snapshot in about 10 minute
I've run into this on a couple of boxes, but those boxes were diskless
root boxes, and used md backed ffs for /tmp and /var. Apparently if you
do that, you're likely to exceed the kernel's auto-tuned kmem map size.
That said, they didn't do it as frequently, so perhaps there's been a
chance. A g
Yeah, this is a Known Problem, and it's quite unfortunate, actually. I
looked at trying to solve it -- changing the types respectively to uid_t,
gid_t, and mode_t, but it involved a lot of ABI munging because the
structures are shared between the userland interface and the kernel
implementation.
On Tue, 15 Oct 2002, Danny J. Zerkel wrote:
> At least for our Linux emulation layer, supporting IPC_64 would be one
> of the pieces (probably the main one) keeping The Sims from running.
> The other thing we are missing is the Linux ioctl() interface for
> reading MSDOSFS directories, but that
On Wed, 16 Oct 2002, Maxim Sobolev wrote:
> What about source-level compatibility, which IMO is a good thing, at
> least if it doesn't add too much complexity (it clearly doesn't in this
> case)? Also, handling single flag should be easier from the coding
> perspective than a load of new values,
On Wed, 16 Oct 2002, Maxim Sobolev wrote:
> > And it's not like the approach you've described makes it any easier to
> > implement: you still have to break out the old and new structures since
> > changing ipc_perm breaks the ABI for all of the System V interfaces,
> > rewrite the kernel code, e
On Wed, 16 Oct 2002, Terry Lambert wrote:
> Robert Watson wrote:
> > I'm not convinced there's any value to providing the backward
> > compatibility that has to be asked for: the only benefit to the current
> > short-based API is that it allow serious security ho
I upgraded one of my older boxes with a Linksys ethernet card this
evening, and was a bit surprised to see this in dmesg:
dc0: port 0xe800-0xe8ff mem
0xfebfff00-0xfebf irq 9 at device 19.0 on pci0
dc0: Ethernet address: 00:00:00:00:00:00
miibus0: on dc0
dcphy0: on miibus0
dcphy0: 10baseT,
On Mon, 21 Oct 2002, Lars Eggert wrote:
> lock order reversal
> 1st 0xc791bc00 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465
> 2nd 0xc04974e0 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2156
It strikes me that, for better or for worse, the reported "reversal" is
the r
On Mon, 21 Oct 2002, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Robert Watson <[EMAIL PROTECTED]> writes:
> : dc0: port 0xe800-0xe8ff mem
> : 0xfebfff00-0xfebf irq 9 at device 19.0 on pci0
> : dc0: Ethernet address: 00:00:00:00:00:0
On Mon, 21 Oct 2002, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Robert Watson <[EMAIL PROTECTED]> writes:
> : dc0: port 0xe800-0xe8ff mem
> : 0xfebfff00-0xfebf irq 9 at device 19.0 on pci0
> : dc0: Ethernet address: 00:00:00:00:00:0
Are you using UFS1 extended attributes on that box? I suspect there might
be a bug involving the open flags passed to extended attribute backing
vnodes such that a remount is refused because there are existing vnodes
opened writable. I.e., the extended attribute backing files are opened
FREAD|FWR
I think UPDATING hasn't been updated on this, but there was a change in
the format printing for printf that conflicts with the ddb format
printing. You need to rebuild your gcc.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laborato
Hmm. I haven't experienced this with my 5.0 boxes not running
WITNESS/INVARIANTS/etc, but I'm updating a box to give it a try.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
On Tue, 29 Oct 2002, John De Boskey wrote:
On Sun, 27 Oct 2002, Sean Kelly wrote:
> On Sun, Oct 27, 2002 at 05:17:44PM -0500, Robert Watson wrote:
> > Are you using UFS1 extended attributes on that box?
>
> Yes.
> (290) smkelly@edgemaster:~$ grep UFS /usr/src/sys/i386/conf/EDGEMASTER
> options
Per our discussion out-of-band, and just for the reference of others who
might have the same question, forced dependencies for rpcbind from ypserv
and ypbind aren't present right now, you can work around by explicitly
enabling rpcbind in rc.conf. You might actually see rpcbind running later
in boo
On Sun, 3 Nov 2002, Miguel Mendez wrote:
> > 2) Security. Can LD_LIBRARY_PATH (or other mechanisms)
> > be used to deliberately subvert any of these programs?
> > (especially the handful of suid/sgid programs here)
> ..
>
> I can't come up right now with an idea of how exploiting LD_LIB
On Sun, 3 Nov 2002, Robert Watson wrote:
> On Sun, 3 Nov 2002, Miguel Mendez wrote:
>
> > > 2) Security. Can LD_LIBRARY_PATH (or other mechanisms)
> > > be used to deliberately subvert any of these programs?
> > > (especially the handful of suid/sgid
On Fri, 8 Nov 2002, Dan Pelleg wrote:
> I'm trying to use setfacl - just the example that's in the manpage. All
> I ever get is: setfacl: acl_get_file() failed: Operation not supported
This error generally results from three cases:
(1) UFS_ACL isn't enabled
(2) Extended attributes aren't avail
On Fri, 15 Nov 2002, Sheldon Hearn wrote:
> On (2002/11/15 09:48), Soeren Schmidt wrote:
>
> > > Don't you think it makes more sense for the kernel to start off with
> > > more restrictive permissions, and have the administrator determine
> > > whether more restrictive permissions are appropriat
On Fri, 15 Nov 2002, John Baldwin wrote:
> On 15-Nov-2002 Wesley Morgan wrote:
> > On Fri, 15 Nov 2002, Vallo Kallaste wrote:
> >
> >> Just finished '-j2 buildworld' and it did well with kernel which had
> >> the options enabled. Therefore I suppose that those options are
> >> still absolutely n
On Sun, 17 Nov 2002, Thierry Herbelot wrote:
> Even make -j1 buildworld with the SMP kernel ends with a complete freeze
> of the machine (the kernel does not go to a panic where I could try a
> backtrace)
I've seen several reports that using a serial break to get into ddb is now
quite a bit mor
I ran into that during heavy builds on one of my boxes a few months ago --
I never really got around to properly debugging it because the UFS file
systems promptly ate themselves. Oddly, I had two boxes in particular
that this happened on, and none of my others, and it wasn't clear to me if
there
Hmm. It looks like there is indeed a lock leak in the RFTHREAD code.
Maybe a change like the following might help:
PROC_LOCK(p2);
psignal(p2, SIGKILL);
PROC_UNLOCK(p2);
}
Change the } to:
} el
On Tue, 19 Nov 2002, Bruce Evans wrote:
> > No, the default permissions are specified in the driver source code
> > via make_dev().
>
> The drivers only get the magic numbers for uids and gids from a central
> file. This is bad enough. I think all devices should have ownership
> root:wheel and
On Tue, 19 Nov 2002, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Robe
> rt Watson writes:
>
> >> > No, the default permissions are specified in the driver source code
> >> > via make_dev().
> >>
> >> The drivers only get the magic numbers for uids and gids from a central
> >> fil
Hmm. Another thread has decided to sleep while holding an inpcb mutex.
Any chance this can be reproduced while running WITNESS? If so, you
should get a panic earlier when the other thread sleeps in the first
place. The easiest way to do that is if you can reproduce the panic with
WITNESS. If y
On Wed, 20 Nov 2002, Robert Watson wrote:
> Hmm. Another thread has decided to sleep while holding an inpcb mutex.
> Any chance this can be reproduced while running WITNESS? If so, you
> should get a panic earlier when the other thread sleeps in the first
> place. The easiest wa
This is not actually DP2, it's about a week earlier. That said, I'm not
sure that bug was fixed in the missing week. If you can, try booting off
of the 5.0-DP2 ISOs found at:
ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-i386/5.0-DP2
Or using the floppies:
ftp://ftp.FreeBSD.org/pub/FreeBSD/
On Wed, 20 Nov 2002, Vallo Kallaste wrote:
> Get the live-5.0-CURRENT-20021119-JPSNAP.iso from current.freebsd.org
> and burn it. Boot from it (P4), watch it complaining about unable to
> load acpi.ko module at bootup. Exit from fixit mode and get fully up and
> running. Change to /boot/kernel and
On Wed, 20 Nov 2002, Steve Kargl wrote:
> NetBSD.org has a security advisory about potential problems with their
> ftpd. If this is part of lukemftp, then the issue of removing/updating
> lukemftp needs to be addressed for FreeBSD 5.0 RELEASE.
>
> ftp://ftp.netbsd.org/pub/NetBSD/security/advis
On Wed, 20 Nov 2002, Joel M. Baldwin wrote:
> --On Wednesday, November 20, 2002 12:01 PM -0500 Robert Watson
> <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 20 Nov 2002, Robert Watson wrote:
> >
> >> Hmm. Another thread has decided to sleep while holding an inpcb
On Wed, 20 Nov 2002, Chris Howells wrote:
> Hi,
>
> On Wednesday 20 November 2002 5:08 pm, Robert Watson wrote:
> > dmesg is a command that dumps the kernel message buffer. You can
> redirect
> > the output to a file:
> >
> > dmesg > fileofchoic
On Wed, 20 Nov 2002, John Baldwin wrote:
> Erm. Did you manage to look at dmesg then? If so, you would have seen
> warnings from WITNESS earlier about the locks messing up. If you can
> reproduce this and are letting it sit unattended, a better plan might be
> to turn on witness_ddb (it's a ke
The build of netncp is currently broken on 5.0-CURRENT, and I'd like to
see this fixed before 5.0-RELEASE. Unfortunately, we're having a lot of
trouble finding a test environment, which is the natural and immediate
follow-on to the compile fixes :-). Was wondering if anyone with FreeBSD
kernel d
On Thu, 21 Nov 2002, Robert Watson wrote:
> The build of netncp is currently broken on 5.0-CURRENT, and I'd like to
> see this fixed before 5.0-RELEASE. Unfortunately, we're having a lot of
> trouble finding a test environment, which is the natural and immediate
> follow-o
On Fri, 22 Nov 2002, Brad Knowles wrote:
> At 5:23 PM -0500 2002/11/21, Robert Watson wrote:
>
> > (And, you have to bring your own test environment, as the second sentence
> > suggests, but doesn't actually state).
>
> Over on -chat, we're in the
In terms of where to take this: there are many reported problems with
smbfs on 5.0-CURRENT. It's not clear whether this is left over from the
KSE imports, the Apple-derived fixes that might not have fixed things,
etc. In any case, before we can look at smbfs install, we really need
smbfs working.
On Thu, 21 Nov 2002, Juli Mallett wrote:
> I'm getting a giant owned assertion failure in the vm_map code, simply
> by running "doscmd something.exe" where something.exe is a
> self-extracting ZIP file (of BIOS upgrade stuff, FWIW), which leads
> trivially to tripping over it. I still don't have
On Fri, 22 Nov 2002, Richard Tobin wrote:
> Somewhere there should be a warning that the root partition needs to be
> *much* bigger in 5.0 than in 4.x. It's gone from 40-something MB to 92
> MB for a default install. It's really frustrating to install a system
> and find that / is 104% full.
On Fri, 22 Nov 2002, Brad Knowles wrote:
> > If I might suggest: there's a freebsd-qa mailing list. It's a great place
> > to organize QA efforts, whereas freebsd-chat is notorious for its lack of
> > signal (it's where dead signals go to rot).
>
> There's been some talk of freebsd-qa,
On 22 Nov 2002, Dhee Reddy wrote:
>Just tried to look up some info and saw that the /proc filesystem
> doesn't
>contain any files.
>Shouldn't they contain entries correcponding to all the processes
> ? truely -- dhee
In fresh 5.0 installs, procfs is not enabled by default. Rig
On Fri, 22 Nov 2002, Martijn Pronk wrote:
> >The build of netncp is currently broken on 5.0-CURRENT, and I'd like to
> >see this fixed before 5.0-RELEASE. Unfortunately, we're having a lot of
> >trouble finding a test environment, which is the natural and immediate
> >follow-on to the compile fix
On Fri, 22 Nov 2002, walt wrote:
> I noticed David Xu's changes to libpthread this morning, so I did a
> "make libraries" and noticed with surprise that libpthread.so.5 was
> still dated Sep 16.
>
> I then did 'cd /usr/src/lib' and a 'make' and noticed that libpthread
> did not show up during th
On Thu, 21 Nov 2002, Luigi Rizzo wrote:
> [Bcc to -net because it is relevant there. This email has been triggered
> by a private discussion i was having with other committers (who will
> easily recognise themselves :) which suggested the possibility of adding
> more fields to mbuf headers]
>
>
On Fri, 22 Nov 2002, Mike Barcroft wrote:
> Dhee Reddy <[EMAIL PROTECTED]> writes:
> > Hello all.
> >Just tried to look up some info and saw that the /proc filesystem doesn't
> >contain any files.
> >Shouldn't they contain entries correcponding to all the processes ?
> > truely
>
Dima,
I recently switched two of my diskless crash boxes over to rc.d from the
old rc scripts, and discovered that the new rc.diskless code uses mdmfs.
Unfortunately, it doesn't appear to support UFS2, since the newfs "-O"
flag isn't supported -- and it isn't quite so simple to add, since mdmfs
On Fri, 22 Nov 2002, Juli Mallett wrote:
> > This is expected behavior -- libpthread is currently disconnected from the
> > build. I'd actually like to see it connected to the build, with an
> > appropriate "WARNING: DRAGONS INCLUDED" man page also hooked up to
> > discourage accidental use. At
On Fri, 22 Nov 2002, John Baldwin wrote:
> On 22-Nov-2002 local.freebsd.current wrote:
> > Having installed DP2 and said NO to NFS client and
> > server in sysinstall (and there's nothing about them
> > in /etc/rc.conf) I see four nfsiod daemons running
> > after the first boot. Are they supposed
On Sat, 23 Nov 2002, Christian Brueffer wrote:
> just got this panic on my notebook. Had to manually shut it down after a
> acpiconf -s 4. At the next bootup, the panic occured. At the moment I'm
> trying to boot into my system again to reproduce it.
In general, this panic occurs in the follow
On Sat, 23 Nov 2002, Ertan Kucukoglu wrote:
> First of all, I do not know much about backtracing, debugging etc.
First advice: we shipped DP2 with two different kernels, the normal kernel
without high debugging features, and then a special debugging kernel
called DEBUG. My first advice when st
On Mon, 25 Nov 2002, Mikhail Teterin wrote:
> The only way to get my -current system back to normal after a crash is
> to boot into single user and do an explicit ``fsck -p''.
>
> Otherwise the system will, seemingly, boot fine, but none of the ttyvs
> will accept any input, although tty-switch
On Mon, 25 Nov 2002, Munish Chopra wrote:
> On 2002-11-25 08:30 +, [EMAIL PROTECTED] wrote:
> >
> > http://projects.imp.ch/openoffice/
> >
> > But, i tried to install that package on my FreeBSD 5.0-CURRENT, well it
> > went fine, but when i try to run openoffice, i will get a "Segmentation
On Sat, 23 Nov 2002, Andrew Gallatin wrote:
> I propose that we make struct label portion of the pkthdr compile-time
> conditional on MAC. The assumption is that you will move the MAC label
> to an m_tag sometime after 5.0-RELEASE.
This weekend I spent about six hours looking at what it would
On Mon, 25 Nov 2002, Bosko Milekic wrote:
> On Mon, Nov 25, 2002 at 11:31:39AM -0500, Robert Watson wrote:
> > BTW, do you have any recent large-scale measurements of packet size
> > distribution? In local tests and measurements, the additional 20 bytes on
> > i386 didn
On Mon, 25 Nov 2002, Sam Leffler wrote:
> As I explained to you; the handling of mtags mimics what was there for
> the aux mbufs. I did this intentionally to avoid changes that might
> introduce subtle problems. My intent was to cleanup this stuff after
> 5.0 releases by replacing the pkthdr co
On Mon, 25 Nov 2002, Sam Leffler wrote:
> I don't see this problem; m_getcl appears to do the right thing.
Hmm. I see the SLIST initialization there also. Maybe I'm thinking of
another function, I'll have to go check. Sorry about that.
Robert N M Watson FreeBSD Core Team, Truste
On Tue, 26 Nov 2002 [EMAIL PROTECTED] wrote:
> On Tue, 26 Nov 2002, Hiten Pandya wrote:
>
> > On Tue, Nov 26, 2002 at 11:21:28AM -0700, [EMAIL PROTECTED] wrote the words in
>effect of:
> > > On Tue, 26 Nov 2002, Bruno Miguel wrote:
> > >
> > > > On 25 Nov 2002 at 23:34, [EMAIL PROTECTED] wrote..
ed ACLS on / by doing a tunefs -a
> enable /dev/ad0s1a. I proceeded to try getfacl and setfacl.
>
> getfacl returned the default settings (just stat() in ACL form according
> to Robert Watson), however, no matter what I tried all I could get with
> setfacl -m g:mail:rwx testfile
Andrew,
Thanks for your patience as I finished some research and experimentation
regarding the options there. Some more details below.
On Sat, 23 Nov 2002, Andrew Gallatin wrote:
> On the contrary, I think that if anything is going to be done, it must
> be done now, so as to not break binary n
On Wed, 27 Nov 2002, Bruce Evans wrote:
> On Tue, 26 Nov 2002, Robert Watson wrote:
>
> > tunefs changes the flag for the next mount, so doesn't take immediate
> > effect. Once you've tunefs'd a read-only file system, you need to unmount
> > and remou
On Thu, 28 Nov 2002, Bruce Evans wrote:
> On Wed, 27 Nov 2002, Robert Watson wrote:
>
> > On Wed, 27 Nov 2002, Bruce Evans wrote:
> >
> > > On Tue, 26 Nov 2002, Robert Watson wrote:
> > >
> > > > tunefs changes the flag for the next mount, so doe
On Wed, 27 Nov 2002, Julian Elischer wrote:
> On Wed, 27 Nov 2002, Robert Watson wrote:
>
> > I'd like to continue to explore options for reducing the number of memory
> > allocations to extend storage on mbufs. One idea I've been tossing around
> > is adopti
On Sat, 30 Nov 2002, Michal Mertl wrote:
> I'm now unable to make it dead-lock again. Yet it happened quite easily.
> I had more md backing files in the same directory at the beginning (to
> test Terry's suspicion mentioned in thread 'jail' on hackers@).
I've noticed that chroot() environments
On Sun, 1 Dec 2002, Jake Burkholder wrote:
> Apparently, On Sun, Dec 01, 2002 at 01:15:00PM -0200,
> Daniel C. Sobral said words to the effect of;
>
> > There I go reply to all...
> >
> > IIRC, we never supported upgrade to 4.0 or 4.1 from anybut but the
> > *latest* version in the 3.x s
Base system perl-based tools added to the TODO list. We need to deal with
these ASAP.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
On Sun, 1 Dec 2002, Kris Kennaway wrote:
> On Sat, Nov 30, 2002 at 10:41:28PM -0500,
On Thu, 5 Dec 2002, kai ouyang wrote:
> Hi, everybody,
> >From Robert N M Watson
> >(1) UFS_ACL isn't enabled
> Yes, I am sure that in my kernel config:
> options UFS_ACL
> options UFS_EXTATTR
> options UFS_EXTATTR_AUTOSTART
Ok, looks good.
> >(2) Extended attributes aren't available on the fil
On Fri, 6 Dec 2002, Kris Kennaway wrote:
> I'm getting this too:
>
> Local package initialization:lock order reversal
> 1st 0xc449ad34 filedesc structure (filedesc structure) @
>/local0/src-client/sys/kern/sys_generic.c:901
> 2nd 0xc4146780 pipe mutex (pipe mutex) @ /local0/src-client/sys/ker
On Fri, 6 Dec 2002, Kris Kennaway wrote:
> On Fri, Dec 06, 2002 at 07:18:03PM -0800, Lars Eggert wrote:
>
> > >I'm getting this too:
>
> After discussing this with various people on IRC, it was determined that
> this is not the place where the reversal is occurring, but since witness
> doesn't h
On Sun, 8 Dec 2002, Bruce Evans wrote:
> On Fri, 6 Dec 2002, Archie Cobbs wrote:
>
> > So in summary my recommendation is to add a big warning to the
> > growfs(1) man page that is should not be run on the root partition,
> > even if you have booted single-user mode and haven't mounted / yet.
>
BTW, one upshot of this whole event is that we should probably be
hard-coding the lock order of all important locks rather than allowing it
to be automatically determined. We'd uncover problems of this sort much
faster and much more easily, and it would provide better documentation of
the intended
On Sun, 8 Dec 2002, Alan L. Cox wrote:
> Please remove ENABLE_VFS_IOOPT from your kernel configuration. This
> code has never been safe for general use.
>
> Unfortunately, when it was documented in NOTES, this was fact was
> omitted.
Is the attached diff appropriate, then?
Robert N M Watson
I'm having a recurring problem on a number of machines wherein the fxp
interfaces on those machines will spew out pause packets in vast
quantities while the system is in ddb, or following a shutdown. This
doesn't happen with other operating systems, and only started happening at
some point in the
In the past week, a number of comments have been made both for and against
additional version control mechanisms being used to supplement the FreeBSD
Project official CVS server. Proponents of additional mechanisms, such as
Perforce, have pointed out that CVS doesn't provide the necessary tools
On Sat, 23 Feb 2002, Alfred Perlstein wrote:
> Usually when I see diff(1) output from you I usually expect a commit
> within the next half hour or so, I just wanted to make myself clear on
> the issue. No worries. :)
>
> Yes, and hopefully JeffR's allocator will fix our problems, that is if
>
Ditto here. My Dell notebook has ceased powering off. I've been meaning
to submit a PR along with the dmesg output (plus some of the whining, I
think from ACPI), but just haven't got to it. I'll try to do so tomorrow.
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL P
Hmm. Well, part of the goal of the upcoming development snapshots is to
provide that. On the other hand, I think the reason there has been less
focus on that of late is that -CURRENT is actually quite stable, leaving
aside a few tiny windows (for example, when I broke booting due to messing
up a
ed on
whatever suggestions come out of this work.
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED] NAI Labs, Safeport Network Services
-- Forwarded message --
Date: Sat, 23 Feb 2002 16:28:47 -0500 (EST)
From: Robert Watson <[EMAIL PROTEC
On Tue, 26 Feb 2002, Kevin Way wrote:
> As one of the many people who've done some initial work on the port, I
> can tell you that it seems to me that there's not a lot of interest in
> this project, beyond criticizing the work of those who've made attempts
> to do any work, or attempting to exp
On Tue, 26 Feb 2002, Garance A Drosihn wrote:
> I think the main issue here is how long the real repository can be
> "locked" while waiting for some change to show up. If work can keep
> going into the main repository, then what does anyone care if someone is
> tracking their own personal work
On Tue, 26 Feb 2002, Julian Elischer wrote:
> > On the other hand, you could easily argue that the expectations might be
> > much lower for smaller pieces of work. For example, the move to td_ucred
> > required a substantial amount of infrastructure, but the patches
> > themselves are relativel
On Tue, 26 Feb 2002, Garance A Drosihn wrote:
> That would be me...
>
> I meant "lock" in the sense of expecting no one to make any major
> changes in the same area of code. I seem to remember you asking for
> such a "lock" (to use the term loosely) in July, and the KSE work going
> in around
One of the disagreements that seems to be evolving is whether or not the
project formally supports a task-oriented structure. A couple of people
have asserted that people might claim tasks (such as myself) and by virtue
of claiming the task, be provided with some notion of ownership that is
supp
On Wed, 27 Feb 2002, George V. Neville-Neil wrote:
> I think we need to avoid the concept of "imposing some modicum of
> structure." If we create structure it is because we need it. Just like
> software. There was a good comment recently about "software gets
> created to scratch an itch." I'
On Thu, 28 Feb 2002, George V. Neville-Neil wrote:
> > What I mean by "imposing structure" is:
> >
> > - Identify patterns of development and structure that seem to have evolved
> > naturally as part of the maturing of the FreeBSD Project
> > - Determine which patterns tend to result in the m
On Fri, 1 Mar 2002, Glenn Gombert wrote:
>I have spent several months figuring how to do diskless mounts for
> test kernels, run debuggers from serial terminals and do remote kernel
> debugging with gdb, and spent lots and lots of time doing is as well.
> Some 'up to date' "How To's" are rea
On Thu, 28 Feb 2002, Galen Sampson wrote:
> I am curious about the file sizes of the backing files for extend
> attributes. I have compiled a custom kernel that has both extended
> attribute support and acl support. I can sucessfully add and remove
> acls for files. I am quite impressed. I us
On Tue, 5 Mar 2002, Adam Webb wrote:
> Is there a known bug or particular reason I can't add network aliases in
> -current?
> --
> Adam Webb
None that I know of, although there does seem to be at least one bug
relating to removable interfaces and dhclient. It might be useful to
include some sa
On Thu, 7 Mar 2002, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Julian
>Elischer writes:
> :
> :
> : On Thu, 7 Mar 2002, Justin T. Gibbs wrote:
> : >
> : > Then do the right things so it will.
> :
> : Unfortunatly that has been proven to not work.
> :
> : after reverting the change
Ok, I've committed a slight reorg to NOTES on -CURRENT to reflect the much
more logical layout in LINT on -STABLE WRT NETSMB, SMBFS, and
NETSMBCRYPTO. No idea where the weird ordering came from, but I think
it's fixed now. :-)
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
On Fri, 8 Mar 2002, David W. Chapman Jr. wrote:
> >As discussed at BSDCon, the release engineers are committed to
> > releasing a relatively stable snapshot of FreeBSD -CURRENT on or
> > around April 1, 2002. Obviously, a lot of major components are still
> > in progress, but a great deal o
501 - 600 of 682 matches
Mail list logo
