Re: mapping different client and server uid:gid for NFS

[Divan Santana]

>> How can one get both entries to work?
>
> By having them on different filesystems. You can't have diferent options
> on different directories exported from the same filesystem.
>
> See "BUGS" in exports(5).

Thanks Stuart for pointing that out.  I did read it but I didn't really
understand it at the time (which is likely my fault).

On that, does the example in the exports(5) not give a contradictory
option as a valid example when it is not? 

 For example:

   /usr /usr/local -maproot=0:10 friends
   /usr -maproot=daemon grumpy.cis.uoguelph.ca 131.104.48.16
   /usr -ro -mapall=nobody
   /u -maproot=bin: -network=131.104.48 -mask=255.255.255.0
   /u2 -maproot=root friends
   /u2 -alldirs -network=cis-net -mask=cis-mask

 Given that /usr, /u and /u2 are local filesystem mount points, the above
 example specifies the following: /usr is exported to hosts friends where
 friends is specified in the netgroup file with users mapped to their
 remote credentials and root mapped to UID 0 and GID 10.  It is exported
 read-write and the hosts in “friends” can mount either /usr or
 /usr/local.  It is exported to 131.104.48.16 and grumpy.cis.uoguelph.ca
 with users mapped to their remote credentials and root mapped to the user
 and groups associated with “daemon”; it is exported to the rest of the
 world as read-only with all users mapped to the user and groups
 associated with “nobody”.

It seems to indicate you can export /usr with an option of -maproot=0:10
to some hosts, while exporting the same /usr local FS to another host
with a different option of -maproot=daemon .  Is that wrong in the man
page?  Or is it because they are being exported to different hosts.

Re: /altroot with multiple encrypted disks

[Rubén Llorente]

Phil wrote:


