* Jonathan Lemon <[EMAIL PROTECTED]> [010616 00:56] wrote:
> On Fri, Jun 15, 2001 at 07:44:59PM -0400, Bosko Milekic wrote:
>
> > > > Here are some performance results. Keep in mind that we're still under
> > > > Giant.
> > > >
> > > > http://people.freebsd.org/~bmilekic/code/mb_alloc/results.
On Sat, 16 Jun 2001 14:34:07 +1000 (EST)
Bruce Evans <[EMAIL PROTECTED]> wrote:
BE> We are (or at least I am) talking about changing it to prevent links to a
BE> string that can _never_ be a valid pathname. Fortunately, in POSIX there
BE> is only one such string (the empty string).
Mayb
I'm interested in learning more about Giant. Is there
any helpful websites people can recommend?
TIA,
Chris Dempsey
__
Do You Yahoo!?
Spot the hottest trends in music, movies, and more.
http://buzz.yahoo.com/
To Unsubscribe: send mail to [EMAIL
From: Matt Dillon <[EMAIL PROTECTED]>
Subject: Re: symlink(2) [Was: Re: tcsh.cat]
Date: Fri, 15 Jun 2001 22:01:47 -0700 (PDT)
> Symlinks do not have to contain paths. People use them for all sorts
> of things so it would be totally inappropriate to put any sort of
True. It would break
:...
:> It has been on evey platform I have ever used ln -s on.
:>
:> DW> One may well argue that this is "broken" in some way(s). Still, changing
:> DW> it at this point could well be considered a POLA violation, at best.
:>
:> I would argue loud and long that changing that *would*
On Fri, Jun 15, 2001 at 07:44:59PM -0400, Bosko Milekic wrote:
> > > Here are some performance results. Keep in mind that we're still under
> > > Giant.
> > >
> > > http://people.freebsd.org/~bmilekic/code/mb_alloc/results.html
> >
> > Just for comparision, 6-way results are at:
> >
> >
On Fri, 15 Jun 2001, Steve O'Hara-Smith wrote:
> On Fri, 15 Jun 2001 06:31:12 -0700 (PDT)
> David Wolfskill <[EMAIL PROTECTED]> wrote:
>
> DW> Indeed: it is my understanding that the "path name" interpretation is
> DW> an issue at the time of reference, not (necessarily) the time of
> DW> creati
On Fri, Jun 15, 2001 at 06:55:29PM -0500, Jonathan Lemon wrote:
> > In any case, the mb_alloc code you used still has the malloc() and
> > free() calls during cluster allocation and freeing and still, it looks to
> > me as very comparable nonetheless.
>
> The results look good to me; the on
On Fri, Jun 15, 2001 at 02:08:03PM +0100, Richard Tobin wrote:
> > P>The string pointed to by path1 shall be treated only as a character
> > P>string and shall not be validated as a pathname.
>
> I have heard on several occasions of peope using symlink(2) to
> atomically store some small
On Fri, Jun 15, 2001 at 07:44:59PM -0400, Bosko Milekic wrote:
>
> On Fri, Jun 15, 2001 at 06:32:55PM -0500, Jonathan Lemon wrote:
> > On Fri, Jun 15, 2001 at 06:54:21PM -0400, Bosko Milekic wrote:
> > >
> > > Hi Folks,
> > >
> > > Here are some performance results. Keep in mind that we're st
On Fri, Jun 15, 2001 at 06:32:55PM -0500, Jonathan Lemon wrote:
> On Fri, Jun 15, 2001 at 06:54:21PM -0400, Bosko Milekic wrote:
> >
> > Hi Folks,
> >
> > Here are some performance results. Keep in mind that we're still under
> > Giant.
> >
> > http://people.freebsd.org/~bmilekic/code/mb_all
Jonathan Smith <[EMAIL PROTECTED]> writes:
> I am thinking of what _was_ 'sysctl hw.atamodes' (or similar) in -STABLE.
You are not Terry.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Fri, Jun 15, 2001 at 06:54:21PM -0400, Bosko Milekic wrote:
>
> Hi Folks,
>
> Here are some performance results. Keep in mind that we're still under
> Giant.
>
> http://people.freebsd.org/~bmilekic/code/mb_alloc/results.html
Just for comparision, 6-way results are at:
http://www.flug
Riccardo Torrini <[EMAIL PROTECTED]> writes:
[snip]
> Only shutdown stop it, but with message:
>"some processes would not die; ps axl advised"
> After reboot all partitions are clean, no need of fsck.
precisely, this is what we could call a driver (kernel?) deadlock.
what's the ps axl output
I am thinking of what _was_ 'sysctl hw.atamodes' (or similar) in -STABLE.
j.
--
When you get the choice to sit it out or dance, I hope you dance
-- I Hope You Dance, Lee Ann Womack
Jon C.: [Microsoft] pops up all over the place
Jon S.: Like a Virus
-- From an online discussion
Hi Folks,
Here are some performance results. Keep in mind that we're still under
Giant.
http://people.freebsd.org/~bmilekic/code/mb_alloc/results.html
Terry, is this OK for you?
Regards,
--
Bosko Milekic
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
Terry Lambert <[EMAIL PROTECTED]> writes:
> So we removed it from the kernel config... and the damn
> thing enabled it again.
You're thinking of ATA_ENABLE_ATAPI_DMA, which is only for ATAPI
devices (i.e. CD-ROMs), not for disks.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: s
< said:
> POSIX explicitly disallow "" filenames everywhere. I think it should be
> so for symlinks too.
But it doesn't, and that's the end of it for at least another five
years.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the me
On Fri, Jun 15, 2001 at 15:53:10 -0400, Garrett Wollman wrote:
> < said:
>
> > Here's an example of a complication: what is the semantics of /tmp/foo/bar
> > where foo is a symlink to ""? I think the pathname resolves to
> > /tmp//bar and then to /tmp/bar, but this is surprising since foo doesn'
< said:
> Maybe, but this doesn't seem to be permitted by POSIX.1-200x:
The response I got to a similar question about symbolic links suggests
that the definition of ``path name resolution'' is supposed to be the
final word on the meaning and interpretation of symbolic links.
-GAWollman
To Un
< said:
> Here's an example of a complication: what is the semantics of /tmp/foo/bar
> where foo is a symlink to ""? I think the pathname resolves to
> /tmp//bar and then to /tmp/bar, but this is surprising since foo doesn't
> point anywhere.
But this is at least consistent with the historic (p
On Fri, 15 Jun 2001 06:31:12 -0700 (PDT)
David Wolfskill <[EMAIL PROTECTED]> wrote:
DW> Indeed: it is my understanding that the "path name" interpretation is
DW> an issue at the time of reference, not (necessarily) the time of
DW> creation. It has, to the best of my knowledge, been valid to crea
Ah- I didn't think your mail needed apologies... but I do thank you for the
followup!
On Fri, 15 Jun 2001, Szilveszter Adam wrote:
> Hello,
>
> First of all I would like to apologise for my mail yesterday; we had a
> party here at the dorm and went a bit crzy... corollary is, next time I
David Wolfskill([EMAIL PROTECTED])@2001.06.15 06:53:27 +:
> And another:
>
> dhcp-133[1] ls -l .netscape/lock
> lrwxrwxr-x 1 david wheel 13 Jun 15 06:40 .netscape/lock -> 1.0.0.127:612
>
> :-},
> david (making no claims about what is "good practice", here)
this is actually more performa
Andrey A. Chernov([EMAIL PROTECTED])@2001.06.15 16:02:50 +:
> On Fri, Jun 15, 2001 at 13:15:04 +1000, Bruce Evans wrote:
>
> > Related bugs:
> > - symlink(2) is happy to create a symlink to the empty pathname although
> > empty pathnames are invalid.
>
> Maybe we need to fix symlink(2) the
Salve,
Con DirectLine potrai riferirti ad un unico operatore per tutte le tue
chiamate urbane, interurbane, internazionali e verso cellulari a tariffe
MAI VISTE...
Segnalando il servizio ai tuoi amici, arriverai ad eliminare del tutto la
bolletta telefonica, e se gli amici sono tanti... potrai a
Hi,
I just upgraded to yesterday's current code and I find myself without a
mouse...
I have a PS/2 one (as many others) and it doesn't work anymore, being under
the console or X.
FreeBSD 5.0-CURRENT #69: Fri Jun 15 16:34:50 CEST 2001
[EMAIL PROTECTED]:/src/src/sys/compile/CAERDONN
Timecount
>Date: Fri, 15 Jun 2001 23:33:07 +1000 (EST)
>From: Bruce Evans <[EMAIL PROTECTED]>
>> I have heard on several occasions of peope using symlink(2) to
>> atomically store some small piece of information for locking purposes.
>> (Symlink was more reliably atomic over NFS than other methods.) So it
On Fri, 15 Jun 2001, Richard Tobin wrote:
> > P>The string pointed to by path1 shall be treated only as a character
> > P>string and shall not be validated as a pathname.
>
> I have heard on several occasions of peope using symlink(2) to
> atomically store some small piece of information
>Date: Fri, 15 Jun 2001 22:57:56 +1000 (EST)
>From: Bruce Evans <[EMAIL PROTECTED]>
>> Maybe we need to fix symlink(2) then ?
>Maybe, but this doesn't seem to be permitted by POSIX.1-200x:
>P>int symlink(const char *path1, const char *path2);
>P>...
>P>The string pointed to by path1
> P>The string pointed to by path1 shall be treated only as a character
> P>string and shall not be validated as a pathname.
I have heard on several occasions of peope using symlink(2) to
atomically store some small piece of information for locking purposes.
(Symlink was more reliably ato
On Fri, 15 Jun 2001, Andrey A. Chernov wrote:
> On Fri, Jun 15, 2001 at 13:15:04 +1000, Bruce Evans wrote:
>
> > Related bugs:
> > - symlink(2) is happy to create a symlink to the empty pathname although
> > empty pathnames are invalid.
>
> Maybe we need to fix symlink(2) then ?
Maybe, but t
Hello,
maybe it was the confg-changes, it simply happend during the last
couple of days.
Michael
On Fri, 15 Jun 2001, Alexander Leidinger wrote:
> On 15 Jun, Michael Class wrote:
>
> > after the recent linker_set-changes on my system the ps2-mouse
>
> I thought the recent change to config was
On Fri, Jun 15, 2001 at 13:15:04 +1000, Bruce Evans wrote:
> Related bugs:
> - symlink(2) is happy to create a symlink to the empty pathname although
> empty pathnames are invalid.
Maybe we need to fix symlink(2) then ?
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [E
On 15 Jun, Michael Class wrote:
> after the recent linker_set-changes on my system the ps2-mouse
I thought the recent change to config was the problem (forgetting the
hints also disables the mouse).
> is not working any more. It seems that a second (virtual ;-)
> keyboard is detected (atkbd1) a
Hello all,
after the recent linker_set-changes on my system the ps2-mouse
is not working any more. It seems that a second (virtual ;-)
keyboard is detected (atkbd1) and that this messes up things.
I can reproduce this with a GENERIC-kernel (output of dmesg is
appended). The system is a dual-prox
Hello,
First of all I would like to apologise for my mail yesterday; we had a
party here at the dorm and went a bit crzy... corollary is, next time I
won't party and email at the same evening, they just don't mix...:-)
In my opinion, you are looking for this fix:
markm 2001/06/07 01:4
37 matches
Mail list logo
