Francis Jordan wrote:
>
> Can anyone please give me some clues as to how to build X with thread support
> enabled. I think the right way to do it is to add the relevant options to
> config/cf/FreeBSD.cf, something like
>
> #define HasPosixThreads YES
> #define ThreadedX YE
Francis Jordan wrote:
>
> Can anyone please give me some clues as to how to build X with thread support
> enabled. I think the right way to do it is to add the relevant options to
> config/cf/FreeBSD.cf, something like
>
> #define HasPosixThreads YES
> #define ThreadedX YES
Jesus Monroy wrote:
>
> Ville-Pertti Keinonen <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] (Mike O'Dell) writes:
> > > we published the best Unix SMP paper I've ever seen in Computing
> > > Systems - from the Amdahl guys who did an SMP version of the kernel
> > > by very clever hacks on SPLx(
Jesus Monroy wrote:
>
> Ville-Pertti Keinonen wrote:
> > m...@servo.ccr.org (Mike O'Dell) writes:
> > > we published the best Unix SMP paper I've ever seen in Computing
> > > Systems - from the Amdahl guys who did an SMP version of the kernel
> > > by very clever hacks on SPLx() macros to make th
This is how mmap() is supposed to work. mmap() may return an area larger
then the one you specified due to page-alignment considerations. It is
not legal for you to write in an area which is outside the range you
specified, but there is no way for the machine to enforce this except
This is how mmap() is supposed to work. mmap() may return an area larger
then the one you specified due to page-alignment considerations. It is
not legal for you to write in an area which is outside the range you
specified, but there is no way for the machine to enforce this except
On Friday, 25 June 1999 at 23:53:50 -0700, Jordan K. Hubbard wrote:
>> I agree with the approach. But why write a simplistic volume manager
>> when we already have vinum?
>
> vinum is far from simplistic, but I suppose it might also do. :)
>
> Still, it would someday be nice if you could use vinu
On Friday, 25 June 1999 at 23:53:50 -0700, Jordan K. Hubbard wrote:
>> I agree with the approach. But why write a simplistic volume manager
>> when we already have vinum?
>
> vinum is far from simplistic, but I suppose it might also do. :)
>
> Still, it would someday be nice if you could use vinum
>From the source code of mmap(), it seems to me that FreeBSD can not handle
mmap() when the specified file range [offset, offset + length] does not
align with memory page boundary. The mmap() automatically enlarges the
mapped area on BOTH ends of the given range to a page boundary. In the
follo
In message <[EMAIL PROTECTED]> Matthew Hunt writes:
: Security holes are rarely in the kernel, and you can easily keep your
: applications up-to-date without rebooting.
And the ones that re in the kernel tend to be DoS type problems that
force a reboot anyway :-(
Warner
To Unsubscribe: send ma
In message <19990624114734.a96...@wopr.caltech.edu> Matthew Hunt writes:
: Security holes are rarely in the kernel, and you can easily keep your
: applications up-to-date without rebooting.
And the ones that re in the kernel tend to be DoS type problems that
force a reboot anyway :-(
Warner
To
On Sun, Jun 27, 1999 at 09:33:45AM +0930, Greg Lehey wrote:
> On Sunday, 27 June 1999 at 0:35:54 +0200, Ollivier Robert wrote:
> > According to Bernd Walter:
> >> I wrote one.
> >> It is place on ftp://ftp.cosmo-project.de/pub/growfs
> >> My tool will grow a UFS filesystem to the current size of
On Sun, Jun 27, 1999 at 09:33:45AM +0930, Greg Lehey wrote:
> On Sunday, 27 June 1999 at 0:35:54 +0200, Ollivier Robert wrote:
> > According to Bernd Walter:
> >> I wrote one.
> >> It is place on ftp://ftp.cosmo-project.de/pub/growfs
> >> My tool will grow a UFS filesystem to the current size of t
On Sun, Jun 27, 1999 at 12:35:54AM +0200, Ollivier Robert wrote:
>
> Another datapoint ot consider, it seems that Linux (at least the derivative
> version maintained by Alan Cox -- the other one :) ) has now grown an LVM
> system (probably à la HP or AIX). That's what I've been told yesterday dur
On Sun, Jun 27, 1999 at 12:35:54AM +0200, Ollivier Robert wrote:
>
> Another datapoint ot consider, it seems that Linux (at least the derivative
> version maintained by Alan Cox -- the other one :) ) has now grown an LVM
> system (probably à la HP or AIX). That's what I've been told yesterday duri
On Sunday, 27 June 1999 at 0:35:54 +0200, Ollivier Robert wrote:
> According to Bernd Walter:
>> I wrote one.
>> It is place on ftp://ftp.cosmo-project.de/pub/growfs
>> My tool will grow a UFS filesystem to the current size of the partition.
>
> Another datapoint ot consider, it seems that Linux
On Sunday, 27 June 1999 at 0:35:54 +0200, Ollivier Robert wrote:
> According to Bernd Walter:
>> I wrote one.
>> It is place on ftp://ftp.cosmo-project.de/pub/growfs
>> My tool will grow a UFS filesystem to the current size of the partition.
>
> Another datapoint ot consider, it seems that Linux (
On Saturday, 26 June 1999 at 12:03:59 -0500, Constantine Shkolny wrote:
> On Saturday, June 26, 1999 8:08 AM, Nick Hibma [SMTP:[EMAIL PROTECTED]]
> wrote:
>>> Programmers need documentation too.
>>
>> And they are going to scream like mad if there isn't any. But in the end
>> they start reading th
On Saturday, 26 June 1999 at 12:03:59 -0500, Constantine Shkolny wrote:
> On Saturday, June 26, 1999 8:08 AM, Nick Hibma [SMTP:hi...@skylink.it]
> wrote:
>>> Programmers need documentation too.
>>
>> And they are going to scream like mad if there isn't any. But in the end
>> they start reading the
According to Bernd Walter:
> I wrote one.
> It is place on ftp://ftp.cosmo-project.de/pub/growfs
> My tool will grow a UFS filesystem to the current size of the partition.
Another datapoint ot consider, it seems that Linux (at least the derivative
version maintained by Alan Cox -- the other one :
According to Bernd Walter:
> I wrote one.
> It is place on ftp://ftp.cosmo-project.de/pub/growfs
> My tool will grow a UFS filesystem to the current size of the partition.
Another datapoint ot consider, it seems that Linux (at least the derivative
version maintained by Alan Cox -- the other one :)
On Fri, Jun 25, 1999 at 02:15:01PM -0700, Matthew Dillon wrote:
> :anybody done any work on a utility for growing ufs filesystems?
> :
> :aaron
>
> It has been brought up a couple of times but nobody has tried
> to do actually it. Personally, I think it would be a doable
> project if
On Fri, Jun 25, 1999 at 02:15:01PM -0700, Matthew Dillon wrote:
> :anybody done any work on a utility for growing ufs filesystems?
> :
> :aaron
>
> It has been brought up a couple of times but nobody has tried
> to do actually it. Personally, I think it would be a doable
> project if
On Fri, Jun 25, 1999 at 02:00:41PM -0700, Aaron Smith wrote:
> anybody done any work on a utility for growing ufs filesystems?
>
I wrote one.
It is place on ftp://ftp.cosmo-project.de/pub/growfs
My tool will grow a UFS filesystem to the current size of the partition.
There is still one big proble
On Fri, Jun 25, 1999 at 02:00:41PM -0700, Aaron Smith wrote:
> anybody done any work on a utility for growing ufs filesystems?
>
I wrote one.
It is place on ftp://ftp.cosmo-project.de/pub/growfs
My tool will grow a UFS filesystem to the current size of the partition.
There is still one big problem
As Matthew Jacob wrote ...
>
>
> On Sat, 26 Jun 1999, Wilko Bulte wrote:
>
> > As Matthew Jacob wrote ...
> > >
> > > Yes, you want the WWN to stay constant. That doesn't mean it should
> > > necessarily be the same physical box. Nor does it mean it should be a
> > > system that comes with a W
As Matthew Jacob wrote ...
>
>
> On Sat, 26 Jun 1999, Wilko Bulte wrote:
>
> > As Matthew Jacob wrote ...
> > >
> > > Yes, you want the WWN to stay constant. That doesn't mean it should
> > > necessarily be the same physical box. Nor does it mean it should be a
> > > system that comes with a WW
On Saturday, June 26, 1999 8:08 AM, Nick Hibma [SMTP:[EMAIL PROTECTED]]
wrote:
> > Programmers need documentation too.
>
> And they are going to scream like mad if there isn't any. But in the end
> they start reading the code anyway, even if there is docu, because they
> don't trust anything but
On Saturday, June 26, 1999 8:08 AM, Nick Hibma [SMTP:hi...@skylink.it]
wrote:
> > Programmers need documentation too.
>
> And they are going to scream like mad if there isn't any. But in the end
> they start reading the code anyway, even if there is docu, because they
> don't trust anything but th
On Sat, 26 Jun 1999, Wilko Bulte wrote:
> As Matthew Jacob wrote ...
> >
> > Yes, you want the WWN to stay constant. That doesn't mean it should
> > necessarily be the same physical box. Nor does it mean it should be a
> > system that comes with a WWN assigned to by the manufacturer.
>
> Manu
On Sat, 26 Jun 1999, Wilko Bulte wrote:
> As Matthew Jacob wrote ...
> >
> > Yes, you want the WWN to stay constant. That doesn't mean it should
> > necessarily be the same physical box. Nor does it mean it should be a
> > system that comes with a WWN assigned to by the manufacturer.
>
> Manuf
As Matthew Jacob wrote ...
>
> Yes, you want the WWN to stay constant. That doesn't mean it should
> necessarily be the same physical box. Nor does it mean it should be a
> system that comes with a WWN assigned to by the manufacturer.
Manufacturers have to register and 'get' a unique range they
I left my system to do a make release only to find that it had
rebooted while doing the make:
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
(no debugging symbols found)...
IdlePTD 3141632
initial pcb at 28e4f4
pani
I left my system to do a make release only to find that it had
rebooted while doing the make:
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
(no debugging symbols found)...
IdlePTD 3141632
initial pcb at 28e4f4
panic
As Matthew Jacob wrote ...
>
> Yes, you want the WWN to stay constant. That doesn't mean it should
> necessarily be the same physical box. Nor does it mean it should be a
> system that comes with a WWN assigned to by the manufacturer.
Manufacturers have to register and 'get' a unique range they c
On Sat, Jun 26, 1999 at 06:55:53AM +0200, Sheldon Hearn wrote:
>
> I don't think the core team would care enough about something this silly
> to bother making a decision, so I'm just watching what people have to
> say. I'm leaning toward leaving the "nowrap" feature out.
FWIW, I think that leavi
On Sat, Jun 26, 1999 at 06:55:53AM +0200, Sheldon Hearn wrote:
>
> I don't think the core team would care enough about something this silly
> to bother making a decision, so I'm just watching what people have to
> say. I'm leaning toward leaving the "nowrap" feature out.
FWIW, I think that leavin
On Sat, Jun 26, 1999 at 03:08:10PM +0200, Nick Hibma wrote:
>
> And they are going to scream like mad if there isn't any. But in the end
> they start reading the code anyway, even if there is docu, because they
> don't trust anything but their own eyes and brain.
ports system == really really l
On Sat, Jun 26, 1999 at 03:08:10PM +0200, Nick Hibma wrote:
>
> And they are going to scream like mad if there isn't any. But in the end
> they start reading the code anyway, even if there is docu, because they
> don't trust anything but their own eyes and brain.
ports system == really really la
> On Wed, Jun 23, 1999 at 07:20:56PM -0400, Chuck Robey wrote:
> > But one thing I like is, although FreeBSD *does* try to appease user
> > demands, it's controlled by programmers, not users, so if something is
> > a technically extemely evil idea, no matter how the masses yell for it,
> > it will
> On Wed, Jun 23, 1999 at 07:20:56PM -0400, Chuck Robey wrote:
> > But one thing I like is, although FreeBSD *does* try to appease user
> > demands, it's controlled by programmers, not users, so if something is
> > a technically extemely evil idea, no matter how the masses yell for it,
> > it will
Hi Chuck,
On Wed, Jun 23, 1999 at 07:20:56PM -0400, Chuck Robey wrote:
> But one thing I like is, although FreeBSD *does* try to appease user
> demands, it's controlled by programmers, not users, so if something is
> a technically extemely evil idea, no matter how the masses yell for it,
> it wil
Hi Chuck,
On Wed, Jun 23, 1999 at 07:20:56PM -0400, Chuck Robey wrote:
> But one thing I like is, although FreeBSD *does* try to appease user
> demands, it's controlled by programmers, not users, so if something is
> a technically extemely evil idea, no matter how the masses yell for it,
> it will
On Sat, 26 Jun 1999 [EMAIL PROTECTED] wrote:
> Hi,
>
> I believe someone working on NEWBUS-ifying ISA-PnP.
> How will they implement it?
> I think current framework is like this.
>++ ++
> ...|ISA DEV | |ISA-hint|<-This device provides
>++ +-
On Sat, 26 Jun 1999 takaw...@shidahara1.planet.sci.kobe-u.ac.jp wrote:
> Hi,
>
> I believe someone working on NEWBUS-ifying ISA-PnP.
> How will they implement it?
> I think current framework is like this.
>++ ++
> ...|ISA DEV | |ISA-hint|<-This device provides
>
On 26-Jun-99 Jesus Monroy wrote:
> The part I'm lost on is "can change things from under it".
> From under what? I assume the statement means "it" as being
> the code or driver. So the question begs, what things can
> change?
The assumption that changes is that your code ass
On 26-Jun-99 Jesus Monroy wrote:
> The part I'm lost on is "can change things from under it".
> From under what? I assume the statement means "it" as being
> the code or driver. So the question begs, what things can
> change?
The assumption that changes is that your code assu
Yes. NIS is braindead.
The amount of traffic is not that large. The problem you will see is
that it takes longer for a prompt to return due to NIS when the network
is heavily loaded and latencies rise.
When you log in to a Sun box (most often NIS-ified) for example, you
will see that it takes
Yes. NIS is braindead.
The amount of traffic is not that large. The problem you will see is
that it takes longer for a prompt to return due to NIS when the network
is heavily loaded and latencies rise.
When you log in to a Sun box (most often NIS-ified) for example, you
will see that it takes a
"Daniel J. O'Connor" <[EMAIL PROTECTED]> wrote:
> On 26-Jun-99 Jesus Monroy wrote:
> > > An approach like that can't possibly be sufficient if code has been
> > > written with the assumption that only interrupt-like events or
> > > blocking calls can change things from under it. There is quite
>
"Daniel J. O'Connor" wrote:
> On 26-Jun-99 Jesus Monroy wrote:
> > > An approach like that can't possibly be sufficient if code has been
> > > written with the assumption that only interrupt-like events or
> > > blocking calls can change things from under it. There is quite
> > > a bit of code i
On 26-Jun-99 Jesus Monroy wrote:
> > An approach like that can't possibly be sufficient if code has been
> > written with the assumption that only interrupt-like events or
> > blocking calls can change things from under it. There is quite a bit
> > of code in FreeBSD that relies on this.
> C
On 26-Jun-99 Jesus Monroy wrote:
> > An approach like that can't possibly be sufficient if code has been
> > written with the assumption that only interrupt-like events or
> > blocking calls can change things from under it. There is quite a bit
> > of code in FreeBSD that relies on this.
> Ca
56 matches
Mail list logo
