On 2024/10/17 23:07, Philip Guenther wrote:
> On Thu, Oct 17, 2024 at 2:16 PM Stuart Henderson
> wrote:
> > On 2024-10-17, Christian Schulte wrote:
> > >
> > > I just don't get the point for trying to support 32bit hardware on a
> > > 64bit system. If the hardware does not support 64bit but is li
On Thu, Oct 17, 2024 at 2:16 PM Stuart Henderson
wrote:
> On 2024-10-17, Christian Schulte wrote:
> >
> > I just don't get the point for trying to support 32bit hardware on a
> > 64bit system. If the hardware does not support 64bit but is limited to
> > 32bit, use i386. If the hardware supports 6
On 2024-10-17, Christian Schulte wrote:
>>
>
> I just don't get the point for trying to support 32bit hardware on a
> 64bit system. If the hardware does not support 64bit but is limited to
> 32bit, use i386. If the hardware supports 64bit, just don't limit it to
> 32bit. Does not make sense to me
On 10/17/24 18:10, Christian Schulte wrote:
> On 10/17/24 17:03, Stuart Henderson wrote:
>> On 2024-10-17, Christian Schulte wrote:
>>> On 10/17/24 09:40, Stuart Henderson wrote:
On 2024-10-16, Christian Schulte wrote:
>
> No. That's what seems to went wrong when going from i386 to a
On 10/17/24 17:03, Stuart Henderson wrote:
> On 2024-10-17, Christian Schulte wrote:
>> On 10/17/24 09:40, Stuart Henderson wrote:
>>> On 2024-10-16, Christian Schulte wrote:
No. That's what seems to went wrong when going from i386 to amd64.
The 3GB hard limit of i386 was in the ra
On 2024-10-17, Christian Schulte wrote:
> On 10/17/24 09:40, Stuart Henderson wrote:
>> On 2024-10-16, Christian Schulte wrote:
>>>
>>> No. That's what seems to went wrong when going from i386 to amd64.
>>> The 3GB hard limit of i386 was in the range of available physical
>>> memory (4GB) without
On 10/17/24 09:40, Stuart Henderson wrote:
> On 2024-10-16, Christian Schulte wrote:
>>
>> No. That's what seems to went wrong when going from i386 to amd64.
>> The 3GB hard limit of i386 was in the range of available physical
>> memory (4GB) without swap. The 128GB on amd64 do not. Changing this
On 2024-10-16, Christian Schulte wrote:
>
> No. That's what seems to went wrong when going from i386 to amd64. The
> 3GB hard limit of i386 was in the range of available physical memory
> (4GB) without swap. The 128GB on amd64 do not. Changing this to what
> "memory" reads, makes no difference, th
On 10/16/24 22:37, Thomas Frohwein wrote:
> On Tue, 15 Oct 2024 16:08:03 +0200
> Christian Schulte wrote:
>
>> On 10/15/24 15:09, Claudio Jeker wrote:
>>> On Tue, Oct 15, 2024 at 02:35:03PM +0200, Christian Schulte wrote:
On 10/15/24 12:45, Claudio Jeker wrote:
> On Tue, Oct 15, 2024
On 10/15/24 20:29, Kirill A. Korinsky wrote:
> On Tue, 15 Oct 2024 12:28:20 +0200,
> Christian Schulte wrote:
>>
>> On 10/15/24 12:09, Stuart Henderson wrote:
>>> On 2024-10-15, Zé Loff wrote:
On Tue, Oct 15, 2024 at 10:14:42AM +0200, Christian Schulte wrote:
> ulimit -d `ulimit -aH | gr
On 10/15/24 18:38, Stefan Sperling wrote:
> On Tue, Oct 15, 2024 at 04:08:03PM +0200, Christian Schulte wrote:
>> On 10/15/24 15:09, Claudio Jeker wrote:
>>> If the problem was trivial it would have been fixed already.
>>
>> I am not around here for working on things a chimpanzee could be trained
>
On Tue, 15 Oct 2024 16:08:03 +0200
Christian Schulte wrote:
> On 10/15/24 15:09, Claudio Jeker wrote:
> > On Tue, Oct 15, 2024 at 02:35:03PM +0200, Christian Schulte wrote:
> >> On 10/15/24 12:45, Claudio Jeker wrote:
> >>> On Tue, Oct 15, 2024 at 12:28:20PM +0200, Christian Schulte
> >>> wro
On 2024-10-15, Christian Schulte wrote:
> On 10/15/24 12:09, Stuart Henderson wrote:
>> On 2024-10-15, Zé Loff wrote:
>>> On Tue, Oct 15, 2024 at 10:14:42AM +0200, Christian Schulte wrote:
ulimit -d `ulimit -aH | grep data | awk '{print $2}'`
ulimit -n `ulimit -aH | grep nofiles | awk '
On Tue, 15 Oct 2024 12:28:20 +0200,
Christian Schulte wrote:
>
> On 10/15/24 12:09, Stuart Henderson wrote:
> > On 2024-10-15, Zé Loff wrote:
> >> On Tue, Oct 15, 2024 at 10:14:42AM +0200, Christian Schulte wrote:
> >>> ulimit -d `ulimit -aH | grep data | awk '{print $2}'`
> >>> ulimit -n `ulimi
On Tue, Oct 15, 2024 at 04:08:03PM +0200, Christian Schulte wrote:
> On 10/15/24 15:09, Claudio Jeker wrote:
> > If the problem was trivial it would have been fixed already.
>
> I am not around here for working on things a chimpanzee could be trained
> to do.
Ouch, you stepped on a big pile of po
On Tue, Oct 15, 2024 at 02:35:03PM +0200, Christian Schulte wrote:
> On 10/15/24 12:45, Claudio Jeker wrote:
> > On Tue, Oct 15, 2024 at 12:28:20PM +0200, Christian Schulte wrote:
> >> On 10/15/24 12:09, Stuart Henderson wrote:
> >>> On 2024-10-15, Zé Loff wrote:
> On Tue, Oct 15, 2024 at 10:
On 10/15/24 15:09, Claudio Jeker wrote:
> On Tue, Oct 15, 2024 at 02:35:03PM +0200, Christian Schulte wrote:
>> On 10/15/24 12:45, Claudio Jeker wrote:
>>> On Tue, Oct 15, 2024 at 12:28:20PM +0200, Christian Schulte wrote:
On 10/15/24 12:09, Stuart Henderson wrote:
> On 2024-10-15, Zé Loff
On Tue, Oct 15, 2024 at 02:35:03PM +0200, Christian Schulte wrote:
> On 10/15/24 12:45, Claudio Jeker wrote:
> > On Tue, Oct 15, 2024 at 12:28:20PM +0200, Christian Schulte wrote:
> >> On 10/15/24 12:09, Stuart Henderson wrote:
> >>> On 2024-10-15, Zé Loff wrote:
> On Tue, Oct 15, 2024 at 10:
On Tue, Oct 15, 2024 at 04:42:56AM -0600, Abel Abraham Camarillo Ojeda wrote:
> On Tue, Oct 15, 2024, 04:34 Christian Schulte wrote:
>
> > On 10/15/24 12:09, Stuart Henderson wrote:
> > > On 2024-10-15, Zé Loff wrote:
> > >> On Tue, Oct 15, 2024 at 10:14:42AM +0200, Christian Schulte wrote:
> >
On 10/15/24 12:45, Claudio Jeker wrote:
> On Tue, Oct 15, 2024 at 12:28:20PM +0200, Christian Schulte wrote:
>> On 10/15/24 12:09, Stuart Henderson wrote:
>>> On 2024-10-15, Zé Loff wrote:
On Tue, Oct 15, 2024 at 10:14:42AM +0200, Christian Schulte wrote:
> ulimit -d `ulimit -aH | grep da
On Tue, Oct 15, 2024 at 12:28:20PM +0200, Christian Schulte wrote:
> On 10/15/24 12:09, Stuart Henderson wrote:
> > On 2024-10-15, Zé Loff wrote:
> >> On Tue, Oct 15, 2024 at 10:14:42AM +0200, Christian Schulte wrote:
> >>> ulimit -d `ulimit -aH | grep data | awk '{print $2}'`
> >>> ulimit -n `uli
On Tue, Oct 15, 2024, 04:34 Christian Schulte wrote:
> On 10/15/24 12:09, Stuart Henderson wrote:
> > On 2024-10-15, Zé Loff wrote:
> >> On Tue, Oct 15, 2024 at 10:14:42AM +0200, Christian Schulte wrote:
> >>> ulimit -d `ulimit -aH | grep data | awk '{print $2}'`
> >>> ulimit -n `ulimit -aH | gr
On 10/15/24 12:09, Stuart Henderson wrote:
> On 2024-10-15, Zé Loff wrote:
>> On Tue, Oct 15, 2024 at 10:14:42AM +0200, Christian Schulte wrote:
>>> ulimit -d `ulimit -aH | grep data | awk '{print $2}'`
>>> ulimit -n `ulimit -aH | grep nofiles | awk '{print $2}'`
>
> ulimit -d `ulimit -dH` etc...
On 2024-10-15, Zé Loff wrote:
> On Tue, Oct 15, 2024 at 10:14:42AM +0200, Christian Schulte wrote:
>> ulimit -d `ulimit -aH | grep data | awk '{print $2}'`
>> ulimit -n `ulimit -aH | grep nofiles | awk '{print $2}'`
ulimit -d `ulimit -dH` etc... but then there's no point setting a
separate hard l
On Tue, Oct 15, 2024 at 10:14:42AM +0200, Christian Schulte wrote:
> On 10/15/24 09:51, Christian Schulte wrote:
> > On 10/14/24 15:49, Stuart Henderson wrote:
> >> On 2024-10-14, Christian Schulte wrote:
> >>> On 10/14/24 10:33, Stuart Henderson wrote:
> On 2024-10-12, Christian Schulte wro
On 10/15/24 09:51, Christian Schulte wrote:
> On 10/14/24 15:49, Stuart Henderson wrote:
>> On 2024-10-14, Christian Schulte wrote:
>>> On 10/14/24 10:33, Stuart Henderson wrote:
On 2024-10-12, Christian Schulte wrote:
> Take i386. Compile it with something -march=i686 or pentiumpro
On 10/14/24 15:49, Stuart Henderson wrote:
> On 2024-10-14, Christian Schulte wrote:
>> On 10/14/24 10:33, Stuart Henderson wrote:
>>> On 2024-10-12, Christian Schulte wrote:
Take i386. Compile it with something -march=i686 or pentiumpro by
default. That's it. Add support for the va
On 2024-10-14, Christian Schulte wrote:
> On 10/14/24 10:33, Stuart Henderson wrote:
>> On 2024-10-12, Christian Schulte wrote:
>>> Take i386. Compile it with something -march=i686 or pentiumpro by
>>> default. That's it. Add support for the various PAE MMU options.
>>
>> "That's it". "Add s
On 10/14/24 10:33, Stuart Henderson wrote:
> On 2024-10-12, Christian Schulte wrote:
>> Take i386. Compile it with something -march=i686 or pentiumpro by
>> default. That's it. Add support for the various PAE MMU options.
>
> "That's it". "Add support for". Do you really think it's a thing si
On 2024-10-12, Christian Schulte wrote:
> Take i386. Compile it with something -march=i686 or pentiumpro by
> default. That's it. Add support for the various PAE MMU options.
"That's it". "Add support for". Do you really think it's a thing simple
enough to sum up in a few words?
Last time st
On 10/12/24 18:33, Philip Guenther wrote:
> On Sat, Oct 12, 2024 at 3:58 AM Christian Schulte wrote:
>>
>> On 10/11/24 15:05, Claudio Jeker wrote:
>>> On Fri, Oct 11, 2024 at 03:00:23PM +0200, Christian Schulte wrote:
On 10/11/24 13:57, Stuart Henderson wrote:
> On 2024-10-09, obs...@loop
On Sat, Oct 12, 2024 at 3:58 AM Christian Schulte wrote:
>
> On 10/11/24 15:05, Claudio Jeker wrote:
> > On Fri, Oct 11, 2024 at 03:00:23PM +0200, Christian Schulte wrote:
> >> On 10/11/24 13:57, Stuart Henderson wrote:
> >>> On 2024-10-09, obs...@loopw.com wrote:
> > In a second server I hav
Christian Schulte:
> Hmm. Why not give up on i386 and make that i686 instead (Pentium Pro)?
> What I mean by this. Rename the current i386 to i686 by compiling it for
> i686
"i386" is the name of the architecture. OpenBSD doesn't run any
longer on actual 80386 CPUs. I forgot what the minimum is
On 10/11/24 15:05, Claudio Jeker wrote:
> On Fri, Oct 11, 2024 at 03:00:23PM +0200, Christian Schulte wrote:
>> On 10/11/24 13:57, Stuart Henderson wrote:
>>> On 2024-10-09, obs...@loopw.com wrote:
> In a second server I have upgraded from 7.5 i386 to 7.6 i386 but server
> sees only 4GB o
On 2024-10-11, Christian Schulte wrote:
> On 10/11/24 13:57, Stuart Henderson wrote:
>> On 2024-10-09, obs...@loopw.com wrote:
In a second server I have upgraded from 7.5 i386 to 7.6 i386 but server
sees only 4GB of RAM
>>>
Is anybody with similar experiences? Any ideas how to fix
On Fri, Oct 11, 2024 at 03:00:23PM +0200, Christian Schulte wrote:
> On 10/11/24 13:57, Stuart Henderson wrote:
> > On 2024-10-09, obs...@loopw.com wrote:
> >>> In a second server I have upgraded from 7.5 i386 to 7.6 i386 but server
> >>> sees only 4GB of RAM
> >>
> >>> Is anybody with similar ex
On 10/11/24 13:57, Stuart Henderson wrote:
> On 2024-10-09, obs...@loopw.com wrote:
>>> In a second server I have upgraded from 7.5 i386 to 7.6 i386 but server
>>> sees only 4GB of RAM
>>
>>> Is anybody with similar experiences? Any ideas how to fix RAM?
>>
>> run 64bit OpenBSD
>>
>> 32bit addres
On 2024-10-09, obs...@loopw.com wrote:
>> In a second server I have upgraded from 7.5 i386 to 7.6 i386 but server sees
>> only 4GB of RAM
>
>> Is anybody with similar experiences? Any ideas how to fix RAM?
>
> run 64bit OpenBSD
>
> 32bit address space is limited to a max of 4GB**, and some of tha
On Thu, 10 Oct 2024 00:44:07 +0200,
obs...@loopw.com wrote:
>
> ** PAE can work around this, but I’m not sure if OpenBSD supports PAE at
> ** all (and theres other issues/caveats with using PAE of course,
> ** including speed and security)
>
Do you know any example of vulnerability specified for
> In a second server I have upgraded from 7.5 i386 to 7.6 i386 but server sees
> only 4GB of RAM
> Is anybody with similar experiences? Any ideas how to fix RAM?
run 64bit OpenBSD
32bit address space is limited to a max of 4GB**, and some of that is eaten up
by PCI devices, etc.
** PAE can wor
On Thu, Oct 10, 2024 at 12:07:03AM +0200, Zbigniew Kossowski wrote:
> I have 2 HP Proliant miniserver and upgraded RAM from 1x4GB to 2x8GB (by YT
> user).
>
> First server:
> BIOS sees 16GB, dmesg sees 16GB spdmem0 and 1 but only 4GB of RAM
>
> # dmesg |grep mem
> real mem = 3622907904 (3455MB)
>
On 10/10/24 00:07, Zbigniew Kossowski wrote:
> I have 2 HP Proliant miniserver and upgraded RAM from 1x4GB to 2x8GB (by
> YT user).
>
> First server:
> BIOS sees 16GB, dmesg sees 16GB spdmem0 and 1 but only 4GB of RAM
>
> # dmesg |grep mem
> real mem = 3622907904 (3455MB)
> avail mem = 35394232
42 matches
Mail list logo
