Thus spake Greg Lehey <[EMAIL PROTECTED]>:
> I've been thinking about what happened, and I have a possibility: the
> session before shutdown included a lot of writing to that file system,
> and I did a shutdown -p. It's possible that the shutdown powered off
> the system before the disk had flush
Thus spake Maxim Konovalov <[EMAIL PROTECTED]>:
> newfs(8) incorrectly claims that FS_OPTTIME is unavailable when
> minfree is less than MINFREE. MINFREE is defined in ufs/ffs/fs.h:
>
> #define MINFREE 8
>
> But relevant code in ufs/ffs/ffs_alloc.c uses hardcoded value:
>
> 288 if (fs->
Thus spake Nate Lawson <[EMAIL PROTECTED]>:
> On Fri, 24 Jan 2003, David Schultz wrote:
> > Thus spake Greg Lehey <[EMAIL PROTECTED]>:
> > > I've been thinking about what happened, and I have a possibility: the
> > > session before shutdown included a l
Thus spake Greg Lehey <[EMAIL PROTECTED]>:
> I've been thinking about what happened, and I have a possibility: the
> session before shutdown included a lot of writing to that file system,
> and I did a shutdown -p. It's possible that the shutdown powered off
> the system before the disk had flushe
Thus spake Garrett Wollman <[EMAIL PROTECTED]>:
> <<[EMAIL PROTECTED]> said:
>
> > Would that be a big problem to allow some fsck option not to erase all
> > these softupdates-pending inodes, but to put them in lost+found as usual?
>
> It certainly couldn't be done with the background fsck, becau
Thus spake Harald Schmalzbauer <[EMAIL PROTECTED]>:
> With 4.x I had a /etc/make.conf where I could force gcc to optimize for my
> CPU with -march.
>
> This file (/etc/defaults/make.conf) vanished, but I can see something
> similar now without any rule set.
>
> Does gcc (or any compiler stage lik
Thus spake Matthew Dillon <[EMAIL PROTECTED]>:
> :However, when you are saving a new version of an important file,
> :you need to be careful that the new version (and its directory
> :entry) hits the disk before the old one goes away. I know that vi
> :saves files in a safe way, whereas ee and ema
Thus spake Jan Srzednicki <[EMAIL PROTECTED]>:
> This massive disk mangling occured on /usr, but still, one file in /home
> got lost - which happened to be quite important file. Background fsck
> logged:
>
> Jan 20 16:06:30 stronghold root: /dev/ad1s1d: UNREF FILE I=1723065
> OWNER=winfried MODE=1
Thus spake Lucky Green <[EMAIL PROTECTED]>:
> Miguel wrote:
> > Having no swap will prevent you from getting crashdumps in
> > case of panic which, if you run 5.0, is not that unusual.
> > Besides these days harddrives cost $1/GB, so why not setup
> > the swap partition anyway?
>
> I don't want
Thus spake Lucky Green <[EMAIL PROTECTED]>:
> I am about to set up a FreeBSD 5.0 machine without a swap partition. The
> server has 1GB of RAM. Are there any caveats that I need to consider
> during installation or configuration?
If you're using sysinstall, it might insist that you have swap.
Then
Thus spake Terry Lambert <[EMAIL PROTECTED]>:
> David Schultz wrote:
> > Thus spake Odhiambo Washington <[EMAIL PROTECTED]>:
> > > acpi_cpu: CPU throttling enabled, 2 steps from 100% to 50.0%
> > > ^
Thus spake Odhiambo Washington <[EMAIL PROTECTED]>:
> The box runs prettier, but I have some output of dmesg that I'd appreciate
> some explanation on. I'll mark the portions where I seek some explanation
> on the dmesg output itself. The most important one is with USB interfaces,
> because they se
Thus spake [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> >And to that fact I have a question:
> >At the moment 8% of the disk is reserved.
> >It being a 170Gb raid, that wastes a good 13,6Gb, which I find at lot.
> >tunefs lets me bring that down to 5% = 8,5Gb without speed penalty.
> >
Thus spake [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> I'm actually more than a bit of mind to rip out the entire bogus
> swap-stripe code: If you want swap on a striped disk, you should
> use hardware, controller, vinum, ccd or raidframe to stripe.
Ccd is a nice simple solution, but by using it you
Thus spake David Schultz <[EMAIL PROTECTED]>:
> Right. The complaint is that hlen is 64 bits and the printf()
> expects the field length specifier to be an int. The same goes
> for getbsize(&hlen, ...), so I'm not sure why the compiler didn't
> complain about a
Thus spake Juli Mallett <[EMAIL PROTECTED]>:
> * De: Craig Rodrigues <[EMAIL PROTECTED]> [ Data: 2002-12-29 ]
> [ Subjecte: Re: sparc64 tinderbox failure ]
> > I'm not sure if your patch will solve the problem.
> > The offending code is here:
> > 240 if (lflag) {
> > 241
Thus spake Kris Kennaway <[EMAIL PROTECTED]>:
> On Mon, Dec 30, 2002 at 03:21:22AM +, Mike Barcroft wrote:
>
> > ===> sbin/swapon
> > cc1: warnings being treated as errors
> > /tinderbox/sparc64/src/sbin/swapon/swapon.c: In function `swaplist':
> > /tinderbox/sparc64/src/sbin/swapon/swapon.c:2
Thus spake Matthew Dillon <[EMAIL PROTECTED]>:
> :Looks good to me, modulo a few nits. I try not to nitpick, but
> :I've mentioned a few of them below. (BDE does a better job of it
> :than I do anyway. :-)
> :
> :The patch puts identical functionality in two places, so maybe it
> :would make sen
Looks good to me, modulo a few nits. I try not to nitpick, but
I've mentioned a few of them below. (BDE does a better job of it
than I do anyway. :-)
The patch puts identical functionality in two places, so maybe it
would make sense to rip support for -s out of pstat/swapinfo (and
integrate 'ps
Thus spake Christian Brueffer <[EMAIL PROTECTED]>:
> How about renaming swapon(8) into swapctl(8) after this function enhancement?
> This name reflects it's purpose much better and would be consistent with the
> other BSDs.
It would be trivial to change the name, although I don't see what
it buys
Thus spake Terry Lambert <[EMAIL PROTECTED]>:
> David Schultz wrote:
> > Thus spake Bruce Evans <[EMAIL PROTECTED]>:
> > > On Sun, 1 Dec 2002, David Schultz wrote:
> > > > Thus spake Giorgos Keramidas <[EMAIL PROTECTED]>:
> [ ... ]
> >
Thus spake Bruce Evans <[EMAIL PROTECTED]>:
> On Sun, 1 Dec 2002, David Schultz wrote:
>
> > Thus spake Giorgos Keramidas <[EMAIL PROTECTED]>:
> > > You don't *HAVE* to create a swap partition. What you see is just a
> > > warning that sysinst
Thus spake Giorgos Keramidas <[EMAIL PROTECTED]>:
> You don't *HAVE* to create a swap partition. What you see is just a
> warning that sysinstall prints, if you have warnings enabled in the
> ``Options'' menu (they are enabled by default, if I'm not mistaken in
> my reading of the source).
I'm pr
Thus spake Bruce Evans <[EMAIL PROTECTED]>:
> On Sat, 23 Nov 2002, David Schultz wrote:
>
> > Thus spake Bruce Evans <[EMAIL PROTECTED]>:
> > > ... C90 has a bogus requirement that
> > > the pointer for malloc(0) be "unique", whatever that mean
Thus spake Garance A Drosihn <[EMAIL PROTECTED]>:
> I'm installing dp2 on a 4-gig disk. I want to split that in two,
> with "dos" for the first 2 gig and freebsd in the last 2 gig. When
> I got to the disklabel step, I tried the "Auto Defaults" option to
> split up the freebsd partition. It pick
Thus spake Bruce Evans <[EMAIL PROTECTED]>:
> Er, malloc(0) is defined as returning either a null pointer or a pointer
> to 0 bytes of allocated space. Which one it chooses to return is
> implementation-defined, not undefined. C90 has a bogus requirement that
> the pointer for malloc(0) be "uniqu
Thus spake Robert Watson <[EMAIL PROTECTED]>:
> The reasons to deprecate procfs are many-fold -- not least that there are
> existing interfaces in the kernel that provide most or all of its features
> at a substantially lower risk. You just have to see the kernel-related
> security advisories for
Thus spake David O'Brien <[EMAIL PROTECTED]>:
> On Fri, Nov 22, 2002 at 12:46:41PM +0100, Marc Recht wrote:
> > >Don't worry about it; it's being totally blown out of proportion;
> > No problem.. :)
> >
> > >there's no way anyone will commit to importing a 2 day old 3.2.1,
> > >which is why I put
Thus spake Kris Kennaway <[EMAIL PROTECTED]>:
> > I have long wondered why NOCLEAN isn't the default. There seem to
> > be a few cases where it doesn't DTRT for kernel builds, but it
> > seems a bit conservative to make incremental world builds require
> > that an undocumented variable be defined.
Thus spake John Baldwin <[EMAIL PROTECTED]>:
> Make release is a very poor example b/c make release goes to great
> efforts to create a clean-room environment for a release. make
> rerelease is quite helpful though and does do what you want to
> restart a previous release. :) Also, make buildworl
Thus spake David O'Brien <[EMAIL PROTECTED]>:
> On Wed, Nov 20, 2002 at 05:57:41PM +0100, Marc Recht wrote:
> > Hi!
> >
> > Will gcc 3.2.1/release be imported before 5.0R ? Just curious..
>
> There will be no more GCC imports before 5.0-R. It is just too much code
> churn with too little "road t
Thus spake Tim Robbins <[EMAIL PROTECTED]>:
> On Wed, Nov 20, 2002 at 01:27:43PM +0100, Alexander Leidinger wrote:
>
> > On Tue, 19 Nov 2002 10:27:00 -0800
> > David Schultz <[EMAIL PROTECTED]> wrote:
> >
> > > > > I'm con
Thus spake Alexander Leidinger <[EMAIL PROTECTED]>:
> > > > I'm concerned about the used character: "-r" is similiar to "-R"
> > >
> > > Yes, `-r' would be a very poor choice for the reason you state.
> >
> > Agreed, but the precedent has already been set by touch(1) and
> > truncate(1). If we'r
Thus spake Garrett Wollman <[EMAIL PROTECTED]>:
> > I'm concerned about the used character: "-r" is similiar to "-R"
>
> Yes, `-r' would be a very poor choice for the reason you state.
Agreed, but the precedent has already been set by touch(1) and
truncate(1). If we're going to get it wrong some
Thus spake Robert Watson <[EMAIL PROTECTED]>:
> So one thing we could start doing is have sysinstall's adduser stuff offer
> to place new users in the operator group, and set up the default
> permissions on removable devices such that the operator group has
> read/write access to them (or even just
Thus spake Bruce Evans <[EMAIL PROTECTED]>:
> > > > I retained the int 12h fallback just to be safe, but I
> > > > think the bootinfo structure is initialized with a valid basemem
> > > > for all loaders since at least 1998. (Maybe the fallbacks in the
>
> Since 1995, but not in boot2 since 2002/
Thus spake Bruce Evans <[EMAIL PROTECTED]>:
> Perhaps the problem with int 0x12 is the same as the one with int 0x15.
> Old implementations of int 0x12 just read the word at 0x40:0x13 in
> real or vm86 mode. This only requires physical page 0 to be mapped
> readable to work in vm86 calls. New imp
Thus spake TOMITA Yoshinori <[EMAIL PROTECTED]>:
> But unfortunately, that ugly code was contained in our inhouse library
> written by someone.
> It took me two days to debug and find out where difference comes from
> between gcc-2.95.4 and gcc-3.2.1.
You can work around the problem by disabling -
Thus spake Andre Albsmeier <[EMAIL PROTECTED]>:
> It seems to be a Quantum Atlas drive. IIRC, I have several of them
> running fine (I am not 100% sure, I am on holidays at the moment :-)).
> You might want to check the firmware of that drive. I have upgraded
> the FW on my Quantum Atlas I and II d
Thus spake David Schultz <[EMAIL PROTECTED]>:
> I'm running into the same problems on a very light I/O load
> (running /usr/bin/less on certain files triggers it). There's
> also a timeout every time at bootup. I have included my dmesg
> below.
[...]
Here
Thus spake Mitsuru IWASAKI <[EMAIL PROTECTED]>:
> > This approach is okay with me in the sense that it doesn't break
> > anything that wasn't already broken, but as you say, I think we
> > can do better. Below is a patch that merely extracts the basemem
> > size from the bootinfo structure for the
Thus spake Mitsuru IWASAKI <[EMAIL PROTECTED]>:
> OK, it seems to be difficult to determine the region for any BIOSes.
> I've decided to introduce a new loader tunable to indicate that BIOS
> has broken int 12H. Attached patch back out 1.385.2.26 changes to
> support older BIOSes, and add support
Thus spake Justin T. Gibbs <[EMAIL PROTECTED]>:
> > I am running current cvsuped within this week. I have an adaptec
> > builtin scsi controller and a seagate drive attached to it and
> > after every bootup as soon as there is heavy disk activity
> > the drive gets disabled for 1 or 2 minutes and
Thus spake Mitsuru IWASAKI <[EMAIL PROTECTED]>:
> Hmmm, I didn't notice that there is a BIOS which requires
> memory area below 640K even when calling INT 15H/E820.
>
> We cannot trust that today's BOISes have INT 12H, so it's
> difficult to determine base memory size w/o INT 15H/E820.
You keep s
Thus spake Sidcarter <[EMAIL PROTECTED]>:
> Fatal trap 12: page fault while in vm86 mode
> fault virtual address = 0x9fdc8
^^^
That's a region of memory right before the 640K mark,
and your BIOS is trying to use it. This used to work,
but revision 1.544 of src/sys/i38
Thus spake Michael G. Petry <[EMAIL PROTECTED]>:
> I'm noticing the same behavior on a PPro system I have and am following
> the thread "SMP broken on PPro". It looks like the problem is not SMP
> specific, but it does seem PPro centric.
I observed the problem on a PPro as well, but it is not spe
Thus spake Glenn Johnson <[EMAIL PROTECTED]>:
> > I have had no trouble with UP -STABLE running on a dual PPro system,
> > but I'm getting an early panic in UP and SMP -CURRENT on the same
> > system. I will post details to current@ soon if I can't figure out
> > the problem.
>
> The problem on -
Thus spake Robert Watson <[EMAIL PROTECTED]>:
> > I can't come up right now with an idea of how exploiting LD_LIBRARY_PATH
> > could be useful with any of these, but the possibility exists. OTOH, the
> > recently added priviledge elevation feature should make it possible to
> > have *no* setuid pro
Thus spake Miguel Mendez <[EMAIL PROTECTED]>:
> Why? I'd love to hear some real reasons for this. NetBSD-current has
> just gone fully dynamic, let's see how much space that needs...
>
> christine: {16} uname -srnm
> NetBSD christine.energyhq.tk 1.6J i386
> christine: {17} du -h /bin /sbin /lib
>
Thus spake Bruce Evans <[EMAIL PROTECTED]>:
> $ cc -o z z.c
> $ ./z
> LDBL_EPSILON failed test 1 with prec 2
> $ cc -O -o z z.c.
> $ ./z
> LDBL_EPSILON failed test 1 with prec 2
> DBL_EPSILON failed test 2 with prec 3
> %%%
>
> The full brokenness only shows up with -O.
Actually, the _full_ broke
Thus spake Terry Lambert <[EMAIL PROTECTED]>:
> David Schultz wrote:
> > > > We've been over this before. To make this work right, we need to make
> > > > /bin and /sbin dynamically linked. NetBSD's /rescue/* approach would
> > >
Thus spake Doug Rabson <[EMAIL PROTECTED]>:
> > > Move the resolver code out to ibresolv.so, and link libc.so
> > > against libresolv.so so that legacy applications are happy, as
> > > long as they are compiled shared. Non-network apps can ignore
> > > most of it. Internal use of some of the bigg
Thus spake Tim Kientzle <[EMAIL PROTECTED]>:
> Thus spake Lucky Green <[EMAIL PROTECTED]>:
> >>... remove ssh1 fallback from the default ...
>
> David Schultz <[EMAIL PROTECTED]> wrote:
> >Removing SSH 1 ... is going to break compatibility ...
>
&
Thus spake M. Warner Losh <[EMAIL PROTECTED]>:
> : No. You should assume that for i386, at least, that long double will
> : have the right LDBL_ constants. I've had them in my local tree for
> : about 3 months now and just haven't found the time to commit to
> : -current. I'll find the time righ
Thus spake Steven Ames <[EMAIL PROTECTED]>:
> > Making SSH 2 the default is one thing. Removing SSH 1 as a
> > fallback altogether is going to break compatibility with other
> > systems like you'd never believe. For example, I regularly need
> > to SSH into Solaris boxen running SSH 1. These mac
Thus spake Lucky Green <[EMAIL PROTECTED]>:
> I therefore believe that the 5.0 release represents a perfect
> opportunity to remove ssh1 fallback from the default distribution of
> FreeBSD and hope the FreeBSD team will consider this change.
Making SSH 2 the default is one thing. Removing SSH 1 a
Thus spake Mike Barcroft <[EMAIL PROTECTED]>:
> No one has started work on any of the C99 math functions yet. I
> think with the exception of the math functions we conform to C99.
Actually, I hacked up some patches for fpclassify(), is*(), and
friends some time ago. But nobody was interested in
Thus spake M. Warner Losh <[EMAIL PROTECTED]>:
> In message: <[EMAIL PROTECTED]>
> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
> : I think it confuses the issue rather than solving it. We're talking
> : about removing binaries which are no longer needed, not replacing
> : binari
Thus spake Mario Goebbels <[EMAIL PROTECTED]>:
> Is there still any development being done on the soundcard
> drivers in FreeBSD? Especially regarding EMU10K2 support?
Go to www.opensound.com/freebsd/. Their drivers should work fine,
even with more than two speakers, and they tend to sound bette
Thus spake Alexander Leidinger <[EMAIL PROTECTED]>:
> On Thu, 26 Sep 2002 10:52:18 -0500 Dan Nelson <[EMAIL PROTECTED]>
> wrote:
>
> > > We have something better than those. SoftUpdates. Much faster than
> > > jfs in metadata intensive operations.
> >
> > If you can stand the 20 minutes of sever
Thus spake Michael WARDLE <[EMAIL PROTECTED]>:
> The Gecko engine developed by the Mozilla Project, however seems
> to be very good. I find Galeon quite nice, as it uses Mozilla's
> quite capable HTML rendering engine, has its own well designed
> GTK-based GUI, and has little of Mozilla's bloat.
Thus spake Terry Lambert <[EMAIL PROTECTED]>:
> Mozilla, Galeon, and other browsers claim to be better, but
> often fail to provide features that have been in Netscape
> for forever.
You mean features like being stable, at least sometimes?
Efficiency? IMO, Mozilla has features up the kazoo, but
Thus spake Terry Lambert <[EMAIL PROTECTED]>:
> > Sometimes. But see http://www.tuxedo.org/~esr/jargon/html/entry/DWIM.html
>
> I understand, but having a different failure is no worse than
> having a failure, I think. In either case, it doesn't work,
> even if it doesn't work in an entirely di
Thus spake Terry Lambert <[EMAIL PROTECTED]>:
> FWIW, there's historical precedent for this: the DEC VAX/VMS
> C compiler would imply semicolons for the programmer that
> forgot them, and a couple of other similar "fixups", issue a
> warning, but the resulting code would run "as the programmer
> m
Thus spake M. Warner Losh <[EMAIL PROTECTED]>:
> I would STRONGLY suggest that any attempts to change the
> setuid semantics of FreeBSD be resisted unless the person making the
> change is willing to a) audit the entire tree for places where the use
> of setuid breaks (and to publish the r
Thus spake Kurt Erik Lindqvist <[EMAIL PROTECTED]>:
> Uhm, I am kinda new to this, so I have no idea how to get that to disk from
> the debugger...:(
>
> However, the error I get is "Fatal trap 19: non-maskable interrupt trap
> while in kernel mode".
>
> If someone could help point me to how t
Thus spake Ian Dowse <[EMAIL PROTECTED]>:
> In message <[EMAIL PROTECTED]>, David Schultz writes:
> >I just made world on -CURRENT (cvsup a few hours ago), booted
> >using a new GENERIC kernel and ran mergemaster. Before I
> >installed world, I mounted the
I just made world on -CURRENT (cvsup a few hours ago), booted
using a new GENERIC kernel and ran mergemaster. Before I
installed world, I mounted the root partition for my more stable
development environment (4.6-RELEASE) to copy my firewall rules
over. In summary:
# mount /dev/ad1s1a /mnt
# mo
Thus spake Peter Wemm <[EMAIL PROTECTED]>:
> Please do not. gcc is just a tool. If it emits a warning on some arches
> because gcc doesn't understand how our libraries work, then we should
> disable the gcc checking for those arches on those functions. ie: remove
> the __printf0like completely
Thus spake Gregory Neil Shapiro <[EMAIL PROTECTED]>:
> Interestingly enough, pam_opieaccess doesn't help at all in this
> situation. The remote user is still prompted for their plain text
> password, it just isn't accepted. However, the damage is already done -- a
> compromised ssh client would
Thus spake David Xu <[EMAIL PROTECTED]>:
> I don't know if FreeBSD can run DOS program, if it can, then one CPU running
> DOS program can confuse another CPU which is running BIOS code because of this
> global flags.
>
> my current patch does not remove vm86_lock, it is still there, my orginal
>
Thus spake Terry Lambert <[EMAIL PROTECTED]>:
> Personally, I prefer knowing my code should work before giving
> it to the compiler, rather than using the compiler to think
> about things I'm too lazy/incapable of thinking of on my own.
> Given that, I would always favor a trade for faster run tim
Thus spake Avleen Vig <[EMAIL PROTECTED]>:
> I would recommend you install the -STABLE branch (the most stanble) or
> -RELEASE (fairly stable with the probability of a few bugs here and
> there).
You have that backwards. (Admittedly, the historical nomenclature
doesn't help.) -STABLE is a conti
Thus spake Terry Lambert <[EMAIL PROTECTED]>:
> Writing a useful (non-"fluff") technical book, optimistically,
> takes 2080 hours ... or 40 hours per week for 52 weeks... a man
> year.
>
> By the time you are done, the book is a year out of date, and
> even if you worked really hard and kept it u
Thus spake Vallo Kallaste <[EMAIL PROTECTED]>:
> Userspace processes will allocate memory
> from UVA space and can grow over 1GB of size if needed by swapping.
> You can certainly have more than one over-1GB process going on at
> the same time, but swapping will constrain your performance.
It isn
Thus spake Terry Lambert <[EMAIL PROTECTED]>:
> I'm pretty sure Solaris also used 4K pages for swappable memory
> in the kernel, as well: 4M pages don't make much sense, since
> you could, for example, exhaust KVA space with 250 kernel modules
> (250 X (1 data + 1 code) * 4M = 2G).
It doesn't use
Thus spake Terry Lambert <[EMAIL PROTECTED]>:
> If you want more, then you need to use a 64 bit processor (or use a
> processor that supports bank selection, and hack up FreeBSD to do
> bank swapping on 2G at a time, just like Linux has been hacked up,
> and expect that it won't be very useful).
Thus spake Miguel Mendez <[EMAIL PROTECTED]>:
> On Sat, 02 Feb 2002 03:29:50 -0800
> Terry Lambert <[EMAIL PROTECTED]> wrote:
>
> Hi Terry et al,
>
> > Let me know the form you want the hierarchy to take, so
> > you can stick it into the GTK hierarchy thingy; I'll be
> > happy to crank out some
101 - 178 of 178 matches
Mail list logo