On Sun, 9 Mar 2008 17:41:15 -0700 (PDT) Mikko Työläjärvi <[EMAIL PROTECTED]>
wrote:
> On Sun, 9 Mar 2008, Mike Meyer wrote:
>
> [...]
>
> > So there are at *least* three things that could be considered broken,
> > in that changing them would fix the problem I encountered.
> >
> > 1) Our /bin/sh
On Sun, 9 Mar 2008, Mike Meyer wrote:
[...]
So there are at *least* three things that could be considered broken,
in that changing them would fix the problem I encountered.
1) Our /bin/sh isn't classified as Definitely usable.
2) zsh is Not usable.
3) zsh is classified as Maybe usable.
#1 cou
On Sunday, 9 March 2008 at 15:27:12 -0400, Mike Meyer wrote:
> I've stumbled on to an obscure problem with autoconf 2.61, and I'm not
> sure quite what to do with it. I've already sent mail to the autoconf
> folks, but I'd like to understand what's going on.
>
> The problem is that, on a FreeBSD s
On Sun, Mar 09, 2008 at 07:40:50PM -0400, Mike Meyer wrote:
> 1) Our /bin/sh isn't classified as Definitely usable.
> 2) zsh is Not usable.
> 3) zsh is classified as Maybe usable.
The third is definitely true.
Joerg
___
freebsd-hackers@freebsd.org maili
On Sun, 09 Mar 2008 18:13:59 -0400 Chuck Robey <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Mike Meyer wrote:
> > I've stumbled on to an obscure problem with autoconf 2.61, and I'm not
> > sure quite what to do with it. I've already sent mail to the autoconf
>
On Sun, Mar 9, 2008 at 2:24 PM, Jonathan Chen <[EMAIL PROTECTED]> wrote:
> I've been battling with a bug related to mlock and COW pages. Since I'm
> basically clueless when it comes to the VM subsystem, I was hoping someone
> with more clue can look at my fix and let me know if I'm doing the rig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Meyer wrote:
> I've stumbled on to an obscure problem with autoconf 2.61, and I'm not
> sure quite what to do with it. I've already sent mail to the autoconf
> folks, but I'd like to understand what's going on.
>
> The problem is that, on a FreeB
I've been battling with a bug related to mlock and COW pages. Since I'm
basically clueless when it comes to the VM subsystem, I was hoping someone
with more clue can look at my fix and let me know if I'm doing the right
thing here.
The problem: User programs will crash (SEGV/BUS) if COW pages
On Sun, 9 Mar 2008 14:41:30 + Frank Mitchell wrote:
> MEMORY LOCKING:
>
> Recompiling my root-privileged program, I get a System Call failure
> for:
>
> mlockall(MCL_CURRENT);
>
> errno says: "Resource temporarily unavailable"
how much memory is installed?
> But mlock(); works.
... and how
I've stumbled on to an obscure problem with autoconf 2.61, and I'm not
sure quite what to do with it. I've already sent mail to the autoconf
folks, but I'd like to understand what's going on.
The problem is that, on a FreeBSD system with only /bin/sh and the
ports zsh as installed shells, if you h
Julian Elischer wrote:
Hartmut Brandt wrote:
Robert Watson wrote:
On Sat, 8 Mar 2008, Hans Petter Selasky wrote:
I'm planning to create a new socket type in FreeBSD called AF_Q921,
which is to be used for ISDN telephony. Where do I find
documentation on how to implement a new socket in the
Bernd Walter wrote:
On Fri, Mar 07, 2008 at 11:08:50AM -0500, Daniel Eischen wrote:
On Thu, 6 Mar 2008, Marko, Shaun wrote:
I'm working on FreeBSD 6.2 and I'm wondering if anybody can help with an
issue I've found using fork and threads. The attached program
demonstrates the problem. In short,
Hans Petter Selasky wrote:
On Saturday 08 March 2008, Robert Watson wrote:
On Sat, 8 Mar 2008, Hans Petter Selasky wrote:
For example, do you
anticipate using or even needing the routing facilities, and how might you
map ISDN telephony parts into the normal network stack infrastructure of
add
MOUNTING EXT2FS:
I dual-boot with OpenSUSE, sharing data on an Ext2 Partition. The machine is
an AMD Sempron with SATA Hard Disk. After installing FreeBSD 64-bit for AMD,
I suddenly got problems with mount_ext2fs. Thus:
"mount_ext2fs /dev/ad4s2 /mnt" , with various options can yield:
"Operatio
On Sun, 9 Mar 2008, Bernd Walter wrote:
On Fri, Mar 07, 2008 at 11:08:50AM -0500, Daniel Eischen wrote:
On Thu, 6 Mar 2008, Marko, Shaun wrote:
I'm working on FreeBSD 6.2 and I'm wondering if anybody can help with an
issue I've found using fork and threads. The attached program
demonstrates t
On Fri, Mar 07, 2008 at 11:08:50AM -0500, Daniel Eischen wrote:
> On Thu, 6 Mar 2008, Marko, Shaun wrote:
>
> >I'm working on FreeBSD 6.2 and I'm wondering if anybody can help with an
> >issue I've found using fork and threads. The attached program
> >demonstrates the problem. In short, if a proce
On Sun, 9 Mar 2008, Hans Petter Selasky wrote:
On Saturday 08 March 2008, Robert Watson wrote:
On Sat, 8 Mar 2008, Hans Petter Selasky wrote:
For example, do you
anticipate using or even needing the routing facilities, and how might you
map ISDN telephony parts into the normal network stack
Andriy Gapon wrote:
on 20/02/2008 20:33 Andriy Gapon said the following:
on 19/02/2008 23:42 Andriy Gapon said the following:
The last result most probably means that RTC IRQ was not the interrupt
to wake CPU from sleeping state.
The first possibility that comes to mind is that on this particul
On Sun, Mar 09, 2008 at 10:17:14AM +0100, Hans Petter Selasky wrote:
> On Saturday 08 March 2008, Max Laier wrote:
> > Am Sa, 8.03.2008, 11:33, schrieb Hans Petter Selasky:
> > > I'm planning to create a new socket type in FreeBSD called AF_Q921, which
> > > is
> > > to be used for ISDN telephony.
On Saturday 08 March 2008, Robert Watson wrote:
> On Sat, 8 Mar 2008, Hans Petter Selasky wrote:
> For example, do you
> anticipate using or even needing the routing facilities, and how might you
> map ISDN telephony parts into the normal network stack infrastructure of
> addresses, routing, inter
On Saturday 08 March 2008, Max Laier wrote:
> Am Sa, 8.03.2008, 11:33, schrieb Hans Petter Selasky:
> > I'm planning to create a new socket type in FreeBSD called AF_Q921, which
> > is
> > to be used for ISDN telephony. Where do I find documentation on how to
>
> interesting ... can you share more
21 matches
Mail list logo
