In article <20190920155304.gn3...@zxy.spb.ru>, s...@zxy.spb.ru writes:
>Location of device in multi-chassis storage system is different story.
>I am don't know how to field engineer insert disks in chassis.
>For me simple is find in /var/run/dmesg.boot S/N <=> daXY mapping and
>turn ON led by
In article <20180513201344.ga34...@ptrace.hagen.corp> you write:
>I'm wondering how to get access to to the SIGWINCH signal. It is defined in
>/usr/include/sys/signal.h and behind the -D__BSD_VISIBLE switch.
>
>I can compile my code with this switch, but is this the proper way to do it?
>I would
In article
,
asom...@freebsd.org writes:
>On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen
>wrote:
>> Is there any expectation that this is going to fixed in any near future?
>No. It's fundamentally
In article <3a8b8ade882d1486aa41b448a9c83...@i805.com.br> you write:
>
>
> It's a terrible Is it a locale bug? Look!
>
>% locale
>LANG=pt_BR.UTF-8
>% touch E
>% ls -l [a-z]*
>-rw-r--r-- 1 rizzo wheel 0 7 abr 02:06 E
No, it's the specification of how character ranges in glob(3) and
< said:
> Well, it's definitely too late for 11, now.
> But, Debian is preparing to remove their heimdal package entirely,
> imminently: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837728
The primary issue, so far as I can see, is that Heimdal and MIT were
only compatible in the parts of
In article
sobo...@freebsd.org writes:
>Hi, while working on some unrelated feature I've noticed that at least
>those two system calls are not returning proper value (-1) on error.
>Instead actual errno value is returned from
In article
capq4ffvem2uzi-qptm_6msneelwft814g1ke4rgxu6mrzwy...@mail.gmail.com,
oliver.pin...@hardenedbsd.org writes:
Btw, I have found this is atf's documantation:
atf_tc_expect_signal(SIGSEGV, reaseon), with this, we could mark the
specific test case could fail / or expect to coredump.
No.
I'm
In article 559d8e55.9050...@freebsd.org a...@freebsd.org writes:
I am not suggesting this but if our man pages used all capitals to signify
important auxiliary verbs then the ERRORS sections would read as
The following error codes MAY be set in errno:
Perhaps in that case it would be more
In article
CAPQ4ffuTcN_ytcH7GPY0s6OqWK9qo6MGaVZhOB+0ojWfd=f...@mail.gmail.com
oliver.pin...@hardenedbsd.org writes:
We discovered that one of the kyua test failing from gettimeofday tests.
The error is reproducible on recent snapshot from 11-CURRENT:
In article 54320e76.3010...@pinyon.org, rcar...@pinyon.org writes:
Am I the only one attempting to maintain a local cluster using
a buildworld server and mounting /usr/src/ and /usr/obj/ via NFS?
Nope.
I intermittently run into installworld failures, usually
in sys/boot/i386 but occasionally
In article alpine.bsf.2.11.1407251459370.72...@wonkity.com you write:
Writing an article is hard. Writing a small section on how deleting
packages is different between pkg and, say, apt, is much easier. The
scope is known.
Indeed, it's pretty trivial.
I think the sort of article Craig was
In article 1396457629.2280.2.ca...@powernoodle.corp.yahoo.com,
sbr...@freebsd.org writes:
I'd like to make this change to login.conf for default installs.
This removes some amount of hackery in the ports system that is working
around our lack of UTF-8 in the base.
I'm not sure what the
In article 533b3903.7030...@rancid.berkeley.edu,
mich...@rancid.berkeley.edu writes:
I have been using FreeBSD on the desktop since 1997,
Hmmm. I'm a bit biased here, but I've been using FreeBSD on the
desktop since, well, before it was called FreeBSD. It's still my
primary platform for nearly
In article 530ea5cd.2070...@protected-networks.net,
i...@protected-networks.net writes:
sigh .. way back in the late 70's or maybe early 80's when I was
actually doing some work on compilers, we had a saying: produce correct
code even if it's not optimal or exit and tell the user why.
Producing
In article 20131221230448.ga61...@troutmask.apl.washington.edu,
Steve Kargl writes:
Other than the noise in /var/log/message, what does this provide
that 'pkg info' doesn't!
A record of when packages were installed and removed.
-GAWollman
___
In article c0a42b456769e22f908e689a1de56...@webmail.lerctr.org,
Larry Rosenman l...@lerctr.org wrote:
Error Message:
received 320KB stream in 1 seconds (320KB/sec)
receiving incremental stream of vault/var@2013-10-25 into
zroot/backups/TBH/var@2013-10-25
cannot receive incremental stream:
In article 20130714054840$7...@grapevine.csail.mit.edu,
dte...@freebsd.org writes:
How about rquery? What protocol does that use? and what does it talk to?
It accesses the sqlite database in /var/db/pkg that was previously
retrieved from the remote repository.
Question: Where can I learn more
In article 20130714064601$3...@grapevine.csail.mit.edu,
dte...@freebsd.org writes:
[I wrote:]
It accesses the sqlite database in /var/db/pkg that was previously
retrieved from the remote repository.
Now from what you explained of pkg, I'm worried that for bsdconfig:
1. Browse packages
In article 20130714191725.ga30...@stack.nl, jil...@stack.nl writes:
Apart from the annoyance of the restarts, automatic stopping and
starting is probably the best policy for having things just work. Some
daemons will crash or otherwise stop being useful when their files have
been deleted or
On Wed, 10 Jul 2013 22:12:59 +0200, Tijl Coosemans t...@freebsd.org said:
I think isnan(double) and isinf(double) in math.h should only be
visible if (_BSD_VISIBLE || _XSI_VISIBLE) __ISO_C_VISIBLE 1999.
For C99 and higher there should only be the isnan/isinf macros.
I believe you are
In article 20120712100110.ga34...@ithaqua.etoilebsd.net,
b...@freebsd.org writes:
- puppet support: (https://github.com/xaque208/puppet-pkgng)
I've actually already written one of these; it may be good to merge.
Would whoever is working on this please raise your hand?
-GAWollman
--
Garrett
In article 4fe340ff.80...@gmail.com, demelier.da...@gmail.com writes:
On 21/06/2012 14:55, Sergey Kandaurov wrote:
It returns (size_t)(-1).
I don't know how is it correct, but this conforms to C spec.
Mm, if I understand well, since it is cast to size_t, I think the return
value will be
In article 4e3d55fd.7090...@freebsd.org, nwhiteh...@freebsd.org writes:
I'm not entirely sure what you're referring to. Whenever you add a /
partition on a partitioning scheme that requires a boot partition (APM,
GPT on some platforms), the installer asks you if you want to add a boot
On Thu, 02 Sep 2010 11:36:57 +0300, Andriy Gapon a...@icyb.net.ua said:
Not sure if debugging with CAMDEBUG would be easier or not.
There could be lots of output.
I never found out, as once I rebooted with the new CAMDEBUG-ified
kernel, everything started working. No idea why. (Maybe the DVD
On Wed, 01 Sep 2010 19:16:03 +0300, Andriy Gapon a...@icyb.net.ua said:
Just want to draw attention of those who use ahci, have hald running and burn
optical media to couple of known issues:
What about those of us who use ahci, don't have hald running, and just
want to read their DVDs? I
After a recent upgrade, I switched to AHCI/CAM for my SATA devices,
including a new DVD drive. Now I find that nothing can play DVDs any
more. For example, here's what mplayer does:
8469 initial thread CALL open(0x806c25450,O_RDONLY,unused0)
8469 initial thread NAMI /dev/cd0
8469
In article 4c79499b.3050...@icyb.net.ua a...@icyb.net.ua writes:
[I wrote:]
...say what? Why is the cd driver suddenly returning ENXIO?
Strange indeed.
Can you dtrace this read? You can use combination of syscall and fbt providers
with execname predicate.
You're going to have to be much much
In article 86k4nikglg@ds4.des.no you write:
Mike Haertel m...@ducky.net writes:
GNU grep uses the well-known Boyer-Moore algorithm, which looks
first for the final letter of the target string, and uses a lookup
table to tell it how far ahead it can skip in the input whenever
it finds a
In article 20100822163644.gu2...@hoeg.nl you write:
I think that implementing a simple fgrep boils down to mmap()ing a file
and calling memmem() on the mapping to search for the input string. Of
course this relies on having an efficient memmem() implementation, for
example using one of the
In article 86bpba7nc1@ds4.des.no, d...@des.no writes:
This means you can't, say, read data from a file into a buffer and then
pass that buffer to iconv, because the buffer is not const (otherwise
you couldn't have read data into it). That seems like a pretty
fundamental flaw.
But it's a
On Sun, 6 Jun 2010 16:41:59 +, b. f. bf1...@googlemail.com said:
Is anybody planning to update the base system heimdal, which has been
largely untouched since May 2008?
I would love for it to go away entirely, and those base-system
components that depend on it to learn how to use either
In article 20100307.144736.420173476735197890@bsdimp.com, Warner
Losh i...@bsdimp.com writes:
We don't have quite as many problems as the NetBSD/OpenBSD crowd in
this respect. They tend to define a new MACHIINE more often then we
have (or will). The need for sys/arch is less severe here
On Mon, 01 Dec 2003 23:24:40 +0100, [EMAIL PROTECTED] (Dag-Erling
=?iso-8859-1?q?Sm=F8rgrav?=) said:
The problem is that the authentication information needs to be stored
somewhere, and the usual solution is to store it in the directory,
...which is usually the worst possible place. Please
On Mon, 24 Nov 2003 03:40:06 -0800, David O'Brien [EMAIL PROTECTED] said:
We have made the assumption for the first three options since day one.
Why should we change the assumptions just because we now have a dynamic
/?
Because we are not all masochists.
-GAWollman
On Fri, 21 Nov 2003 15:38:49 -0800, Tim Kientzle [EMAIL PROTECTED] said:
There have been a lot of proposed solutions:
* Rewrite NSS to not require dlopen().
* Rewrite dlopen() to not require dynamic linking.
* Don't support NSS in /bin/sh.
* Change the default script interpreter
On Fri, 21 Nov 2003 03:37:20 +0100, boyd, rounin [EMAIL PROTECTED] said:
well, try to think about non-minimalism when you're trying to track
down a kernel bug in a zillion SLOC ...
How about trying to think about FreeBSD when posting on the FreeBSD
mailing-lists.
-GAWollman
On Fri, 31 Oct 2003 18:01:34 +1100 (EST), Bruce Evans [EMAIL PROTECTED] said:
POSIX requires in addition [u]int{8,16,32}_t, and [u]int64_t if 64 bit
integer types exist. It says that the existence of int8_t implies
that a byte is 8 bits and CHAR_BIT is 8. I'm not sure what prevents
int8_t
On Thu, 30 Oct 2003 12:32:46 +0100 (CET), Harti Brandt [EMAIL PROTECTED] said:
The c89 utility (which specified a compiler for the C Language specified
by the 108 ISO/IEC 9899: 1990 standard) has been replaced by a c99 utility
(which specifies a compiler for 109 the C Language specified by the
On Thu, 30 Oct 2003 12:34:15 -0500, Barney Wolff [EMAIL PROTECTED] said:
Just a minor note: GigE should not require a crossover cable. It's
supposed to work to connect two GigE adapters with a straight-thru
cable. I verified this with two Intel em NICs, quite a while ago.
This should hardly
On Thu, 30 Oct 2003 17:40:40 -0800 (PST), Steve Lee [EMAIL PROTECTED] said:
So there is no way to mirror the root so if one drive fails,
i can't have the other drive boot up ?
There are ways to do that, but in order for that to work at all you
need to have BIOS support. Some of the ATA
On Wed, 29 Oct 2003 08:12:17 -0600, Mark Nipper [EMAIL PROTECTED] said:
initial complaints, I do think that fdisk/disklabel in sysinstall
need to be improved upon. They do not handle multi-terabyte disk
arrays properly at all
You should probably use GPT on multi-terabyte disk arrays.
I'm working on getting the AFS client to work under FreeBSD. I just
compiled a -current kernel with DEBUG_VFS_LOCKS, and before I could
even load the AFS module I had the system stop with the following
locking assertion:
getdirtybuf: 0xc2678000 interlock is not locked but should be
Backtrace
On Thu, 25 Sep 2003 19:33:06 -0700, David Schwartz [EMAIL PROTECTED] said:
think '-pthread' is a good thing. It's nice to have a portable way to say
that I want to compile POSIX code. What good is a standard if there's no
standard way to get to it?
The Standard way to do it is:
c99
I think it was John Baldwin who wrote:
I think having a magic option to gcc that translates to 'link with the
foo library' is rediculous. What's next, a gcc -math to get the math
functions in libm?
As far as POSIX is concerned, that's precisely how it works. `c99
foo.c -l m' means `link in
On Wed, 24 Sep 2003 15:19:43 -0400 (EDT), Daniel Eischen [EMAIL PROTECTED] said:
Eek, no. Libpthread is libpthread, libthr is libthr, etc. A
symlink doesn't help you anyways because the library/application
becomes dependent on the thing it is symlink'd to, not the
symlink.
That depends on
On Thu, 4 Sep 2003 18:19:02 -0700, Marcel Moolenaar [EMAIL PROTECTED] said:
In theory, yes. In practice, maybe not. If I remember correctly,
the problem we're trying to solve is twofold:
Actually, the problem we were trying to solve is simpler than that.
genassym needs to be able to compute
On Sat, 30 Aug 2003 12:23:35 -0400 (EDT), Robert Watson [EMAIL PROTECTED] said:
The only way to close this sort of race is to have a notion of a
unique process identifier that lasts beyond the lifetime of the
process itself -- i.e., the ability to return EMYSINCERESTREGRESTS
if you try to
On Sun, 24 Aug 2003 16:04:40 -0700, David Schultz [EMAIL PROTECTED] said:
Yep, looks broken. In the POSIX standard, the functionality of
statfs() is provided by statvfs(), so implementing the latter may
be a way out that doesn't involve breaking any ABIs.
statfs() is a lot more useful
On Mon, 25 Aug 2003 14:14:18 -0300, Daniel C. Sobral [EMAIL PROTECTED] said:
There are two problems with HTT. First, L1/L2 cache issues. Second, the
virtual CPUs are not independent, and there are many cases where
instructions in one virtual CPU stall the other. So take, for example,
the
On Mon, 11 Aug 2003 11:24:13 -0500, Jonathan Fosburgh [EMAIL PROTECTED] said:
- Windows on the same loop as anything else
Liberal use of zoning should help that. Each Windows HBA should be in a
seperate zone. This is from personal experience and also assumes you are
using a switched
On Sat, 09 Aug 2003 18:10:56 -0600, Aaron Wohl [EMAIL PROTECTED] said:
Anyone using a storage area network with freebsd (or linux)? Anything to
recommend as working well or to stay way from?
We have two SANs with FreeBSD and Debian servers on them, sharing (and
booting from) a generic RAID
On Thu, 12 Jun 2003 22:22:07 +1000, Tim Robbins [EMAIL PROTECTED] said:
builtin alloca() until we figure out how to fix the one in libc.
It is fundamentally impossible to ``fix'' the alloca() implementation
in libc. alloca() CANNOT be implemented that way. If GCC's builtin
alloca() is
On Thu, 12 Jun 2003 15:38:49 +1000, Tim Robbins [EMAIL PROTECTED] said:
Misbehaving in what way? CSTD=c99 causes gcc to use alloca() from
libc instead of its builtin version. Perhaps alloca() in libc is
broken -- any bugs in it would have been covered up by gcc until
now.
alloca() in libc is
On Thu, 12 Jun 2003 11:37:03 -0700, Tim Kientzle [EMAIL PROTECTED] said:
Sounds like alloca() should simply be stricken from libc
on all architectures.
Yes. (For values of `all' being `i386'.)
Might also be a good idea to begin removing uses of it.
Not necessarily. There's nothing wrong,
I just noticed my news server hanging in nbufkv state, apparently
having hosed itself overnight (about 15 hours ago); expire was still
running, although it was not the only process waiting. I can't find
anything in the -current archives from this century. Any suggestions?
FWIW, most of the
On Mon, 2 Jun 2003 08:09:17 +0300, Vallo Kallaste [EMAIL PROTECTED] said:
FreeBSD 5.x series is slowly progressing, but is nowhere near to
production quality. As the things are currently, you simply waste
your time.
I'm running an old 5.1-current and a more recent 5.1-beta of about a
week ago
On Wed, 12 Mar 2003 16:51:15 -0800, David Schultz [EMAIL PROTECTED] said:
A real problem is that a swapped out process' uarea has to be
paged back in, even when no memory is available. I don't think
there's an easy way around that, given that you need the uarea and
kernel stack to handle the
I've been trying to figure out why my Intel SR2100 servers would not
boot with ACPI enabled, hanging uninterruptibly after probing the ACPI
timer. I experimented with disabling various subsystems, and came up
with the following results:
- With `pci_link' disabled, the boot gets as far as
On Tue, 11 Mar 2003 19:42:41 +0300, Andrey A. Chernov [EMAIL PROTECTED] said:
What to do, if, say, C99 program want to use some POSIX functions from
lower (and not from higher) POSIX standard?
Programmer error. Either it's a C99 program or it's an old-POSIX
program; it cannot be both.
On Tue, 11 Mar 2003 00:38:08 +0100, Poul-Henning Kamp [EMAIL PROTECTED] said:
Has anybody found out what the standards conformant thing is for /dev/fd ?
There is no standard, other than Tenth Edition and Plan 9. Most
programs which use it expect it to behave like one or the other.
-GAWollman
On Mon, 10 Mar 2003 18:47:15 -0500 (EST), Alien Space Bats attacked
and caused me to utter:
There is no standard, other than Tenth Edition and Plan 9. Most
programs which use it expect it to behave like one or the other.
s/one or the other/that/
-GAWollman
To Unsubscribe: send mail to
On Sat, 8 Mar 2003 11:19:43 -0500, Craig Rodrigues [EMAIL PROTECTED] said:
Does the use of #warning need to be protected by
#if __GNUC__ in FreeBSD header files?
No, it needs to be replaced by the standard `#error' directive
instead. I asked portmgr to do a run on the portsd cluster with this
On Sat, 1 Mar 2003 22:18:12 +1100 (EST), Bruce Evans [EMAIL PROTECTED] said:
Interestingly, socreate() in Lite2 always does a can-wait malloc() so
our current soalloc(M_NOWAIT) does the same thing as Lite2 and is only
wrong if the FreeBSD change from can-wait to can-wait-if p != 0
change was
On Fri, 28 Feb 2003 14:06:13 -0700 (MST), M. Warner Losh [EMAIL PROTECTED] said:
Also, 386-core based chips are still in production (or have been in
the last year). It has only been very recently that the embedded
chips have transitioned to 486. Calling them, as others have, 10
years
On Thu, 27 Feb 2003 08:40:22 -0800 (PST), John Polstra [EMAIL PROTECTED] said:
FreeBSD violates POSIX in this respect. The 1003.1 standard
(section 2.5) requires pthread_t to be an arithmetic type. We are
non-compliant in the same way for almost all of the primary
thread-related types:
Not
On Thu, 27 Feb 2003 09:06:41 -0800 (PST), John Polstra [EMAIL PROTECTED] said:
Interesting. I don't have that standard and wasn't aware of the
change.
You do. It's available for free on the Web from opengroup.org. Free
registration is required. Mike may still have some copies of the
On Thu, 27 Feb 2003 23:09:56 -0500 (EST), Geoffrey [EMAIL PROTECTED] said:
I was evidently under the mistaken impression this was about nuts
and bolts. If we are to focus on window dressing, we are definitely
hozed.
We focus on what's actually useful to the plurality of users. Support
On Thu, 20 Feb 2003 18:39:33 -0800 (PST), Julian Elischer [EMAIL PROTECTED] said:
What would be really cool is if more config files could
do 'includes' so that you could have a syslogd.local.conf
wher eall your local entries could be. In addition you could make it
look in
On Sun, 9 Feb 2003 22:47:47 +1100 (EST), Bruce Evans [EMAIL PROTECTED] said:
_fpathconf() is quite different from __semctl. It is not a syscall.
It is a weak alias for fpathconf() which is prototyped normally in
unistd.h. The prototype for fpathconf() should be turned into
a prototype for
On Sun, 09 Feb 2003 19:43:38 +0100, Marcin Dalecki [EMAIL PROTECTED] said:
Trying to use a compiler different from GCC I have found the folowing error
/usr/include/sys/syslimits.h, line 42: Error:
[ISO 6.8]: Unknown preprocessing directive, '#warning'.
It should probably be a #error
On Sat, 01 Feb 2003 16:02:57 -0800, Bakul Shah [EMAIL PROTECTED] said:
I can't see what actual error is avoided by this warning.
It's a potential error -- if there were an actual error, it would be
an error and not a warning.
The issue is simple:
Say you have an object and a function declared
On Sat, 1 Feb 2003 19:31:47 -0500 (EST), I wrote:
union baz {
int foo;
struct frotz *gorp;
} foobaz;
#define foo foobaz.foo
Oops... What I meant to say:
union baz {
int bazu_foo;
struct frotz *bazu_gorp;
On Fri, 31 Jan 2003 09:33:55 -0800, Kris Kennaway [EMAIL PROTECTED] said:
Hmm..there must be something in the configure script that thinks we do.
http://bento.freebsd.org/errorlogs/alpha-5-latest/nvi-1.81.5_2.log
It erroneously thinks that because we have the grantpt() function, we
have
On Wed, 29 Jan 2003 18:17:31 -0800, Kirk McKusick [EMAIL PROTECTED]
said:
The other alternative would be to
create a setuid-to-root program that would take a snapshot and
chown it to the user that does dumps.
I think this would actually be a useful feature for more than just
dumps. I might
On Wed, 22 Jan 2003 11:14:47 +0100 (CET), Jan Srzednicki
[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, because
On Wed, 22 Jan 2003 11:32:12 -0800, David Schultz [EMAIL PROTECTED]
said:
Unfortunately, I think it is possible that the unreferenced inode
has not been initialized, even though it is allocated in the inode
bitmap, so you could potentially get random junk.
That is definitely true on UFS2,
On Sat, 18 Jan 2003 10:25:53 -0500, Kutulu [EMAIL PROTECTED] said:
I upgraded my system last night to the latest -CURRENT and noticed a change
in the daily mail cleanup. Unfortunately, I'm not running sendmail, so now
I'm getting:
If you can come up with a good (silent) way to detect whether
On Mon, 6 Jan 2003 17:22:58 +0200, Andy Fawcett [EMAIL PROTECTED] said:
#if defined(QT_THREAD_SUPPORT) defined(_POSIX_THREAD_SAFE_FUNCTIONS)
This conditional is erroneous, so you should definitely bug Troll Tech.
It should instead read:
#if defined(QT_THREAD_SUPPORT)
On Tue, 31 Dec 2002 00:34:04 -0500 (EST), Matthew N. Dodd [EMAIL PROTECTED] said:
I just installed RC2 using a 3C574B with the 'ep' driver; worked just fine
aside from needing to re-roll kern.flp and mfsroot.flp to support OLDCARD.
My 3C589D works just fine in 5-current with NEWCARD.
On Tue, 24 Dec 2002 12:40:25 +0100, Poul-Henning Kamp [EMAIL PROTECTED] said:
Isn't there a pretty obvious race between the revoke() and the open() ?
To the extent that the race matters, it is obviated by making sure
that only the current user has permission to open the device. If the
user
On Tue, 24 Dec 2002 15:43:56 +0100, [EMAIL PROTECTED] said:
There is no way you can close the race between:
revoke(/dev/ttyfoo);
and
open(/dev/ttyfoo);
Not even in init(8). There is always the risk that another process
opens the device between the two.
If that process
On 17 Dec 2002 16:35:50 -0600, Ryan Sommers [EMAIL PROTECTED] said:
I'm wondering what it's doing because it isn't copying over ports
very fast.
It's slow because it's creating lots of very small directories.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
On Sun, 15 Dec 2002 10:26:22 -0800 (PST), Matthew Dillon
[EMAIL PROTECTED] said:
Now you are forcing me to go to core. It's absolutely ridiculous and
you know it. Goddamn it, next time I won't even bother posting if all
I get is this sort of crap.
All the better, if you refuse
On Sun, 15 Dec 2002 11:41:26 -0800 (PST), Matthew Dillon
[EMAIL PROTECTED] said:
If people are reasonable with me, I am reasonable right back. If
people are unreasonable, they shouldn't expect me to be reasonable
in response. It's really that simple.
As a FreeBSD developer, you
On Fri, 13 Dec 2002 08:41:16 -0800, Joe Kelsey [EMAIL PROTECTED] said:
So, is there some mechanism I am missing? Is there a layer between the
application calling sem_open and the kernel receiving the parameters
that strips it down to the last component? If there is a higher level
On Fri, 13 Dec 2002 12:02:47 -0500, Craig Rodrigues [EMAIL PROTECTED] said:
So apart from the leading slash character, nothing is mentioned about
embedded slashes in the semaphore name. What's the right behavior
for FreeBSD then?
The reason why the standard is written that way was to allow
On Fri, 13 Dec 2002 11:05:45 -0800, Alfred Perlstein [EMAIL PROTECTED] said:
http://www.freebsd.org/cgi/man.cgi?query=sem_openapropos=0sektion=0manpath=SunOS+5.7format=html
BZZT!
Appeal to irrelevant authority.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
On Fri, 13 Dec 2002 12:02:02 -0800, Kevin Oberman [EMAIL PROTECTED] said:
Thanks for pointing out the obvious! (Although I am confused by why it
wiped the root partition which is BEFORE swap.)
Because it starts at the end of the specified partition and works its
way backwards. (The hope is to
On Wed, 11 Dec 2002 23:09:46 -0800 (PST), Nate Lawson [EMAIL PROTECTED] said:
I've noticed this too with fxp. It only happens while in ddb and I
thought it was my fault (I was debugging some networking problems).
It happens when the NIC's receive queue fills up. When you're in DDB,
the
On Mon, 09 Dec 2002 10:26:49 -0700 (MST), M. Warner Losh [EMAIL PROTECTED] said:
may != MUST. We do not pollute the name space. Providing additional
facilities pollutes the name space, breaking strictly conforming
programs.
Not necessarily. The Standard reserves certain namespaces for the
lock order reversal
1st 0xc37e7a68 vnode interlock (vnode interlock) @ ../../../kern/vfs_subr.c:939
2nd 0xc043d720 vm page queue mutex (vm page queue mutex) @ ../../../vm/vm_kern.c:424
ident says:
/sys/kern/vfs_subr.c:
$FreeBSD: src/sys/kern/vfs_subr.c,v 1.419 2002/10/26 14:38:21 rwatson
On Tue, 19 Nov 2002 21:07:49 -0600, Sean Kelly [EMAIL PROTECTED] said:
Actually it is the 'c' slice that is generally used to indicate the whole
disk. This is still the case in 5.0. However, I am unable to tell you what
'd' used to represent. I am also clueless on this particular detail.
No,
On Wed, 20 Nov 2002 11:39:22 +0800, kai ouyang [EMAIL PROTECTED] said:
I don't know why the 'c' partition doesn't start at 0.
It is strange.
For backwards compatibility, the FreeBSD 4.x kernel would fake up the
partition tables so that they would look like old (pre-slicing)
FreeBSD partition
On Sun, 17 Nov 2002 15:51:59 +0100, Alexander Leidinger [EMAIL PROTECTED]
said:
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.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
On Mon, 18 Nov 2002 12:08:49 -0800, Kris Kennaway [EMAIL PROTECTED] said:
It's described in the file itself. Can you please file a PR about the
missing manpage documentation?
make.conf is no longer installed in -current. A user trying to
understand why some glop is being added automatically
On Mon, 18 Nov 2002 22:31:28 -0600, Brian Smith [EMAIL PROTECTED] said:
Is this the recommended method of preventing these problems?
The recommended method of preventing these problems generally is to
use POSIX semaphores (or other POSIX synchronization mechanisms
appropriate to threaded
On Wed, 13 Nov 2002 10:07:22 -0800 (PST), Nate Lawson [EMAIL PROTECTED] said:
Thanks, that's what I was expecting. The attached patch provides the
following behavior:
sleep 0 = exit 0 immediately
sleep [ \t]*1 = sleep 1 second
sleep [ \t]*\.2zzz = sleep .2 seconds
sleep [ \t]*-.* =
On Wed, 13 Nov 2002 11:26:44 -0800 (PST), Nate Lawson [EMAIL PROTECTED] said:
So sleep -1 should sleep for ~0UL seconds? And should usage() ever be
called then?
Well, the standard says that anything might happen as a result of
`sleep -- -1'. I'm just pointing out why the standard says so.
On 11 Nov 2002 17:56:08 +0100, Marc Recht [EMAIL PROTECTED] said:
I'm thinking more of it like an aggregation. IMHO it should be possible,
if the user wants to, to get POSIX 199506 and BSD.
That would be very difficult, since FreeBSD never supported that
version (indeed, never even claimed
On Mon, 11 Nov 2002 09:54:58 -0500, Mike Barcroft [EMAIL PROTECTED] said:
/* 1003.2-1992 */
-#if __POSIX_VISIBLE = 199209
+#if __POSIX_VISIBLE = 199209 || __XSI_VISIBLE
size_tconfstr(int, char *, size_t);
int getopt(int, char * const [], const char *);
__XSI_VISIBLE should
1 - 100 of 480 matches
Mail list logo