Re: Should 80MB of RAM be enough for kernel relinking on i386?
On Wed, 22 Sep 2021 17:27:30 +0100
"Patrick Harper" wrote:
> If the situation isn't going to change anytime soon then I have some
> diffs for INSTALL.i386 and INSTALL.amd64. The latter has not specified
> disk requirements, I guess since anyone who owns an amd64 system will
> very likely be using a disk big enough for X, so I figured that the
> same would apply to any user of an i386 system that meets the proposed
> minimum RAM. These are based on the 2021-09-21 snapshot versions.
>
> --- INSTALL.i386.txtWed Sep 22 16:52:38 2021
> +++ INSTALL.i386_newWed Sep 22 16:51:17 2021
> @@ -201,10 +201,7 @@ OpenBSD/i386 7.0 supports most SMP (Symmetrical
> MultiP
> systems. To support SMP operation, a separate SMP kernel (bsd.mp)
> is included with the installation file sets.
>
> -The minimal configuration to install the system is 32MB of RAM and
> -at least 250MB of disk space to accommodate the `base' set.
> -To install the entire system, at least 600MB of disk are required,
> -and to run X or compile the system, more RAM is recommended.
> +The minimal configuration to install the system is 512MB of RAM.
>
> Please refer to the website for a full list of supported hardware:
> https://www.openbsd.org/i386.html
Hello.
I have Soekris net4801 gateway/firewall and it only has 128Mb of RAM.
I usually upgrade to -current by putting the CF card into a different
machine, since writing to CF card is slow on Soekris, but tonight I
upgraded to -current using the box itself and timed how long it took to
relink the kernel - 25 minutes.
It has 256Mb of swap. Eh, 259.9M apparently.
After-reboot relinking is currently disabled until I figure out
what to put in the new bsd.re-config to change flags for
wd to 0x0ff0 automatically, no luck yet.
Soekris dmesg:
OpenBSD 7.0 (GENERIC) #203: Wed Sep 22 19:24:38 MDT 2021
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
real mem = 133709824 (127MB)
avail mem = 114921472 (109MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 20/80/03, BIOS32 rev. 0 @ 0xf7840
pcibios0 at bios0: rev 2.0 @ 0xf/0x1
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc8000/0x9000
cpu0 at mainbus0: (uniprocessor)
cpu0: Geode(TM) Integrated Processor by National Semi ("Geode by NSC"
586-class) 267 MHz, 05-04-00
cpu0: FPU,TSC,MSR,CX8,CMOV,MMX
cpu0: TSC disabled
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Cyrix GXm PCI" rev 0x00
sis0 at pci0 dev 6 function 0 "NS DP83815" rev 0x00, DP83816A: irq 10, address
00:00:24:c3:54:68
nsphyter0 at sis0 phy 0: DP83815 10/100 PHY, rev. 1
sis1 at pci0 dev 7 function 0 "NS DP83815" rev 0x00, DP83816A: irq 10, address
00:00:24:c3:54:69
nsphyter1 at sis1 phy 0: DP83815 10/100 PHY, rev. 1
sis2 at pci0 dev 8 function 0 "NS DP83815" rev 0x00, DP83816A: irq 10, address
00:00:24:c3:54:6a
nsphyter2 at sis2 phy 0: DP83815 10/100 PHY, rev. 1
ral0 at pci0 dev 10 function 0 "Ralink RT2860" rev 0x00: irq 11, address
00:1d:6a:0e:80:cd
ral0: MAC/BBP RT2860 (rev 0x0101), RF RT2820 (MIMO 2T3R)
ral1 at pci0 dev 14 function 0 "Ralink RT2560" rev 0x01: irq 5, address
00:13:d3:00:9f:7a
ral1: MAC/BBP RT2560 (rev 0x04), RF RT2525
gscpcib0 at pci0 dev 18 function 0 "NS SC1100 ISA" rev 0x00
gpio0 at gscpcib0: 64 pins
"NS SC1100 SMI" rev 0x00 at pci0 dev 18 function 1 not configured
pciide0 at pci0 dev 18 function 2 "NS SCx200 IDE" rev 0x01: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 1-sector PIO, LBA48, 3811MB, 7806960 sectors
wd0(pciide0:0:0): using PIO mode 4
geodesc0 at pci0 dev 18 function 5 "NS SC1100 X-Bus" rev 0x00: iid 6 revision 3
wdstatus 0
ohci0 at pci0 dev 19 function 0 "Compaq USB OpenHost" rev 0x08: irq 9, version
1.0, legacy support
isa0 at gscpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS
gpio1 at nsclpcsio0: 29 pins
gscsio0 at isa0 port 0x15c/2: SC1100 SIO rev 1:
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb0 at ohci0: USB revision 1.0
uhub0 at usb0 configuration 1 interface 0 "Compaq OHCI root hub" rev 1.00/1.00
addr 1
dt: 445 probes
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
root on wd0a (1f081011692bae0c.a) swap on wd0b dump on wd0b
Re: Some more humor, maybe?
Yes On Thu., Sep. 23, 2021, 12:11 a.m. flint pyrite, wrote: > forget about host, it is plausible to self host > > What remains is the catalyst? > > Remember movement would not occur without involvement > >
Some more humor, maybe?
forget about host, it is plausible to self host What remains is the catalyst? Remember movement would not occur without involvement
nextcloudclient fails to work with gnome-keyring
Hello there! I have been testing some machine for deployment as a workstation. I have set up XFCE4 as a desktop environment (which is launched by my .xsession file). I have also set nextcloudclient and installed gnome-keyring-daemon. I have found that Nextcloud Client is unable to leverage gnome-keyring in order to save credentials securely. Nextcloud Client always complains because the secrets agent cannot be used because of an "Unknown Error". Things I have tried in order to properly launch gnome-keyring-daemon include: Using an .xsession script such as: . $HOME/.profile eval $(/usr/local/bin/gnome-keyring-daemon --start ) export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK /usr/local/bin/startxfce4 Also, I have tried using the XFCE4 desktop configuration tool, enabling Gnome Services on startup in the Advanced tab. Essentially, I can get the keyring started, but nextcloud, or qtkeychain, or whatever backend is suppose to talk to gnome-keyring fails to find it. As a workarround I am using Kwalletd5 for the time being, which works. If anybody has any guide or instructions to set up gnome-keyring with nextcloudclient, or ideas to get such setup working, I am eager to read your ideas. The working environment is OpenBSD 6.9 -RELEASE amd64. -- OpenPGP Key Fingerprint: 543F EB89 7FDE 8E33 AFF7 E794 E4AB 4807 58F7 6C76
Re: 6.9/amd64 runaway acpi process on Thinkpad T580
I dunno if this is helpful, but I just unplugged my thinkpad and triggered the behavior. ACPI shot right up, and in this case the "charging" LED has stayed on. I've never triggered it by unplugging before, but the symptoms are the same. The system was under some load while doing so (watching a video in Firefox and extracting a backup.) The last line in dmesg also seems weird to me; it might be a firmware thing, from that. Danny OpenBSD 7.0 (GENERIC.MP) #224: Mon Sep 20 11:44:33 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 38362574848 (36585MB) avail mem = 37183885312 (35461MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x6ecc4000 (63 entries) bios0: vendor LENOVO version "N24ET49W (1.24 )" date 04/19/2019 bios0: LENOVO 20L50054US acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT TPM2 UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT SSDT SSDT BOOT BATB SLIC SSDT SSDT SSDT LPIT WSMT SSDT SSDT SSDT DBGP DBG2 MSDM DMAR ASF! FPDT UEFI acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1591.45 MHz, 06-8e-0a 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,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 256KB 64b/line 8-way L2 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.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1596.28 MHz, 06-8e-0a 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,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1596.28 MHz, 06-8e-0a 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,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1596.28 MHz, 06-8e-0a 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,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz, 1596.28 MHz, 06-8e-0a cpu4: 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_CTR
Re: Should 80MB of RAM be enough for kernel relinking on i386?
If the situation isn't going to change anytime soon then I have some diffs for INSTALL.i386 and INSTALL.amd64. The latter has not specified disk requirements, I guess since anyone who owns an amd64 system will very likely be using a disk big enough for X, so I figured that the same would apply to any user of an i386 system that meets the proposed minimum RAM. These are based on the 2021-09-21 snapshot versions. --- INSTALL.i386.txtWed Sep 22 16:52:38 2021 +++ INSTALL.i386_newWed Sep 22 16:51:17 2021 @@ -201,10 +201,7 @@ OpenBSD/i386 7.0 supports most SMP (Symmetrical MultiP systems. To support SMP operation, a separate SMP kernel (bsd.mp) is included with the installation file sets. -The minimal configuration to install the system is 32MB of RAM and -at least 250MB of disk space to accommodate the `base' set. -To install the entire system, at least 600MB of disk are required, -and to run X or compile the system, more RAM is recommended. +The minimal configuration to install the system is 512MB of RAM. Please refer to the website for a full list of supported hardware: https://www.openbsd.org/i386.html --- INSTALL.amd64.txt Wed Sep 22 16:52:48 2021 +++ INSTALL.amd64_new Wed Sep 22 16:51:12 2021 @@ -202,6 +202,8 @@ is included with the installation file sets. OpenBSD/amd64 7.0 supports both UEFI/GPT booting and BIOS/MBR booting. +The minimal configuration to install the system is 512MB of RAM. + Please refer to the website for a full list of supported hardware. https://www.openbsd.org/amd64.html Patrick Harper
Radiusd anyone know of a Simple to use web front end for usermanagement ?
Hi All, I was wondering is there a front end web interface out there for radiusd (for the un inducted users who wouldnt be comfortable with the command line I would rather use radiusd than freeradius alternatives ... perhaps im missing something in the ma pages any tips tricks would be welcome thanks -- Kindest regards, Tom Smyth.
Re: OpenSMTPd: Ignoring /etc/hosts file?
> On Mon, Sep 13, 2021 at 12:28:04PM +0200, Simon Hoffmann wrote: > > > do you have "lookup file bind" record in your /etc/resolv.conf file? > > > > This option is not available in the current debian version. > > > FWIW, the equivalent setting on glibc-based Linux systems would be the > `hosts` line in /etc/nsswitch.conf: > > $ grep hosts /etc/nsswitch.conf > hosts: files dns > I had this setting, but it did not change the behaviour... signature.asc Description: PGP signature
Re: OpenSMTPd: Ignoring /etc/hosts file?
On Mon, Sep 13, 2021 at 12:28:04PM +0200, Simon Hoffmann wrote: > > do you have "lookup file bind" record in your /etc/resolv.conf file? > > This option is not available in the current debian version. FWIW, the equivalent setting on glibc-based Linux systems would be the `hosts` line in /etc/nsswitch.conf: $ grep hosts /etc/nsswitch.conf hosts: files dns
