On 2014-04-27, Edwin Amsler wrote:
> Good call. That would work around this current problem nicely. Though, I
> don’t know if this problem is with this specific core, or Cyrix chips in
> general.
>
> I won’t be too worried about the whole exercise. I was going to use it for a
> project, but I r
Hi Ingo,
On Sun, Apr 27, 2014 at 1:30 AM, Ingo Schwarze wrote:
>
> > I'm working on 5.2 version.
>
> That's unsupported for nearly a year now.
> Consider upgrading to 5.5 after May 1.
I know, but I'll never know what ancient versions my users will use, so I'm
using a (reasonably) old version to
Hi Michal,
Michal Lesiak wrote on Sun, Apr 27, 2014 at 12:01:54PM +0200:
> I know, but I'll never know what ancient versions my users will use,
> so I'm using a (reasonably) old version to build the package and
> compile stuff to retain some backwards-compatibility.
That's not a good plan at all
Hi Ingo,
On Sun, Apr 27, 2014 at 12:33 PM, Ingo Schwarze wrote:
> That's not a good plan at all. Sometimes, new binaries work on
> old versions and vice versa, but in general, that's not the case.
> So if you ship packages for 5.2-stable (well, actually, 5.2-obsolete),
> you force your users to
>Ok, got it. My understanding was that binaries complied on older systems have a
>better chance of running correctly on newer systems than the other way around.
Huh? You've understood incorrectly. Each release of OpenBSD is ABI
incompatible
with the previous, or next. We make no promises about
On Sat, 26 Apr 2014 09:27:50 -0700, Yassen Damyanov wrote:
> Pardon me, just saw that it says 1.0.0f, not 1.0.1f.
> Fear makes the wolf look bigger!
> Y.
>
>
There are other things to worry about if you are running 5.1, what about
that use-after-free race condition openssl has that is patched
Hi Theo,
On Sun, Apr 27, 2014 at 3:21 PM, Theo de Raadt wrote:
> Huh? You've understood incorrectly. Each release of OpenBSD is ABI
> incompatible
> with the previous, or next. We make no promises about ABI. Making such
> promises
> would be incompatible with making progress. If you want
Folks,
I'm trying to configure the amd service in order to auto-mount a NFS
directory. I noticed that adding the following line in
/etc/rc.conf.local:
amd_flags="-a /tmp/amd_mnt -l syslog -x all /nfs nfs.map"
the service fails to start, not being probably able to apply the
specified options to t
On Sun, April 27, 2014 22:32, Alessandro DE LAURENZIS wrote:
> Folks,
>
> I'm trying to configure the amd service in order to auto-mount a NFS
> directory. I noticed that adding the following line in
> /etc/rc.conf.local:
>
> amd_flags="-a /tmp/amd_mnt -l syslog -x all /nfs nfs.map"
>
> the service
On Sun 27/04, Kirill Bychkov wrote:
> On Sun, April 27, 2014 22:32, Alessandro DE LAURENZIS wrote:
> Hi.
> This is mentioned in /etc/rc.conf:
> amd_flags=NO# for normal use: "" and see amd_master below
>
Hi Kirill,
Thanks for your feedback. 5.4-Rel here, and:
just22@poseidon:[~]> eg
On Sat, Apr 26, 2014 at 6:25 PM, Yassen Damyanov wrote:
> Hello list,
>
> I worry about my 5.1 servers being at risk due to the heartbleed bug, as
> they report openssl 1.0.1f which is known to be vulnerable:
>
Funny to see people being scared about security issue of particular
component of syste
On 2014-04-27, Michał Lesiak wrote:
> Hi Ingo,
>
> On Sun, Apr 27, 2014 at 12:33 PM, Ingo Schwarze wrote:
>
>> That's not a good plan at all. Sometimes, new binaries work on
>> old versions and vice versa, but in general, that's not the case.
>> So if you ship packages for 5.2-stable (well, actu
The constant MFSNAMELEN as defined in:
lib/libc/sys/getfsstat.2:#define MFSNAMELEN 16
lib/libc/sys/statfs.2:#define MFSNAMELEN 16
sys/sys/mount.h: #define MFSNAMELEN 16
defines the fs type name and, according to comments, it includes nul
terminating character.
The following code mak
Ping.
Can anyone confirm or deny whether or not the newer Thinkpad
tablets' styluses work as an input device? I see that there is a
usbtablet(4) driver in xenocara, with people reporting success
using external tablets, so it would probably be a matter of
whether or not the newer Thinkpads still u
On April 27, 2014 6:46:31 PM CDT, Bryan Linton wrote:
>Ping.
>
>Can anyone confirm or deny whether or not the newer Thinkpad
>tablets' styluses work as an input device? I see that there is a
>usbtablet(4) driver in xenocara, with people reporting success
>using external tablets, so it would proba
Is OpenBSD capable of booting from pure UEFI yet? This basically translates to
"Is there a UEFI capable bootloader" since I don't have secure boot or anything
turned on. I'm rather happy not having to deal with the bios at the moment so
having to turn legacy boot back on would be really annoying
On Mon, Apr 28, 2014 at 5:47 AM, Tekk wrote:
> Is OpenBSD capable of booting from pure UEFI yet? This basically
> translates to "Is there a UEFI capable bootloader" since I don't have
> secure boot or anything turned on. I'm rather happy not having to deal with
> the bios at the moment so having
On Sun 27/04, Kenneth R Westerback wrote:
> On Fri, Apr 25, 2014 at 12:31:16PM +0200, Alessandro DE LAURENZIS wrote:
> > On Tue 22/04, Kenneth Westerback wrote:
> > > >
> > > > Another thing: as highlighted in my initial message, I'm using the
> > > > loopback i/f as router address in the lease dec
18 matches
Mail list logo
