Sorry, but my mail goes further.
It says it should be correct. For some definition of correct. It
should either behave somehow for a logical reason, or it should behave
in the historical fashion. Or once the historical behaviour is looked
at, if there is an argument that is wrong, then it
Thank you for that detail!
Addressing this one corner case would require substantial changes, I
think. Not worth it, in my opinion.
I think it would be worthwhile describing the multi-user mode of
operation of RCS in the manual, as it's currently completely
absent/omitted. Patch coming soon,
athom...@athompso.net wrote:
> Heh, good point. Didn't even occur to me because as it happens, I am
> running as root and would like to not change the ownership.-Adam
> On Apr. 29, 2020 13:32, Anders Andersson wrote:
>
> On Wed, Apr 29, 2020 at 7:46 PM Adam Thompson
> wrote:
> >
> >
On 2020-04-29, f.holop wrote:
> f.holop - Wed, 29 April 2020 at 14:57:46
>> i'll try to make a similar test with some linux live distro to see
>> if i get similar results.
>
> I have tested MX linux install ISO that also doubles as a Live distro.
>
> In the end it's apples and oranges because I
On 2020-04-29, Denis Fondras wrote:
> On Wed, Apr 29, 2020 at 09:58:27PM +0200, Lars Bonnesen wrote:
>> On an obsd 6.6, I use the vmx device, but the syntax:
>> inet 172.18.11.9 255.255.255.252 NONE vlandev vmx2 description VLAN703
>>
>
> vlandev is not supported any more.
> You have to use
f.holop - Wed, 29 April 2020 at 14:57:46
> i'll try to make a similar test with some linux live distro to see
> if i get similar results.
I have tested MX linux install ISO that also doubles as a Live distro.
In the end it's apples and oranges because I use the openbsd USB key to
boot the system
That did it... thanks!
On Wed, Apr 29, 2020 at 10:42 PM Sebastian Benoit
wrote:
> Lars Bonnesen(lars.bonne...@gmail.com) on 2020.04.29 21:58:27 +0200:
> > In earlier obsd versions I have been having success with this in
> > hostname.vlan703
> > inet 172.18.11.9 255.255.255.252 NONE vlandev em5
(To misc@ readers, this reply includes an earlier reply from me that
inadvertently wasn't copied to the list).
Allan Streib writes:
> multifred writes:
>
>> To boot OpenBSD you have to use the internal SATA or ATA devices.
>
> Thanks, I will try that. Was about to report that a 6.7 snapshot
Lars Bonnesen(lars.bonne...@gmail.com) on 2020.04.29 21:58:27 +0200:
> In earlier obsd versions I have been having success with this in
> hostname.vlan703
> inet 172.18.11.9 255.255.255.252 NONE vlandev em5 description VLAN703
>
> On an obsd 6.6, I use the vmx device, but the syntax:
> inet
On Wed, Apr 29, 2020 at 09:58:27PM +0200, Lars Bonnesen wrote:
> On an obsd 6.6, I use the vmx device, but the syntax:
> inet 172.18.11.9 255.255.255.252 NONE vlandev vmx2 description VLAN703
>
vlandev is not supported any more.
You have to use parent and vnetid, check man ifconfig.
In earlier obsd versions I have been having success with this in
hostname.vlan703
inet 172.18.11.9 255.255.255.252 NONE vlandev em5 description VLAN703
On an obsd 6.6, I use the vmx device, but the syntax:
inet 172.18.11.9 255.255.255.252 NONE vlandev vmx2 description VLAN703 does
not work as
Heh, good point. Didn't even occur to me because as it happens, I am
running as root and would like to not change the ownership.-Adam
On Apr. 29, 2020 13:32, Anders Andersson wrote:
On Wed, Apr 29, 2020 at 7:46 PM Adam Thompson
wrote:
>
> When I use co(1) with "-l" to check out a file
On Wed, Apr 29, 2020 at 7:46 PM Adam Thompson wrote:
>
> When I use co(1) with "-l" to check out a file (and/or "ci -l") is there
> any way to preserve file ownership and *not* have it reset to the user
> running co(1) or ci(1)?
> I don't see anything in rcs(1), co(1) or ci(1) that even mentions
When I use co(1) with "-l" to check out a file (and/or "ci -l") is there
any way to preserve file ownership and *not* have it reset to the user
running co(1) or ci(1)?
I don't see anything in rcs(1), co(1) or ci(1) that even mentions the
fact that the file will wind up owned by the user running
On Wed, Apr 29, 2020 at 05:45:30PM +0200, Marko Cupać wrote:
> Hi,
>
> on 6.6-RELEASE amd64, (sys)patched up to 019_smtpd_exec, I am noticing
> these:
>
> Apr 29 17:23:33 bgp1 bgpd[42338]: neighbor IP.ADD.RE.SS (desc): bad
> AGGREGATOR, AS 0 not allowed, attribute discarded
>
> My bgpd.conf is
Hi,
on 6.6-RELEASE amd64, (sys)patched up to 019_smtpd_exec, I am noticing
these:
Apr 29 17:23:33 bgp1 bgpd[42338]: neighbor IP.ADD.RE.SS (desc): bad
AGGREGATOR, AS 0 not allowed, attribute discarded
My bgpd.conf is almost default, announcing my AS to two upstream peers.
I wrote to my
I have an Macmini2,1 from mid 2007 with similar specs [1] and presumably
similar firmware. I tested a whole lot of combinations for booting it
and
came to the following conclusion:
To boot OpenBSD you have to use the internal SATA or ATA devices.
That means you need to use the CD/DVD-drive as
Stuart Henderson - Wed, 29 April 2020 at 12:24:50
> The boot loader only has access to what bios/uefi makes available,
> it looks like it isn't setting up your nvme device if you boot from USB
> unless you go through that menu. There isn't much OpenBSD can do about this.
i'll try to make a
On Wed, Apr 29, 2020 at 11:46:06AM +0200, Moises Simon wrote:
> On Tue, Apr 28, 2020 at 03:38:58PM -0500, Abel Abraham Camarillo Ojeda wrote:
> > I think increasing -b option in sndiod helps to prevent audio jumping, I
> > hear music with a local mpd with music directory over nfs, plus a lot of
>
On 2020-04-28, f.holop wrote:
> hi,
>
> i am trying to run openbsd on a very new notebook and it kind of works.
>
> i have taken away some space from win10 and created a partition, and the
> installation went well. atm i dont want to create a boot menu, so i
> just insert a usb key with openbsd
On April 29, 2020 12:06:02 PM GMT+03:00, "f.holop" wrote:
>Chris Bennett - Tue, 28 April 2020 at 23:03:32
>> Some BIOS's require you to select legacy boot and legacy boot before
>> UEFI in order to boot off of a USB. Also might need to turn off boot
>> security option, too.
>>
>> A lot of BIOS's
On Tue, Apr 28, 2020 at 03:38:58PM -0500, Abel Abraham Camarillo Ojeda wrote:
> I think increasing -b option in sndiod helps to prevent audio jumping, I
> hear music with a local mpd with music directory over nfs, plus a lot of
> firefox and chrome and hear no jumps , etc
>
> regards
I can
Chris Bennett - Tue, 28 April 2020 at 23:03:32
> Some BIOS's require you to select legacy boot and legacy boot before
> UEFI in order to boot off of a USB. Also might need to turn off boot
> security option, too.
>
> A lot of BIOS's suck nowadays. Who woulda thought that examining the
> BIOS
On Tue, Apr 28, 2020 at 3:21 PM Consus wrote:
> On Tue, Apr 28, 2020 at 03:01:15PM +0300, Yury Grebenkin wrote:
> > OpenBSD gives a better sound experience on my machine than several
> > Linux distributions I have used and FreeBSD. Just want to say thank
> > you to all the people involved and
24 matches
Mail list logo
