Kris Kennaway wrote:
packages are usually built from the ports tree, but not always, and
users may use packages without a ports tree present on the local system.
short of doing pkg_delete -af then pkg_add /some/dir
are there any ports-mgmt/* tools for upgrades that don't need the ports
tree pre
Philip M. Gollucci wrote:
Florent Thoumie wrote:
This adds support for /etc/pkg.conf configuration file.
Also, this adds support for naive multi-site package fetching.
Any comment welcome (and appreciated).
Patch is here:
http://people.freebsd.org/~flz/local/ports/pkg-install-config.diff
Tar
Florent Thoumie wrote:
This adds support for /etc/pkg.conf configuration file.
Also, this adds support for naive multi-site package fetching.
Any comment welcome (and appreciated).
Patch is here:
http://people.freebsd.org/~flz/local/ports/pkg-install-config.diff
Tarball is here:
http://people.
Your are right PAE is for i386, i mean try running i386 freebsd with
PAE enabled rather than amd64. PAE will let you access 64GB which is
far than you got.
On Sat, May 31, 2008 at 7:01 PM, Tz-Huan Huang <[EMAIL PROTECTED]> wrote:
> On Sun, Jun 1, 2008 at 2:54 AM, Maslan <[EMAIL PROTECTED]> wrote:
Hi,
is PAE enabled in your kernel config ?
Thanks
On Sat, May 31, 2008 at 5:52 AM, Tz-Huan Huang <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Our nfs server is running 7-stable/amd64 with 8G ram, the size of zfs
> pool is 12T. We have set vm.kmem_size and vm.kmem_size_max to
> 1.5G, but the kernel still
On Sun, Jun 1, 2008 at 2:54 AM, Maslan <[EMAIL PROTECTED]> wrote:
> Hi,
>
> is PAE enabled in your kernel config ?
Our server runs on amd64. I might be wrong, but I think PAE is for i386
only, right?
Thanks,
Tz-Huan
___
freebsd-hackers@freebsd.org maili
On Sat, May 31, 2008 at 12:49:53PM -0400, John Baldwin wrote:
> On Saturday 31 May 2008 01:52:56 am Tz-Huan Huang wrote:
> > Hi,
> >
> > Our nfs server is running 7-stable/amd64 with 8G ram, the size of zfs
> > pool is 12T. We have set vm.kmem_size and vm.kmem_size_max to
> > 1.5G, but the kernel s
John Baldwin wrote:
>> Physical Disks:
>> Port Drive Model Serial # Size Type/Status(Vol ID)
>> 0WDC WD5000ABYS-0 WD-WCAPW5637184 465.8GB Member Disk(0)
>> 1ST3500320NS 5QM09E6F 465.8GB Error Occurred(0)
>> 2WDC WD5000ABYS-0 WD-WCAPW5548822 465.8GB
On Sat, May 31, 2008 at 12:49:53PM -0400, John Baldwin wrote:
> On Saturday 31 May 2008 01:52:56 am Tz-Huan Huang wrote:
> > Hi,
> >
> > Our nfs server is running 7-stable/amd64 with 8G ram, the size of zfs
> > pool is 12T. We have set vm.kmem_size and vm.kmem_size_max to
> > 1.5G, but the kernel s
On Sun, Jun 1, 2008 at 12:49 AM, John Baldwin <[EMAIL PROTECTED]> wrote:
> On Saturday 31 May 2008 01:52:56 am Tz-Huan Huang wrote:
>> Hi,
>>
>> Our nfs server is running 7-stable/amd64 with 8G ram, the size of zfs
>> pool is 12T. We have set vm.kmem_size and vm.kmem_size_max to
>> 1.5G, but the ke
On Saturday 31 May 2008 01:52:56 am Tz-Huan Huang wrote:
> Hi,
>
> Our nfs server is running 7-stable/amd64 with 8G ram, the size of zfs
> pool is 12T. We have set vm.kmem_size and vm.kmem_size_max to
> 1.5G, but the kernel still panics by "kmem_map too small" often.
> According to [1], the limitat
In message: <[EMAIL PROTECTED]>
Andriy Gapon <[EMAIL PROTECTED]> writes:
:
: I've just came back from a good 2 week vacation and catching up on news.
: In release notes for OpenBSD 4.3 I see the following:
: http://openbsd.org/43.html
: Filesystems on USB devices are automatically dism
Hello,
As a followup to my previous patch on csup, I've tried to do some fixes to
RCS-files. However, instead of doing major workarounds in csup to handle
files which does not behave correctly to RCS, I implemented MD5 check of RCS
content. This means that the MD5 sum from cvsupd is checked agains
On Thu, May 29, 2008 at 12:04:41AM -0400, John Baldwin wrote:
> On Sunday 25 May 2008 11:45:37 am Stefan Farfeleder wrote:
> > On Sun, May 25, 2008 at 09:06:47AM -0600, John E Hein wrote:
> > > FWIW, it seems bash and sh report line number differently.
> > >
> > > # grep -n ^ ~/tmp/ln
> > > 1:#!/bi
Tz-Huan Huang wrote:
> Is there any standard way to modify the layout of KVM? For example, we
> may want to set KVM to 6G and leave the 2G for user space usage.
> [2] http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084325.html
Isn't this a limitation of gcc and the kernel/userland
15 matches
Mail list logo