On Fri, 2002-11-08 at 22:23, Hiten Pandya wrote:
> On Wed, Nov 06, 2002 at 10:27:47PM +0100, Frode Nordahl wrote the words in effect of:
> > Hello,
> >
> > I have been searching mailing lists and my friend Google for information
> > about a acpid (like apmd) implementation for FreeBSD, but I have
In message: <[EMAIL PROTECTED]>
Brooks Davis <[EMAIL PROTECTED]> writes:
: On Fri, Nov 08, 2002 at 04:16:06PM -0700, M. Warner Losh wrote:
: > I'd love for there to be a way to know which binaries use __sF.
:
: The following script run on your bin, sbin, lib, and libexec directories
:
At Fri, 8 Nov 2002 00:58:10 + (UTC),
Joel M. Baldwin <[EMAIL PROTECTED]> wrote:
> > I got same result on my box. Only solution I have is deinstall
> > dnetc. :-)
...
> What motherboard/CPU is this on?
> Have you tried a nonSMP kernel?
It's SuperMicro's P3TDDE with dual P-III (1.13GHz). Yes,
On Fri, 8 Nov 2002, Andrea Campi wrote:
> Hi all,
>
> for months now I've been having a reproducible hang under load
> (make -j4 buildworld on a uniprocessor with plenty of RAM). I transcribed
> some info which might be useful to debug it; it seems to me this is a
> deadlock (am I right?). I'll le
Ok here are some thought about devfs
1/ devices are coming and going and becoming more portable
2/ disk partitioning schemes are also multiplying
3/ devices such as usb or bluetooth nets can be configured in arbitray ways
4/ there are more than 256 types of device in the world.
With these in mind
My normal server is offline.
Anything sent to me in the last day or so will be in a queue waiting for it to
come back online... meanwhile, I have undiverted my freebsd mail and am reading it on
hub..
So if you are waiting for me to respond to something you sent today...
contact me again.
julian
On Fri, Nov 08, 2002 at 06:14:09PM -0600, Anti wrote:
> and if you must? dual boot 4.7 here so was able to create the
> devices easy enough from there and all is well, but i'd like to do
> it on some other boxes where this isn't an option...
Perhaps you could explain why it's not an option.
Kris
At 6:13 PM -0500 11/8/02, Daniel Eischen wrote:
On Fri, 8 Nov 2002, M. Warner Losh wrote:
In message: <[EMAIL PROTECTED]>
Daniel Eischen <[EMAIL PROTECTED]> writes:
: All the ports are going to be rebuilt for the release anyways,
: so this doesn't affect fresh installs, correct?
On Wed, Oct 30, 2002 at 02:36:01PM -0800, Bill Fenner wrote:
[ snip ]
>
> The update to the /etc/rc.d infrastructure keeps the ability to run
> twice, but does not actually run it twice. I started creating an
> /etc/rc.d/sysctl-last that would run "/etc/rc.d/sysctl lastload",
> but realized that I
On Fri, Nov 08, 2002 at 06:26:13PM -0800, Doug Barton wrote:
>
> I'm not sure I like this change actually... having the debug output go
> to syslog is very useful if you don't have a console on the system for
> whatever reason.
>
I agree.
It's also usefull when you're in an X session or other
con
On Fri, Nov 08, 2002 at 10:09:10PM -0500, Hiten Pandya wrote:
> P.S. hw.pci should moved somewhere global, but donno how this can be
> done or even if it is possible to do.
I think you just need a SYSCTL_DECL(_hw_pci) in scope.
-- Brooks
--
Any statement of the form "X is the one, true Y" is F
On Fri, Nov 08, 2002 at 05:45:00PM -0500, Matthew N. Dodd wrote the words in effect of:
> On Fri, 8 Nov 2002, Terry Lambert wrote:
> > "Matthew N. Dodd" wrote:
> > > Recompile your kernel with
> > >
> > > options PCI_ALLOW_UNSUPPORTED_IO_RANGE
> >
> > Given the number of times that this comes up, c
and if you must? dual boot 4.7 here so was able to create the devices easy enough from
there and all is well, but i'd like to do it on some other boxes where this isn't an
option...
On Sat, 09 Nov 2002 00:14:08 +0100
Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
> In message <[EMAIL PROTECTED
Gordon Tetlow wrote:
>
> On Fri, Nov 08, 2002 at 09:06:15AM -0800, Gordon Tetlow wrote:
> > gordon 2002/11/08 09:06:15 PST
> >
> > Modified files:
> > etc rc.subr
> > Log:
> > Diff reduction to NetBSD:
> >
> > Fix a minor grammer nit.
> > Get rid of _echo that u
On Fri, Nov 08, 2002 at 05:05:23PM -0800, Brooks Davis wrote:
> On Fri, Nov 08, 2002 at 04:16:06PM -0700, M. Warner Losh wrote:
> > I'd love for there to be a way to know which binaries use __sF.
>
> The following script run on your bin, sbin, lib, and libexec directories
> does a pretty decent jo
On Fri, Nov 08, 2002 at 05:22:13PM -0800, [EMAIL PROTECTED] wrote:
> BTW, I did remove the $ from $*. I thought it was running too fast :-)
You're supposed to pass it a list of files not run it in a directory.
-- Brooks
--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerpr
Quoting Brooks Davis <[EMAIL PROTECTED]>:
| On Fri, Nov 08, 2002 at 04:16:06PM -0700, M. Warner Losh wrote:
| > I'd love for there to be a way to know which binaries use __sF.
|
| The following script run on your bin, sbin, lib, and libexec directories
| does a pretty decent job of finding f
On Fri, Nov 08, 2002 at 04:16:06PM -0700, M. Warner Losh wrote:
> I'd love for there to be a way to know which binaries use __sF.
The following script run on your bin, sbin, lib, and libexec directories
does a pretty decent job of finding files that contain refrences to __sF
and listing the ports
Daniel Eischen wrote:
> I'm not even close to a shared library/linker expert, but
> I thought there was a way to have something run when an
> object file got loaded. From rtld(1):
>
> After all shared libraries have been successfully loaded, ld-elf.so.1
> proceeds to resolve external referenc
Multilingual message - scroll down!
Deutsch:
---
Die Antivirus checkroutine unseres Mailservers (ms.dindi.com) hat festgestellt,
dass Sie von "[EMAIL PROTECTED]" (diese Adresse könnte gefälscht sein!!) eine
Email-Nachric
David Schultz wrote:
> 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,
On Fri, 8 Nov 2002, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Daniel Eischen <[EMAIL PROTECTED]> writes:
> : On Fri, 8 Nov 2002, M. Warner Losh wrote:
> :
> : > In message: <[EMAIL PROTECTED]>
> : > Daniel Eischen <[EMAIL PROTECTED]> writes:
> : > : All the
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
I was trying to do 'portupgrade portupgrade' today and my -CURRENT
system rebooted. Strange - I haven't seen such behaviour before. I
believe it wouldn't happen before my last upgrade (it was 30-10-2002
-CURRENT system, and I cvsup'ed it on 6-11-2002)
After reboot I retried portupgrade - samre res
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
In message: <[EMAIL PROTECTED]>
Daniel Eischen <[EMAIL PROTECTED]> writes:
: On Fri, 8 Nov 2002, M. Warner Losh wrote:
:
: > In message: <[EMAIL PROTECTED]>
: > Daniel Eischen <[EMAIL PROTECTED]> writes:
: > : All the ports are going to be rebuilt for the release anyways,
:
> > I mean *all* the cruft -- old modules and config files, deprecated binaries
> > and man pages, even old shlibs if it's safe.
>
> I agree with you, and I was giving an example that a lesser form of
> this is already required during the upgrade.
>
> It would be VERY useful if someone could deve
In message <[EMAIL PROTECTED]>, Anti writes:
>
>how are you supposed to get rid of devfs?
You're not.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can ade
On Fri, 8 Nov 2002, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Daniel Eischen <[EMAIL PROTECTED]> writes:
> : All the ports are going to be rebuilt for the release anyways,
> : so this doesn't affect fresh installs, correct? It is only a
> : problem when mixing older 4.
On Fri, 8 Nov 2002, Terry Lambert wrote:
> Horen wrote:
> > Now the missing facts:
> >
> >4.x binaries will not run on 5.0, lib.c inconsistency.
>
> You are not running the most recent 5.x. We can't help you, I
> think.
>
>
> >Identical XFree86 sources compiled nativly on 4.6, 4.7 and
"M. Warner Losh" wrote:
> My plan is as follows:
>
> 1) Restore __sF to libc for 5.0.
> 2) Fix 4.x binaries so that __sF isn't referened in new
>binaries. This should have been done in Aug 2001, but
>wasn't.
>
> Depending on how things go, __sF will be rem
how are you supposed to get rid of devfs? building a kernel without it won't boot
since there are no devices... shouldn't there be a ./MAKEDEV all or something
underneath the devfs mount so you can boot without it? or am i missing something?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "
On Fri, 8 Nov 2002, Terry Lambert wrote:
> "Matthew N. Dodd" wrote:
> > Recompile your kernel with
> >
> > options PCI_ALLOW_UNSUPPORTED_IO_RANGE
>
> Given the number of times that this comes up, can we change that to
> "PCI_ALLOW_ACTUALLY_SUPPORTED_IO_RANGE_WHICH_IS_NON_DEFAULT_TO_BE_ANNOYING"
> ?
Hiten Pandya wrote:
> > I have been searching mailing lists and my friend Google for information
> > about a acpid (like apmd) implementation for FreeBSD, but I have found
> > nothing.
> >
> > Does one exist anywhere, or has anyone started out on something without
> > telling anyone? :)
>
> Why do
Ray Kohler wrote:
> > Yes, it's already a mandatory step (remove old includes, or you can't
> > build C++ programs).
>
> I mean *all* the cruft -- old modules and config files, deprecated binaries
> and man pages, even old shlibs if it's safe.
You need a registration system which can subsume all
"Matthew N. Dodd" wrote:
> Recompile your kernel with
>
> options PCI_ALLOW_UNSUPPORTED_IO_RANGE
Given the number of times that this comes up, can we change that to
"PCI_ALLOW_ACTUALLY_SUPPORTED_IO_RANGE_WHICH_IS_NON_DEFAULT_TO_BE_ANNOYING"
?
Thanks.
-- Terry
To Unsubscribe: send mail to [EMAIL
Maksim Yevmenkin wrote:
> 1. Hardware: Attach the USB device into a USB port closer
> to the root hub.
>
> 2. Software: Detect the CRC/Timeout error and count exceeded
> and attempt to re-queue the packets while changing the length
> of the packets. Changing the length of the packets will change
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Andrew Kenneth Milton wrote:
> +---[ Steve Kargl ]--
> |
> | I agree with Dan. Let's do it now. My understanding is
> | that 5.0 will be an "early adopter" release and production
> | systems should run 4.7{8,9,..} until 5.1 is released.
> |
> | To accomplish the change, I
Martin Faxer wrote:
> the nvidia supplied drivers appear to work fine except for libGL* which
> are compiled on an older system and thus give:
> /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libGL.so.1: Undefined symbol
> "__sF"
>
> any way to get around this?
Yes. Run a newer version of -current. W
Daniel Eischen wrote:
> > By default, ti_jump_table entries contain pointers to dummy function like
> > _return_zero if no threading library is loaded. When the threading library is
> > loaded, ti_jump_table is populated with new pointers to functions implemented
> > in threading library library. G
Horen wrote:
> Now the missing facts:
>
>4.x binaries will not run on 5.0, lib.c inconsistency.
You are not running the most recent 5.x. We can't help you, I
think.
>Identical XFree86 sources compiled nativly on 4.6, 4.7 and 5.0.
>4.6-4.7: no problem
>5.0: logout from X blocks
On Fri, Nov 08, 2002 at 04:22:24PM -0500, Ray Kohler wrote:
> > From [EMAIL PROTECTED] Fri Nov 8 16:15:05 2002
> > Date: Fri, 8 Nov 2002 13:02:58 -0800
> > From: Kris Kennaway <[EMAIL PROTECTED]>
> > To: Ray Kohler <[EMAIL PROTECTED]>
> > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
- Nate Lawson's Original Message -
> On Thu, 7 Nov 2002, David Rhodu wrote:
> > Sidcarter wrote:
> > >Hi Folks,
> > >
> > > I just did a cvsup and installed a kernel. I have been trying this from
> > > the past few days with the same error. I am copying this by hand,
> > > since it crashes
In message: <[EMAIL PROTECTED]>
Steve Kargl <[EMAIL PROTECTED]> writes:
: Here's the fun part. The following 5.0 libraries have the same
: version number as their 4.x counterparts. Try running a 4.x
: app linked against one of these libaries on a 5.0 machine. You
: should also note t
In message: <[EMAIL PROTECTED]>
Steve Kargl <[EMAIL PROTECTED]> writes:
: On Fri, Nov 08, 2002 at 12:17:00PM -0500, Daniel Eischen wrote:
: > On Fri, 8 Nov 2002, M. Warner Losh wrote:
: >
: > >
: > > Yes, but this is too painful. If we were going to do this, the time
: > > for the pa
In message: <[EMAIL PROTECTED]>
Daniel Eischen <[EMAIL PROTECTED]> writes:
: All the ports are going to be rebuilt for the release anyways,
: so this doesn't affect fresh installs, correct? It is only a
: problem when mixing older 4.x and 5.0 libraries/binaries with
: __sF-free libc (i
On Wed, Nov 06, 2002 at 10:27:47PM +0100, Frode Nordahl wrote the words in effect of:
> Hello,
>
> I have been searching mailing lists and my friend Google for information
> about a acpid (like apmd) implementation for FreeBSD, but I have found
> nothing.
>
> Does one exist anywhere, or has anyon
> From [EMAIL PROTECTED] Fri Nov 8 16:15:05 2002
> Date: Fri, 8 Nov 2002 13:02:58 -0800
> From: Kris Kennaway <[EMAIL PROTECTED]>
> To: Ray Kohler <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: Re: perl5.6.1 wrapper
>
> On Fri, Nov 08, 2002 at 06:54:37
On Fri, Nov 08, 2002 at 06:54:37AM -0500, Ray Kohler wrote:
> Then we're back to the problem of there being a complete stale perl in
> the base system after a 4.X->5.X upgrade, but then, I've always thought
> that "clean out the cruft" ought to be a mandatory step in upgrading.
Yes, it's already
Hi
I have opportunity to test sparc64 installer and if time permits, OS
itself for upcoming weekend. The boxes are Netra T1's with two
different ethernet interfaces (2 eri and 4 qfe) and as usual SCSI
disks and ATAPI cdrom. I did short sweep over sparc64 documents
available online and found that a
I've sent mail to phoenix@ , but I thought I'd let this list
know as well. Native phoenix works fine on -current for me,
in spite of the Makefile claims. Install the perl5 port on a
recent -current and phoenix will build and run perfectly. (And
if it doesn't, I'm sure phoenix@ would like to know a
Recompile your kernel with
options PCI_ALLOW_UNSUPPORTED_IO_RANGE
On Fri, 8 Nov 2002, Willem van Engen wrote:
> Hmm, not for me (yet?). Part of dmesg:
>
> VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc03bb322 (122)
> VESA: NVidia
> VESA: NVidia Riva TNT A0
>
> agp0: mem 0xe000
Dear Hackers,
i'm replying to myself, because i think i might have found
some more information on the problem. i would appreciate
if any USB expert would care to comment on this.
please take a look at
http://www.geocities.com/m_evmenkin/usb/24505201.pdf
and look for "USB Dribble" section. Let m
On Fri, 8 Nov 2002, Juan Francisco Rodriguez Hervella wrote:
> I've seen that... so, the only possibility we've got is to cry loudly at
> NVIDIA people and ask them to make a driver for -CURRENT
>
> (I shouldn't install -CURRENT on my home computer :(
I run -CURRENT on my systems (which is whe
* Poul-Henning Kamp <[EMAIL PROTECTED]> [021108 05:29] wrote:
> In message <[EMAIL PROTECTED]>, G
> erald Pfeifer writes:
>
> >Sheesh.
> >
> >PHK, now we have the situation where user programs require #ifdefs
> >to be portable among the BSDs when this was not required before.
> >
> >Please conside
Hi,
> On todays Current i get on Insertion:
>
> pccard0: Allocation failed for cfe 0
> ata2 at port 0x100-0x10f irq 11 function 0 config 1 on pccard0
> ad4: 61MB [490/8/32] at ata2-master BIOSPIO
>
> On todays Current i get on Boot:
>
> pccard0: Allocation failed for cfe 0
> ata2 at port 0x100
I've been dealing for some weeks now with having my system unexpectedly lock
up and be unreachable via Ctrl-Alt-Esc, and tracked it down as far as "the
daily script" or "trying to relabel the entire filesystem" until recently.
Imagine my relief when rwatson suggests to try using the serial c
On Thu, 7 Nov 2002, David Rhodu wrote:
> Sidcarter wrote:
>
> >Hi Folks,
> >
> >I just did a cvsup and installed a kernel. I have been trying this from the past
> >few days with the same error. I am copying this by hand, since it crashes
> >immediately after loading the modules.
> >The error messa
On Sat, Nov 09, 2002 at 04:16:11AM +1000, Andrew Kenneth Milton wrote:
>
> 6. Assume Crash Position.
>
Thanks for your important contribution to a discussion
which is addressing a rather serious problem. Here's the
important part of the "Ghost..." thread.
The following 4.7 libs make reference
+---[ Steve Kargl ]--
|
| I agree with Dan. Let's do it now. My understanding is
| that 5.0 will be an "early adopter" release and production
| systems should run 4.7{8,9,..} until 5.1 is released.
|
| To accomplish the change, I think we need to do:
| 1. Install a comp
Hi,
i had a similar problem as reported by Tomi Vainio on 27.09.2002
with a CF-PCMCIA Adapter and a Sandisk 64MB CF Card with NEWCARD on a
- -current of ~ 20.09.2002:
(This is a Thinkpad X20)
pccard0: Allocation failed for cfe 0
ata2 at port 0x100-0x10f irq 11 function 0 config 1 on pccard0
pcc
On Fri, Nov 08, 2002 at 12:17:00PM -0500, Daniel Eischen wrote:
> On Fri, 8 Nov 2002, M. Warner Losh wrote:
>
> >
> > Yes, but this is too painful. If we were going to do this, the time
> > for the pain was 6-9 months ago, not just before the release.
>
> All the ports are going to be rebuilt f
On Fri, 8 Nov 2002, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Ray Kohler <[EMAIL PROTECTED]> writes:
> : > From [EMAIL PROTECTED] Fri Nov 8 02:45:04 2002
> : > Date: Fri, 08 Nov 2002 00:39:35 -0700 (MST)
> : > To: [EMAIL PROTECTED]
> : > Subject: Re: [PATCH] note the _
> From [EMAIL PROTECTED] Fri Nov 8 11:30:05 2002
> Date: Fri, 08 Nov 2002 09:27:32 -0700 (MST)
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [PATCH] note the __sF change in src/UPDATING
> From: "M. Warner Losh" <[EMAIL PROTECTED]>
>
> In message: <[EMAIL PROTECTED]>
>
Does your kernel module load correctly? I get complaints about an
unsupported memory range [see my previous post for more details]. I'm
building a kernel with 'option PCI_ALLOW_UNSUPPORTED_IO_RANGE' now to
see if that helps.
And about __sF, could an LD_PRELOAD with a __sF 'stub' be a workaround?
-
On Fri, Nov 08, 2002 at 05:43:20PM +0100, Martin Faxer wrote:
> On Fri, Nov 08, 2002 at 05:30:19PM +0100, Martin Faxer wrote:
> i apologize for not reading current@ a bit more :)
> i found the __sF thread now :)
another apology, since this is my 3rd mail in a very short period of
time! however, i
On Fri, Nov 08, 2002 at 05:30:19PM +0100, Martin Faxer wrote:
> [ sorry for not getting the in-reply-to correct, i'm no longer
> subscribed to current@ ]
>
> the nvidia supplied drivers appear to work fine except for libGL* which
> are compiled on an older system and thus give:
> /usr/libexec/ld
[ sorry for not getting the in-reply-to correct, i'm no longer
subscribed to current@ ]
the nvidia supplied drivers appear to work fine except for libGL* which
are compiled on an older system and thus give:
/usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libGL.so.1: Undefined symbol
"__sF"
any way to
In message: <[EMAIL PROTECTED]>
Ray Kohler <[EMAIL PROTECTED]> writes:
: > From [EMAIL PROTECTED] Fri Nov 8 02:45:04 2002
: > Date: Fri, 08 Nov 2002 00:39:35 -0700 (MST)
: > To: [EMAIL PROTECTED]
: > Subject: Re: [PATCH] note the __sF change in src/UPDATING
: > From: "M. Warner Losh" <
Hi,
I just doscovered, that the -Wformat feature does not work for warn() and
err(), but works for printf() und Co. Was the __printf0like feature not
patched into the actual gcc?
harti
--
harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private
[EMAI
On Thu, 31 Oct 2002, Alexander Kabaev wrote:
> On Thu, 31 Oct 2002 12:20:14 -0500 (EST)
> Daniel Eischen <[EMAIL PROTECTED]> wrote:
>
> > I wonder how it works for Solaris (you can see both the non-underscore
> > and single-underscore symbols resolve to the same thing)? Perhaps their
> > stubs i
Hmm, not for me (yet?). Part of dmesg:
VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc03bb322 (122)
VESA: NVidia
VESA: NVidia Riva TNT A0
agp0: mem 0xe000-0xe3ff at
device 0.0 on pci0
agp0: allocating GATT for aperture of size 256M
nvidia0: mem 0xe600-0xe6ff
On Fri, 8 Nov 2002, Horen wrote:
> On Thu, 7 Nov 2002, Terry Lambert wrote:
>
> > Horen wrote:
> > > On FreeBSD 4.6 or 4.7 works, on FreeBSD 5.0 it doesn't work.
> > > Don't you think it is OS related. ?
> >
> > THere are a lot of MS-DOS programs that won't run on FreeBSD;
> > I don't think that
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
Chris Faulhaber writes:
> On Fri, Nov 08, 2002 at 09:38:17AM -0500, 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
> >
> > getfacl seems to work fwiw.
On Fri, Nov 08, 2002 at 11:17:39AM +0800, kai ouyang wrote:
> Hi,
> I am trying to understand the ACL implementation in FreeBSD-Current. I
> have a question about ACL.
> in "acl.h", there are some acl_type_t value macro:
> /*
> * Possible valid values for acl_type_t arguments.
> */
> #define
On Fri, Nov 08, 2002 at 09:38:17AM -0500, 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
>
> getfacl seems to work fwiw.
>
> Same results on UFS and UFS2 filesystems. I
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
getfacl seems to work fwiw.
Same results on UFS and UFS2 filesystems. I have UFS_ACL, also tried
UFS_EXTATTR. -current as of about a week ago.
Any c
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Erik Trulsson wrote:
>
> On Fri, Nov 08, 2002 at 02:11:08PM +0100, Juan Francisco Rodriguez Hervella wrote:
> > Hello,
> >
> > I've just seen the release of FreeBSD-NVIDIA driver for
> > FreeBSD-4.7
> >
> > Will this driver work with -CURRENT ?¿
> >
> > PS: http://www.nvidia.com/view.asp?IO=freebs
On Fri, 2002-11-08 at 23:52, Erik Trulsson wrote:
> The README file found at the above URL claims that:
>
>
> FreeBSD -STABLE versions older than 4.7 and FreeBSD -CURRENT are
> not supported.
>
>
> So I guess the answer is no.
> It is of course possible that it might work anyway even if NVIDIA
In message <[EMAIL PROTECTED]>, G
erald Pfeifer writes:
>Sheesh.
>
>PHK, now we have the situation where user programs require #ifdefs
>to be portable among the BSDs when this was not required before.
>
>Please consider reverting
That has been considered, and I don't think it is a sensible soluti
On Fri, Nov 08, 2002 at 02:11:08PM +0100, Juan Francisco Rodriguez Hervella wrote:
> Hello,
>
> I've just seen the release of FreeBSD-NVIDIA driver for
> FreeBSD-4.7
>
> Will this driver work with -CURRENT ?¿
>
> PS: http://www.nvidia.com/view.asp?IO=freebsd_1.0-3203
The README file found at t
On Fri, 8 Nov 2002, Pierre Beyssac wrote:
> Fine, but if included "as is" in Wine because, it will break
> compatibility with Net/OpenBSD because DBREG_DRX is a FreeBSDism...
> that's why I surrounded my patch with a #ifdef DBREG_DRX (which
> seems cleaner than a #ifdef __FreeBSD__).
Sheesh.
PHK,
Hello,
I've just seen the release of FreeBSD-NVIDIA driver for
FreeBSD-4.7
Will this driver work with -CURRENT ?¿
PS: http://www.nvidia.com/view.asp?IO=freebsd_1.0-3203
--
JFRH.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Fri, Nov 08, 2002 at 02:04:01PM +0100, Pierre Beyssac wrote:
> Fine, but if included "as is" in Wine because, it will break
> compatibility with Net/OpenBSD because DBREG_DRX is a FreeBSDism...
Sorry for the phrasing, remove the spurious "because" to make sense
of it :)
--
Pierre Beyssac
On Fri, Nov 08, 2002 at 12:08:32PM +0100, Gerald Pfeifer wrote:
> Unfortunately (in the sense that both of you duplicated effort),
> Alfred independently came up with a similiar patch which went in as
> $PORTSDIR/emulators/wine/files/patch-context_i386
> and which I already fed upstream to the Wi
Upgrades from RELENG_4 and pre-"static __sF" systems should be
working again.
On Fri, Nov 08, 2002 at 04:47:51AM -0800, Ruslan Ermilov wrote:
> ru 2002/11/08 04:47:51 PST
>
> Modified files:
> secure/lib/libcrypto Makefile.inc
> Log:
> DON'T EVER PUT THIS BACK!
>
> Pointy
Horen <[EMAIL PROTECTED]> writes:
> Posted a week ago the question, didn't get any reaction.
>
> Everything with current from last night works fine but killing
> X or logging out ends in a black screen. No way to activate the
> display without reboot. Remote login is fine. Typing blind works
> to
> From [EMAIL PROTECTED] Fri Nov 8 04:15:04 2002
> To: Kris Kennaway <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: perl5.6.1 wrapper
> Date: Fri, 08 Nov 2002 08:58:44 +
> From: Mark Murray <[EMAIL PROTECTED]>
>
> IMVHO, the perl wrapper should be removed altogether, and the
> per
Doug Rabson wrote:
> > It _would_ be a good idea to document any internal library
> > symbols used by macros. Removing such symbols is a
> > good way to break existing compiled applications.
> >
> > Library design involves a lot of tradeoffs.
>
> In the windows world, all this is handled by havin
> From [EMAIL PROTECTED] Fri Nov 8 02:45:04 2002
> Date: Fri, 08 Nov 2002 00:39:35 -0700 (MST)
> To: [EMAIL PROTECTED]
> Subject: Re: [PATCH] note the __sF change in src/UPDATING
> From: "M. Warner Losh" <[EMAIL PROTECTED]>
>
> In message: <[EMAIL PROTECTED]>
> Ray Kohler <[EMAIL PROTE
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Horen wrote:
> On FreeBSD 4.6 or 4.7 works, on FreeBSD 5.0 it doesn't work.
> Don't you think it is OS related. ?
>
> I even installed Linux RedHat 8.0 ( gcc 3.2x ) code. It works.
> Only on FreeBSD 5,0 , it doesn't work.
Install X from FreeBSD 4.6 or 4.7 on FreeBSD 5.0... plain enough?
-- Terry
On Fri, 8 Nov 2002, Pierre Beyssac wrote:
>> As for source compatibility, just use the DBREG_DRX macro, which exists
>> in both -STABLE and -CURRENT (it was merged into -STABLE two years ago).
> It's too bad source compatibility hasn't been preserved.
Indeed.
> Argument d is not properly parenthe
On Thu, Nov 07, 2002 at 05:02:14PM -0800, Terry Lambert wrote:
> Horen wrote:
> > > You stated "Typing blind starts X again".
> > >
> > > Can you tell us what you mean by this?
> > >
> > > o It restarts X, as if you typed "startx"
> >
> > Exactly that.
>
> The problem is clearly in the X11 co
On Wed, Oct 30, 2002 at 05:29:39PM +0100, Dag-Erling Smorgrav wrote:
> That revision doesn't change the structure, just how it is defined, so
> binary compatibility is not an issue. As for source compatibility,
> just use the DBREG_DRX macro, which exists in both -STABLE and
> -CURRENT (it was mer
Hi all,
for months now I've been having a reproducible hang under load
(make -j4 buildworld on a uniprocessor with plenty of RAM). I transcribed
some info which might be useful to debug it; it seems to me this is a
deadlock (am I right?). I'll leave the laptop in ddb so I can provide
more info.
T
On Thursday 07 November 2002 9:42 pm, Tim Kientzle wrote:
> Terry Lambert asked:
> > Any chance we could get rid of all externally visable symbols that
> > are not defined as being there by some standard, and not just __sF,
> > since we are breaking the FORTRAN compiler and other third party
> > co
1 - 100 of 104 matches
Mail list logo