I guess an an appropriate boot block needs to be installed on the second
disk (I don't know how to do that either). Also I would guess /altroot
would need to be temporarily mounted after each backup to swap the
parameters in the "/" and "/altroot" lines. I'm not knowlegeable enough
to think of anything else.

I might be talking c**p here and this uber-redundancy scenario isn't the
intended way for /altroot to be used. Otherwise I'd be very interested
and grateful to read any ideas anyone has on the subject.

Phil



I think if you need that sort of redundancy you just use a mirror RAID. 
Boot encrypted mirror RAID is supported (man boot(() and man bioctl(8)).


I suspect you could use installboot(8) on the disk holding your /altroot 
to make it bootable, but I have never tested such a thing.

Re: Disconnecting the mouse triggers unrecoverable error loop

[David Colburn]

Please see dmesg, below. Thanks for looking ...

On 10/28/24 04:01, Stuart Henderson wrote:

On 2024-10-27, David Colburn  wrote:

Simplified plus "sysctl grep hw" output:

Best to include a dmesg. sysctl hw doesn't give much information about
what's in the system.



b7$ dmesg
OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 68559847424 (65383MB)
avail mem = 66460274688 (63381MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xecfb0 (86 entries)
bios0: vendor Dell Inc. version "1.19.0" date 12/02/2021
bios0: Dell Inc. OptiPlex 7050
efi0 at bios0: UEFI 2.6
efi0: American Megatrends rev 0x5000b
acpi0 at bios0: ACPI 5.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT SSDT HPET SSDT 
SSDT UEFI SSDT LPIT SSDT SSDT SSDT SSDT DBGP DBG2 MSDM SLIC TPM2 SSDT 
ASF! BGRT DMAR
acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) 
PEGP(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) 
PXSX(S4) RP13(S4) PXSX(S4) [...]

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz, 3392.10 MHz, 06-9e-09, 
patch 00f8
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,RSBA,MISC_PKG_CT,ENERGY_FILT,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 
64b/line 4-way L2 cache, 6MB 64b/line 12-way L3 cache

cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 24MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz, 3392.11 MHz, 06-9e-09, 
patch 00f8
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,RSBA,MISC_PKG_CT,ENERGY_FILT,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 
64b/line 4-way L2 cache, 6MB 64b/line 12-way L3 cache

cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz, 3392.12 MHz, 06-9e-09, 
patch 00f8
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,RSBA,MISC_PKG_CT,ENERGY_FILT,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 
64b/line 4-way L2 cache, 6MB 64b/line 12-way L3 cache

cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz, 3392.11 MHz, 06-9e-09, 
patch 00f8
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,RSBA,MISC_PKG_CT,ENERGY_FILT,GDS_CTRL,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 256KB 
64b/line 4-way L2 cache, 6MB 64b/line 12-way L3 cache

cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xf000, bus 0-127
acpihpet0 at acpi0: 2399

Re: Minimum supported chipsets of amd64

[Benjamin Raskin]

Anon loli, please do everyone a favor and get off of this mailing list.

No one here likes or appreciates your long winded rants.

No one cares if you're autistic.

Plenty of people on this mailing list have told you to leave. I don't know
why you keep trying to be friendly to everyone here, as it's clearly not
working.

Go find another mailing list to spam.


Sincerely,
Everyone on misc

On Wednesday, October 30, 2024, Anon Loli  wrote:

> On Tue, Oct 29, 2024 at 12:26:54PM +0100, Christian Schulte wrote:
> > On 10/28/24 22:53, Anon Loli wrote:
> > > On Mon, Oct 28, 2024 at 05:35:47PM +0100, Christian Schulte wrote:
> > >> On 10/24/24 03:01, Mike Larkin wrote:
> > >>>
> > >>> Every one of us who has worked in this area, at this level, has read
> those
> > >>> 800+ page documents. Sometimes they are many thousands of pages (eg
> the latest
> > >>> Intel SDM or latest ACPI spec).
> > >>>
> > >>> Tell us what you are doing and what you want to know and maybe we
> can point
> > >>> you to the right docs, but there is no short-cutting reading the
> reference
> > >>> manuals.
> > >>>
> > >>
> > >> I would really like to understand why this architecture stood the test
> > >> of time. Just because it boots in 8 bit CPU mode from the 70ties not
> > >> even capable of beating a 6502? Just because developers were not
> > >> continuously forced to throw away all knowledge and could build upon
> it?
> > >> Seems to be the reason. Intel tried to throw away legacy burdens and
> got
> > >> set straight by AMD. I am currently approaching page 4000 of
> > >> documentation. Shaking heads. Unbelievable. What I am lacking so far
> is
> > >> a current PCI bus specification. This seems to not be available to non
> > >> members who I am certainly not. Coming from a hardware background,
> > >> documents like this
> > >>
> > >>  controller-hub-10-family-datasheet.pdf>
> > >>
> > >> clearly were a waste of time, at least when your goal is not to
> produce
> > >> mainboards. Well. Normally you would program devices directly. It even
> > >> contains write-once-by-firmware registers. It will take some time for
> me
> > >> to understand the reasoning behind this. Not questioning there are no
> > >> reasons for doing it that way. I am just trying to make me stop hating
> > >> that architecture. I am still failing at this task but I would like to
> > >> overcome this. At least it has linear address space. Oh. What a
> wonder.
> > >> Every 68k had this decades ago. Oh sorry. Your comments are very
> helpful
> > >> to me so far so thank you. Because the machine independent parts in
> the
> > >> kernel really are abstractions of formerly machine dependent parts,
> > >> understanding the worst case of those - namely x86 and amd64 - will
> help
> > >> me understand those. I am still in the process of reading x86/amd64
> > >> documentation even if it make me shake my head every so often.
> > >>
> > >> Regards,
> > >> --
> > >> Christian
> > >
> > > I just wrote a whole big-ass e-mail about how hardware has been shit
> for
> > > decades now.
> > > I do not feel like rewriting all of it right now it was a genius
> e-mail.
> > >
> > > I fucking hate when my e-mail client goes bananas because it's
> terminal based.
> > > Fuck escape sequences and stupid retarded Unix.
> > > When do escape sequences actually work as intended? When?
> > >
> > > Anyways suckless.org rocks, and should be implied to hardware.
> > >
> > > Open Source is Insufficient to Solve Trust Problems in Hardware
> > > https://youtube.com/watch?v=Hzb37RyagCQ
> > >
> > > How do you know the hardware in front of you actually conforms to the
> hardware
> > > design you might or might not have?
> > > You can't, it's not like software, at least you can't with existing
> hardware,
> > > watch the video.
> > >
> > > Mud towers build on mud foundation are still mud and will collapse
> under mud.
> > >
> > > This was more-less the important stuff
> > > Fuck I hate re-writing emails fuck me!
> > >
> >
> > Fuck. Ass. Genius. You maybe want to watch the Youtube Channels of Ben
> > Eater [1] or James Sharman [2] for a starting point talking about
> > hardware and how to build a CPU from scratch using bread boards. Fuck.
> > Ass. Genius. Then start reading about what microelectronics is about or
> > even get a degree in microelectronics. Fuck. Ass. Genius.
> >
> > [1] 
> > [2] 
> >
> > --
> > Christian
>
> Since I am autistic, I have trouble understanding when exactly someone is
> making fun of me or what tone they are using, especially trough text.
> For the sake of friendliness I shall assume that you said all of that in
> good
> spirit and were not condescending.
>
> I knew about Ben Eater for many years, I am extremely interested in
> microelectronics.. I am also interested in chemistry and creating your own
> transistors and stuff - silicon, e

Re: Both UK BSD User Groups gone?

[Polarian]

Hello,

> done.

Thank you :D

> unlikely for me, I'm quite far from London and I only really go there
> if I have to (usually on the way somewhere else).

Aren't you from Devon? That isn't exactly far at least by my standards
:P

Also quite frankly don't blame you, when someone thinks of a nice trip
in the UK, London isn't the first choice.

Take care,
-- 
Polarian
GPG signature: 0770E5312238C760
Jabber/XMPP: polar...@icebound.dev

Re: Apple Macbook Air (M1) lost bwfm

[Stuart Henderson]

On 2024-10-30, Jan Stary  wrote:
> On Sep 25 14:59:09, stu.li...@spacehopper.org wrote:
>> On 2024-09-25, Jan Stary  wrote:
>> > This is 7.6-beta/arm64 (#179) on an MBA (M1, 2020),
>> > the last kernel used is this:
>> >
>> > https://github.com/janstary/dmesg/blob/master/apple-macbook-air-A2337.20240915
>> >
>> > While this listing shows
>> > bwfm0 at pci1 dev 0 function 0 "Broadcom BCM4378" rev 0x03: msi
>> > and it worked (I pkg_add-u'd the packages after the upgrade),
>> > now I don't even have bwfm - with this same kernel, or with
>> > an older /obsd (#31 of May's 7.5).
>> >
>> > I blame the macOS upgrade to 15.0 (24A335) but I can't be sure.
>> > Is it possible the macOS upgrade did something to the firmware?
>> > OpenBSD has bwfm-firmware-20200316.1.3p3 installed.
>> 
>> OpenBSD/arm64 on Apple hardware doesn't use firmware from bwfm-firmware,
>> there's some process to copy it from MacOS
>
> Is there some other reason why bwfm-firmware is installed then?

Yes - to simplify things.


-- 
Please keep replies on the mailing list.

Re: Snapshots and packages

[Stuart Henderson]

On 2024-10-31, hahahahacker2009  wrote:
> Vào Th 5, 31 thg 10, 2024 vào lúc 03:35 J Doe
> đã viết:
>>
>> Hello,
>>
>> I have a basic question about following -current.
>>
>> I have an OpenBSD 7.5 system.  I want to grab the latest snapshot and update 
>> my packages.  Is the correct process as follows ?
>>
>> $ doas sysupgrade -s
>> $ doas pkg_add -uvi
>>
>
> Yes
>
>> The OpenBSD FAQ mentions that package updates changes when a snapshot is a 
>> release candidate.  In that case is the correct process as follows ?
>>
>> $ doas sysupgrade -s
>> $ doas pkg_add -D snap
>>
>
> TL;DR: when pkg_add -u breaks, run pkg_add -D snap -u instead

Or just set PKG_PATH to the snapshots directory and export it in your
shell startup script.

-- 
Please keep replies on the mailing list.

Re: Both UK BSD User Groups gone?

[Stuart Henderson]

On 2024-10-30, Polarian  wrote:
> I decided to look into it and found the ukfreebsd mailing list was
> somehow tied with the former user groups, I only got a single response
> [2] so I think its safe to say these can be removed from the OpenBSD
> User Group list, I am not really sure how to request this myself, was
> hoping someone could help out?

done.

> Lastly, to dip my toe into the ocean, hypothetically, if there was a
> meetup/miniconf in London, possibly next year who would be interested in

unlikely for me, I'm quite far from London and I only really go there
if I have to (usually on the way somewhere else).

Re: 7.5: Caja start up problem after 012_xserver

[Dan]

After played a little with other ports,
launched a couple of "pkg_delete -a" and
reapplied the patch 75_012.. Caja returned to run 
proprely, with all the icons and dark mode ok.
Thxs!

-Dan


Dan  wrote:

> 
> Hello,
> 
> After the latest patch, 012_xserver, installed via syspatch, Caja is
> not so friendly:
> 
> (caja:87440): dbind-WARNING **: 17:04:10.688: Couldn't connect to
> accessibility bus: Empty address '' Could not register the
> application: Timeout was reached
> 
> and it doesn't start under Xfce.
> 
> 
> -Dan
> 

7.5: SCIM gui hangs at first mouse interaction

[Dan]

Hello,

Using Xfce, xenodm free.

After sometimes I didn't do so I felt guilty and I got the idea to put
my mouse over the SCIM bar: it freeze the software (at best, I have
seen also a couple of Xorg crashes)

Tested reverting patch, this doesn't depends on the last 75_012
xserver patch. 


-Dan