On 19 Jan, Stefan Esser wrote:
> I seem to remember, that drives of that time required the write cache
> to be enabled to get any speed-up from tagged commands. This was no
> risk with SCSI drives, since the cache did not make the drives lye
> about command completion (i.e. the status for the wri
On 18 Jan, Wojciech Puchar wrote:
> If computer have UPS then write caching is fine. even if FreeBSD crash,
> disk would write data
I've had my share of sudden UPS failures over the years. Probably more
than half have been during an automatic battery self test. UPS goes on
battery, and then *b
On 5 Jul, Olivier Smedts wrote:
> an Ubuntu "server" :
> # time fsqfqsdfs
> fsqfqsdfs: command not found
>
> real0m0.408s
> user0m0.120s
> sys 0m0.040s
>
> and that's a *fast* one !
Lucky you!
Fedora 16 on my fastest hardware ...
# time fsqfqsdfs
bash: fsqfqsdfs: command not foun
On 17 Jan, Atom Smasher wrote:
> thanks john.
>
> i've been a long-time (10+ years) freeBSD user (desktops, laptops,
> servers, and anywhere else i can run it) and advocate (encouraging others
> to at least check it out) and also a long-time satisfied johnco customer.
>
> my freeBSD days seem t
On 26 Dec, Venkatesh Srinivas wrote:
> Hi!
>
> I've been playing with two things in DragonFly that might be of interest here.
>
> Thing #1 :=
>
> First, per-mountpoint syncer threads. Currently there is a single thread,
> 'syncer', which periodically calls fsync() on dirty vnodes from every moun
On 1 Dec, Ondřej Majerech wrote:
> Hello,
>
> my 8.1-R system has just started hanging on reboot. Specifically after
> I svn up'd my source and updated from 8.1-R-p1 to -p2.
>
> Some kind of hang occurs on every reboot attempt. Usually it hangs at
> the "Rebooting..." message, but sometimes the
On 25 Sep, sam wrote:
> sam wrote:
>> Don Lewis wrote:
>>> On 24 Sep, sam wrote:
>>> Expect major file system lossage ...
>>> I think this patch could be better, but this should get you going ...
>>>
>>>
>>
>>
>> UNEXPECTE
On 25 Sep, sam wrote:
> Don Lewis wrote:
>> On 24 Sep, sam wrote:
>>
>>
>>> any solutions ?
>>>
>>
>> The patch below should allow a manual fsck to run to completion. I'd
>> recommend running "fsck -N" and capturing
On 24 Sep, sam wrote:
> hi, all
> http://lists.freebsd.org/pipermail/freebsd-questions/2007-June/151686.html
>
> my problem
> # fsck /dev/aacd0s1f
> ** /dev/aacd0s1f (NO WRITE)
> ** Last Mounted on /usr
> ** Phase 1 - Check Blocks and Sizes
> fsck_ufs: cannot alloc 2378019004 bytes for inoinfo
I'
On 31 Jul, João Carlos Mendes Luís wrote:
> Hi,
>
> Sent this to -questions, but got no answer. Now I'll try -hackers...
>
> I've just configured my first server with 4G RAM. To use it, I had
> to select PAE in kernel config. I was a little bit troubled by it's
> advice not to use modu
On 12 Oct, Rob Watt wrote:
>> >> On Fri, 7 Oct 2005, Don Lewis wrote:
>> I MFC'ed the fix to RELENG_6 last week, but the patch didn't apply
>> cleanly to RELENG_5. I tweaked the patch for RELENG_5 and tested it on
>> a UP box. I'd like to get some tes
On 11 Oct, Rob Watt wrote:
> On Mon, 10 Oct 2005, Rob Watt wrote:
>
>> Don,
>>
>> On Fri, 7 Oct 2005, Don Lewis wrote:
>>
>> > Both HEAD and RELENG_6 have been patched. I've tested the following
>> > patch for RELENG_5 on a uniprocessor s
On 3 Oct, Rob Watt wrote:
> We noticed the patches from Don Lewis, but have not tested them yet. We
> weren't sure if we could just apply those patches against 6.0-BETA5, or
> whether we should wait for them to be MFC'd.
Both HEAD and RELENG_6 have been patched. I've te
t; + error = sysctl_wire_old_buffer(req, 0);
>> + if (error)
>> + return (error);
>> p = pfind((pid_t)name[0]);
>> if (!p)
>> return (ESRCH);
>
> John,
>
> We tried this patch and were able to run our simulations (and top) for 3
> days straight without
On 2 Oct, Don Lewis wrote:
> It turns out that fill_kinfo_thread() grabs a bunch of locks to grab
> things out of struct proc, which breaks badly if sched_lock is grabbed
> before calling fill_kinfo_thread().
>
> I refactored fill_kinfo_thread() into two functions, one of which
On 1 Oct, Don Lewis wrote:
> On 30 Sep, John Baldwin wrote:
>> It turns out that the sysctl buffer is already wired in one of the two cases
>> that this function is called, so I moved the wiring up to the upper layer in
>> the other case and cut out a bunch of the lo
On 30 Sep, John Baldwin wrote:
> On Friday 30 September 2005 11:25 am, Antoine Pelisse wrote:
>> On 9/30/05, John Baldwin <[EMAIL PROTECTED]> wrote:
>> > On Friday 30 September 2005 05:24 am, Antoine Pelisse wrote:
>> > > Hi Robert,
>> > > I don't think your patch is correct, the total linked list
On 30 Sep, Antoine Pelisse wrote:
> Hi Robert,
> I don't think your patch is correct, the total linked list can be broken
> while the lock is released, thus just passing the link may not be enough
> I have submitted a PR[1] for this a month ago but nobody took care of it yet
There are two problem
On 29 Sep, Doug Barton wrote:
> Mike Meyer wrote:
>> A 4K block won't hold your median file. But an 8K block wastes a lot of
>> space. You might get a file with 0 blocks and 3 frags, assuming that UFS2
>> will do that, which doesn't seem good. If UFS2 won't do that, you get a
>> lot of half-emp
On 20 Aug, Eric Anderson wrote:
> As a data point, I've been using 64mb compact flash cards (rated at 100k
> writes) in about 100 Soekris boxes (running FreeBSD) for about 4 years,
> and they are all still working, except for one. Now, most compact flash
> cards are rated at 1 million writes.
On 10 Aug, Dmitry Morozovsky wrote:
> Colleagues,
>
>
> from ffs_alloc.c:
>
> case FS_OPTSPACE:
> /*
> * Allocate an exact sized fragment. Although this makes
> * best use of space, we will waste time relocating it if
> *
me errors.
>>
>> I don't know how to repair this file system. Could anyone point me
>> what to do?
>
> I'm struggling with the same problem. Suggestion so far from Don Lewis:
>
> Try setting kern.maxdsiz to a larger value in /boot/loader.conf and
> rebootin
On 21 May, Peter Jeremy wrote:
> On Fri, 2005-May-20 21:51:34 +0200, Hans Petter Selasky wrote:
>>Can anyone explain why "uiomove()" has to sleep, and why there is no
>>non-blocking "uiomove()"?
>
> As far as I can see, uiomove() only sleeps if it is asked to do a
> kernel<->userland move that t
On 16 May, alexander wrote:
> You're right. The code I'm using is wrong when it is being executed
> under the console. However the fact that Eterm and xterm do what I
> want to do with my app show that I'm not the only one who needs a
> NOP ascii value. Both render the NUL ascii code as NOP. Since
On 21 Feb, Robert Watson wrote:
>
> On Mon, 21 Feb 2005, Igor Shmukler wrote:
>
>> > So the first thing to do is to decied what your requirements are: are you
>> > willing to fail in the edge cases like the above? If so, life is a lot
>> > easier :-).
>>
>> I guess I am willing to fail :). Per
On 15 Feb, Max Laier wrote:
> On Tuesday 15 February 2005 12:38, Borja Marcos wrote:
>> Hello,
>>
>> Looking at the mbuf statistics available in FreeBSD 4 and FreeBSD 5 I
>> can see that the statistics available in FreeBSD 5 are, surprisingly,
>> much less comprehensive. Is there any othe
On 26 Jan, Chris Landauer wrote:
>
> hihi, doug -
>
>> Doug Ambrisko <[EMAIL PROTECTED]> wrote
>> ...
>> The assumption with this calculation is that st & it tend to be
>> small compared to tt so the 1024 X shouldn't overflow much.
>> ...
>> [EMAIL PROTECTED] wrote:
>> |..
On 23 Jan, Peter Jeremy wrote:
> On Fri, 2005-Jan-21 14:49:41 -0800, Chris Landauer wrote:
>>i'm running some combinatorial search programs that take weeks or months to
>>complete, and no timer i've used is able to report correctly the user and
>>system time (they all make the same mistake - eventu
On 18 Jan, David Malone wrote:
> On Tue, Jan 18, 2005 at 03:18:42PM -, Steven Hartland wrote:
>> The attached patch checks for
>> MSG_NOSIGNAL and if set enables SO_NOSIGPIPE
>> for the duration of send call.
>
> I just had a quick look at the patch. The patch should probably
> use kern_setsoc
On 29 Oct, Siddharth Aggarwal wrote:
>
> Thanks for your reply.
>
> Hmm. At the moment, the user can send an ioctl to define a checkpoint. But
> I would guess that this could happen between 2 strategy() function calls
> corresponding to the same filesystem operation?
Yes.
> So if there a way to
On 29 Oct, Siddharth Aggarwal wrote:
>
> Another related question ...
>
> Is it possible to delay or queue up disk writes until I exit from my
> function in the kernel (where I am trying to sync with the disk)? Or
> make sure that my sync function never goes to sleep waiting for the disk
> driver
On 7 Oct, Roman Kurakin wrote:
> Hi,
>
> I have some problems with printing from kernel.
> At first I think that my problems was cause I use printf,
> but changed all of them to log cause it safe to use from
> interrupt handlers. The situation become better but I still
> observe system lock
On 20 Sep, [EMAIL PROTECTED] wrote:
>> cat kern_syscalls.diff
> --- kern_syscalls.c Sat Sep 18 13:42:21 2004
> +++ kern_syscalls2.cMon Sep 20 14:18:45 2004
> @@ -58,6 +58,16 @@
> syscall_register(int *offset, struct sysent *new_sysent,
> struct sysent *old_sysent)
> {
>
On 19 Sep, [EMAIL PROTECTED] wrote:
>
>>Don,
>>
>>This sounds excellent. Can an src-committer verify that the following
> is
>>ok and commit it along with the manpage diff I posted earlier to HEAD?
>>
>>The hard-wired number 8 in there seems like something that could probably
>>be improved a lot,
On 19 Sep, Giorgos Keramidas wrote:
> On 2004-09-19 15:04, [EMAIL PROTECTED] wrote:
>> --- kern_syscalls.c Sat Sep 18 13:42:21 2004
>> +++ kern_syscalls2.cSun Sep 19 14:59:27 2004
>> @@ -58,6 +58,12 @@
>> syscall_register(int *offset, struct sysent *new_sysent,
>> struct s
On 18 Sep, [EMAIL PROTECTED] wrote:
> Here i report a patch different from Giorgos' one. The approch is completely
> different: working on syscall_register() function in kern/kern_syscalls.c
> file.
>
> ==
>
>> cat kern_syscalls.diff
> --- kern_syscalls.c Sat Sep 1
On 18 Sep, Pawel Jakub Dawidek wrote:
> On Fri, Sep 17, 2004 at 12:37:12PM +0300, Giorgos Keramidas wrote:
> +> % +#ifdef INVARIANTS
> +> % + KASSERT(0 <= narg && narg <= 8, ("invalid number of syscall args"));
> +> % +#endif
>
> Maybe:
> KASSERT(0 <= narg && narg <= sizeof(args) / sizeof(ar
On 18 Sep, Matt Emmerton wrote:
>
> - Original Message -
> From: "Mike Meyer" <[EMAIL PROTECTED]>
> To: "Matt Emmerton" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>; "Avleen Vig"
> <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Saturday, September 18, 2004 1:22 A
On 25 Jun, Brandon D. Valentine wrote:
> On Fri, Jun 25, 2004 at 02:43:03PM +0300, Danny Braniss wrote:
>> I understand, but the problem is that all access via amd are now stalled, till
>> the one process failes/times-out. I guess it's because the single thread amd.
>
> This is an excellent opport
On 24 Jun, Danny Braniss wrote:
> found the cause: NFS/amd
> a user had several symlinks to /net/host/xyz, and host was down.
> doing ls -F /net/host/xyz does the trick, the machine becomes
> unresponsive.
/net is evil. A fun trick is to attempt to access
/net/nonexistenthost and watch amd wedge
On 22 Jun, pradeep reddy punnam wrote:
> Hi,
>
> i am modifing my ../netinet/ip_input.c code so that kernel can inform a
> user process about the arrival of a packet, i want to use signaling
> mechanism for this , i know the pid of the process to which the signal
> should be send, i am looking
On 6 Jun, Daniel Eischen wrote:
> On Sun, 6 Jun 2004, Marcel Moolenaar wrote:
>
>> On Sun, Jun 06, 2004 at 02:31:56PM -0600, Scott Long wrote:
>>
>> > As with Alpha,
>> > the fate of a platform rests on the people who are willing to work on
>> > it, not on whether it is in a particular list.
>>
On 16 May, David Malone wrote:
> On Sun, May 16, 2004 at 02:25:37AM -0300, Marc G. Fournier wrote:
>> so I take there are 'gaps' in the inode list? it doesn't re-use freed
>> ones but keeps climbing until maybe it rolls around or something?
>
> A particular numbered inode always lives in the same
On 9 May, Bartek Marcinkiewicz wrote:
> Hello,
>
> I've just experienced kernel panic while trying
> to play mp3 file. (My sound card: Creative Sound
> Blaster 16, ISA, worked fine on older 5.x system).
>
> While reading code:
>
> sys/dev/sound/pcm/sound.c::snd_mtxcreate() creates
> non-recurs
On 23 Feb, Brian O'Shea wrote:
> --- Brian O'Shea <[EMAIL PROTECTED]> wrote:
>> --- Mathew Kanner <[EMAIL PROTECTED]> wrote:
>> >
>> >Hello Brian,
>> >Don Lewis commited changes to the 5.2- tree on 2/14. Could
>>
On 23 Feb, Brian O'Shea wrote:
> --- Don Lewis <[EMAIL PROTECTED]> wrote:
>>
>> The cause of deadlocks is more likely to be caught by WITNESS. In this
>
> With WITNESS the hang still occurrs, and still no panic. It's hard to
> tell since the problem
On 23 Feb, Mathew Kanner wrote:
> On Feb 23, Brian O'Shea wrote:
>> --- Mathew Kanner <[EMAIL PROTECTED]> wrote:
>> >
>> >Hello Brian,
>> >Don Lewis commited changes to the 5.2- tree on 2/14. Could
>> > you update and try again, als
On 10 Feb, Steven Hartland wrote:
> Ok looks like this has been spotted before and its a kernel issue
> described here:
> http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=bausg0%2416c5%241%40FreeBSD.csie.NCTU.edu.tw&rnum=13
If the kernel patch mentioned above fixes the problem, I'l
On 10 Feb, Dag-Erling Smørgrav wrote:
If you don't minde a bit of bloat, maybe changing this:
> openpam_log(PAM_LOG_DEBUG, "returning '%s'", (s)); \
to this:
openpam_log(PAM_LOG_DEBUG, "returning '%s'", (s) != NULL ? (s) : "");
might quiet the warning.
On 23 Jan, Stuart Pook wrote:
>> send() for UDP should block if the socket is filled and the interface
>> can't drain the data fast enough.
>
> It doesn't (at least I cannot make it block)
>
>> Good question. There is not feedback loop like in tcp, so handling this
>> blocking and releasing woul
On 5 Jan, Brett Glass wrote:
> It's probably one of the Slashdot "BSD is dead" trolls. The fact is, though,
> that there ARE things about FreeBSD that could stand improvement. These
> days, when I build a box, I am torn between using FreeBSD 5.x -- which is
> not ready for prime time but is at le
A few more data points:
System 1 (FreeBSD 4-STABLE)
Pentium II 400
Asus P2B-LS motherboard (fxp + aic7890 Ultra2 SCSI on board)
384 MB ECC RAM
Matrox G20
Floppy
Seagate ST336737LW
Seagate ST39173LW
Plextor PX-R412C CD-R
Tandberg SLR-5
Floppy
Supermicro Case with lots of fans
On 29 Dec, Jason Slagle wrote:
>
> So I'm not the only one?
>
> After submitting a single PR, I started getting innudated with klez
> emails. 12+ a day, to an account that had never received one.
>
> Me thinks it's time to obscure the emails somehow.
That might not help. I would think that it
On 14 Nov, M. Warner Losh wrote:
> checking stopevent 2 with the following non-sleepable locks held:
> exclusive sleep mutex sigacts r = 0 (0xc48c5aa8) locked @ kern/subr_trap.c:260
> checking stopevent 2 with the following non-sleepable locks held:
> exclusive sleep mutex sigacts r = 0 (0xc48c5aa8
On 20 Aug, Lars Eighner wrote:
> On Tue, 19 Aug 2003, Don Lewis wrote:
> I set the port setup in minicom to 57600, and got this
> on connect:
>
>
> atdt4857440
> CONNECT 29333/ARQ/V90/LAPM/V42BIS
>
>
> and when I hung up the current settings looked like this:
On 19 Aug, Lars Eighner wrote:
> On Tue, 19 Aug 2003, Don Lewis wrote:
>
>> On 19 Aug, Lars Eighner wrote:
>> > This has been answered by somebody on some forum, but I lost it.
>
>> If you manually dial using cu or tip, what connection speed does the
>> mode
On 19 Aug, Lars Eighner wrote:
> This has been answered by somebody on some forum, but I lost it.
>
> I have an internal hardware modem. I have configured ppp on demand.
> Unfortunately, my 56k modem connects at an effective rate of about
> 14.4k when I use ppp under FreeBSD. I have got normal c
On 6 Aug, Frank Mayhar wrote:
> On Monday I received my brand-new Epson C82, a replacement for a 900N with
> a dead print head. I had already configured CUPS so I imagined that I would
> just hook it up with USB and everything would be happy.
>
> Well, that's not how it turned out.
>
> I tried
On 7 Aug, Frank Mayhar wrote:
> Don Lewis wrote:
>> Unless someone snuck it in while I wasn't looking, our ulpt
>> implementation doesn't support reading data from the printer, so it's
>> not possible to check the ink levels. I've had to boot Linu
On 29 Jun, I wrote:
> On 22 Jun, Andrey Alekseyev wrote:
>> Name cache can be purged by nfs_lookup(), if the latter finds that the
>> capability numbers doesn't match. In this case, nfs_lookup() will send a
>> new "lookup" RPC request to the server. Name cache can also be purged from
>> getnewvnod
On 22 Jun, Andrey Alekseyev wrote:
> Don,
>
>> When a file is renamed on the server, its file handle remains valid.
>
> Actually I was wrong in my assumption on how names are purged from the
> namecache. And I didn't mean an operation with a file opened on the client.
> And it actually happens th
On 21 Jun, Andrey Alekseyev wrote:
> Don,
>
>> old vnode and its associated file handle. If the file on the server was
>> renamed and not deleted, the server won't return ESTALE for the handle
>
> I'm all confused and messed up :) Actually, a rename on the server is not
> the same as sillyrenam
On 20 Jun, Andrey Alekseyev wrote:
>> Eh, but the generation number for file1 should have been changed! This will
>
> I'm sorry, the generation number is not changed in your scenario. Thus,
> I believe if the sequence of actions on the server is
>
> mv file1 tmpfile
> mv file2 file1
> mv tmpfile
On 20 Jun, Andrey Alekseyev wrote:
> Don,
>
>> One case where there is a difference between timing out old file handles
>> and just invalidating them on ESTALE:
>
> Frankly, I just didn't find any mechanism in the STABLE kernel that
> does "timing out" for file handles. Do you mean, it would be n
On 20 Jun, Andrey Alekseyev wrote:
> In the normal situation, namecache entry+vnode+nfsnode+file handle may
> stay cached for a really long time (until re-used? deleted or renamed
> on the *client*). Expiring file handles (a new mechanism?) means much the
> same to me as simply obtaining a new nam
On 19 Jun, Andrey Alekseyev wrote:
> Hello,
>
> I've been trying lately to develop a solution for the problem with
> open() that manifests itself in ESTALE error in the following situation:
>
> 1. NFS server: echo "" > file01
> 2. NFS client: cat file01
> 3. NFS server: echo "" > file02 &
On 16 Jun, Juli Mallett wrote:
> Not to turn this into too much of a bikeshed, but here's an idea I
> jotted down a while ago:
>
> %%%
> There has been a lot of talk about deprecation of floppies in upcoming
> releases, and I've been thinking a lot about whether or not we need to
> do this, and I
On 27 May, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "Bruce R. Montague" <[EMAIL PROTECTED]> writes:
> :
> : Julian Elischer wrote:
> :
> : > ... I have not been able to compile the openoffice port ...
> :
> : > ... Has anyone else seen this?
> :
> :
> : I trie
On 27 May, Julian Elischer wrote:
>
> For the last month (more actually)(and after completely rebuilding my
> system and all the ports on it) I have not been able to compile
> the openoffice port due to gcc failures.
> (I have posted the message earlier several times)
> Has anyone been able to c
On 8 Oct, Oliver Fromme wrote:
> I should have been more specific in my examples. Sorry.
>
> Think about INN with using cycbuffers (CNFS) when storing
> news articles (which is pretty standard on fullfeed news
> servers). Those cycbuffers are a bunch of large files.
> Their size never changes
On 26 Aug, Mikko Työläjärvi wrote:
> On Mon, 26 Aug 2002, Terry Lambert wrote:
>
>> John Nielsen wrote:
>> > "FreeBSD, NetBSD, and OpenBSD are not yet supported in USB mode, due to
>> > missing functionality in the kernel "ulpt" driver (bidirectional I/O,
>> > device ID retrieval, switching to 7
On 22 Aug, Terry Lambert wrote:
> Alternatively, rather than those options, try losing 512M of
> the RAM... I note they are all 1G boxes.
When I first put this system together several months ago, I only
installed the first 512M of RAM and the problem was much worse. I only
had about a 50% chanc
On 22 Aug, Soeren Schmidt wrote:
> However, this kind of problem in most cases spells bad HW to me,
> ie subspec RAM, poor powersupply, badly cooled CPU, overclocking etc etc...
My motherboard chipset supports ECC RAM and I have ECC RAM installed. I
upgraded to an expensive Antec power supply t
On 22 Aug, Mark Santcroos wrote:
> On Thu, Aug 22, 2002 at 09:43:45AM +0200, Martin Blapp wrote:
>> Thats memory corruption. I'm also not able anymore
>> to make 10 buildworlds (without -j, that triggers
>> panics in pmap code).
>>
>> Bye the way, I'm experiencing this since about 4-5 months.
>>
On 8 Jul, Peter Wemm wrote:
> Julian Elischer wrote:
>> this is not a 'reformat'
>>
>> what I want to do is an old-fashionned refomat/verify where the controller
>> writes new track headers etc.
>
> The thing is, just about all IDE drives more than a few GB or so do 'track
> writing' and have n
On 2 Jul, Brian Reichert wrote:
> I'm mucking with 'make release' under 4.5-RELEASE, and keep running
> into a stumbling block:
>
> When the documentation toolset is being built in the chrooted
> environment, at one point docbook-dsssl-doc is built, among other
> things, via ports.
>
> Regretta
On 30 Jun, Julian Elischer wrote:
>
>
> On Sun, 30 Jun 2002, Charles Sprickman wrote:
>
>> On Sun, 30 Jun 2002, Julian Elischer wrote:
>> > do you have 2 machines you can link together?
>>
>> Oh yes. But I know nothing about remote gdb.
>
> it's not that difficult..
>
> have the source and
On 20 Jun, Mike Makonnen wrote:
> On Thu, 20 Jun 2002 00:04:41 -0700 (PDT)
> Don Lewis <[EMAIL PROTECTED]> wrote:
>
>>
>> Your patch also looks like it should fix the bug. I prefer my patch,
>> though, because I think the resultant code is structured
On Nov 8, 5:06pm, Max Khon wrote:
} Subject: RE: daemon()
} hi, there!
}
} On Wed, 8 Nov 2000, Koster, K.J. wrote:
}
} > > No one with any brains uses bash 1 for anything
} > > anymore.
}
} > Then why is it there? To help up the port count? If it's not good, it should
} > be nuked, IMHO.
}
On Nov 7, 11:41pm, [EMAIL PROTECTED] wrote:
} Subject: Re: daemon()
}
}
} On Tue, 7 Nov 2000, Max Khon wrote:
}
} > what is FD 4?
}
} I can't reproduce this? Does it always happen?
It might be something that the shell forgets to close, so it will be
dependent on which shell you use.
To Unsu
On Sep 1, 4:55pm, John DeBoskey wrote:
} Subject: SIOCSPGRP documentation?
} Hi,
}
}Like the subject says, I'm looking for documentation
} on the SIOCSPGRP ioctl call:
}
} rc = ioctl(port,SIOCSPGRP,&pid);
}
}I've gone through the source tree and while I can find
} references where it's
On Sep 1, 3:24pm, Peter Pentchev wrote:
} Subject: Re: Redirect stdout/stderr to syslog [OFF-TOPIC]
} On Fri, Sep 01, 2000 at 02:13:19PM +0200, Alexander Maret wrote:
} > > -Ursprungliche Nachricht-
} > > Von: Peter Pentchev [mailto:[EMAIL PROTECTED]]
} > > Gesendet: Freitag, 1. September
On Jun 22, 5:11pm, "Daniel O'Connor" wrote:
} Subject: Re: How many files can I put in one diretory?
}
} On 22-Jun-00 Luigi Rizzo wrote:
} > that sounds insane! Because a name is a name, why dont they call
} > those files xx/yy/zz/tt.html and the like, to get down to a more
} > reasonable # o
On May 24, 6:58pm, Arun Sharma wrote:
} Subject: Re: file creation times ?
} On Thu, May 25, 2000 at 11:03:38AM +1000, Peter Jeremy wrote:
} > To put it another way, why _should_ FreeBSD store a file creation time?
}
} 0. I'm tired of seeing people putting "Created: mm/dd/yy" in their documents.
On May 22, 3:33pm, Alfred Perlstein wrote:
} Subject: Re: please hep me!
} * David Scheidt <[EMAIL PROTECTED]> [000522 14:30] wrote:
} > dscheidt@shell-2 ~ 536$ ls -al | grep .snapshot
} > dscheidt@shell-2 ~ 537$ ls -al .snapshot
} > total 60
} > drwxrwxrwx 2 root wheel 4096
On May 22, 1:32pm, Matthew Dillon wrote:
} Subject: Re: NFS server problems on 3.4-S, any interest?
} :>From the workstation:
} :Name Mtu Network Ipkts IerrsOpktsOerrs Coll Drop
} :fxp0 150032102492 0 31653667 0 30900 0
30900 collisions is a pretty good clu
On Mar 3, 11:47am, Assar Westerlund wrote:
} Subject: Re: Keeping using locally modified source
} There's even a hack in FreeBSD cvs and cvsup to allow you to keep a
} `local' branch that's not clobbered by cvsup, namely the environment
} variable CVS_LOCAL_BRANCH_NUM.
I thought about using this
On Oct 27, 2:51pm, Julian Elischer wrote:
} Subject: Re: why FFS is THAT slower than EXT2 ?
}
}
} On Wed, 27 Oct 1999, Mike Smith wrote:
}
} > > in order to save space I gzip'ped output of my tests.
} > > ungzipping ports tarball on FreeBSD took 28 min
} > > on Linux --- about 2.5 times faste
On Oct 4, 12:52am, Darryl Okahata wrote:
} Subject: Re: Developer assessment (was Re: A bike shed ...)
} 1. Instant escalation. Example: supplicant A asks question in FreeBSD
}group. Some FreeBSD contributor says, "RTFM", and does not give any
}useful information whatsoever like which "
On Sep 5, 9:18pm, Matthew Dillon wrote:
} Subject: Re: mbuf shortage situations
} : The only reason that I see for which we would actually panic() in
} :this situation (as opposed to suffer the packet loss) is if we get to the
} :point where we're losing packets because some script kid starts
On Sep 5, 9:18pm, Matthew Dillon wrote:
} Subject: Re: mbuf shortage situations
} : The only reason that I see for which we would actually panic() in
} :this situation (as opposed to suffer the packet loss) is if we get to the
} :point where we're losing packets because some script kid starts
On Aug 21, 2:10am, Wes Peters wrote:
} Subject: mmap mapped segment length
} I discovered to my dismay today that the length field in the mmap call is
} a size_t, not an off_t. I was attempting to process a large (~50 MByte) file
} and found I was only processing the first 4 MBytes of it.
50 MB
On Aug 21, 2:10am, Wes Peters wrote:
} Subject: mmap mapped segment length
} I discovered to my dismay today that the length field in the mmap call is
} a size_t, not an off_t. I was attempting to process a large (~50 MByte) file
} and found I was only processing the first 4 MBytes of it.
50 MB
On Aug 16, 9:18pm, Terry Lambert wrote:
} Subject: Re: BSD XFS Port & BSD VFS Rewrite
} > I don't see how the namei recursion method prevents catching // as a
} > namespace escape.
}
}
} //apple-resource-fork/intermediate_dir/some_other_dir/file_with_fork
}
} You can't inherit the fact that yo
On Aug 16, 9:18pm, Terry Lambert wrote:
} Subject: Re: BSD XFS Port & BSD VFS Rewrite
} > I don't see how the namei recursion method prevents catching // as a
} > namespace escape.
}
}
} //apple-resource-fork/intermediate_dir/some_other_dir/file_with_fork
}
} You can't inherit the fact that y
On Aug 9, 9:21pm, Dan Moschuk wrote:
} Subject: Re: gethostbyaddr() and threads.
}
} | Well, I guess we might as well change the API, since everyone else does.
Unless
} | someone comes up with a bettter idea, of course :)
} |
} | -Joe
}
} The API should not change. There is already enough des
On Aug 9, 9:21pm, Dan Moschuk wrote:
} Subject: Re: gethostbyaddr() and threads.
}
} | Well, I guess we might as well change the API, since everyone else does. Unless
} | someone comes up with a bettter idea, of course :)
} |
} | -Joe
}
} The API should not change. There is already enough des
On Aug 6, 3:29pm, Sheldon Hearn wrote:
} Subject: quad_t and portability
}
} Hi folks,
}
} I want to patch wc(1) so that it uses quad_t instead of u_long. This is
} necessary if wc(1) is to produce sensible results for files containing
} more than 4GB of data.
Why not off_t, which should be por
On Aug 6, 3:29pm, Sheldon Hearn wrote:
} Subject: quad_t and portability
}
} Hi folks,
}
} I want to patch wc(1) so that it uses quad_t instead of u_long. This is
} necessary if wc(1) is to produce sensible results for files containing
} more than 4GB of data.
Why not off_t, which should be po
On Jul 4, 5:35pm, "Jonathan M. Bresler" wrote:
} Subject: Re: Pictures from USENIX
} beards are great...women love them, getting fluffed is much
} better than getting scratchedkids love them. brush the beard
} whenever you brush your hair. dont hae to deal with a buzzing razor,
} very
1 - 100 of 105 matches
Mail list logo
