RE: Hardening browser
Haai, "Tomasz Rola" wrote: > On Thu, Mar 05, 2020 at 12:25:56PM +0100, zeurk...@volny.cz wrote: >> > > I use lynx a lot, very nice tool. It also helped me to restart my > browsing of gopher sites. There was plenty of them 20+ years ago, now > it is just a handful of servers. But still, better than nothing. Menever quite was into Gopher, but mereally should try and have a look someday... >> Occasionally, when really pressed, meruns 'tails', a specialized Lunix >> distro, from a DVD on a spare craptop; at least that way, mecan get rid >> of the bloated, buggy shit by simply turning off the machine. > > I do not know tails, only read about it. > > Using separate computers for different roles might be a way of the > future. A very convoluted way. But one cannot count too much on > security offered by modern popular cpus and there is always a chance > to be struck by something unexpected: I have just read that bmp file > from game server might make buffer overflow on client side. So, one > machine for gaming, one for reading, one for shopping and one for > work. And one for listing the music. 2003 came calling ;) Seriously: what you fear has already come to pass, for many people, long ago. It's even in the mainstream now: there, it's considered good practice to design an "app" so that a luser can seamlessly use it across the various "devices" in its possession. Or is merunning behind and did that idea die? > I will never propose this kind of solution to normal people. :-) Thankfully, we're not normal here =) >> -- >> Friggin' Machines! > > Oh no, it is not the machines. It is their masters. And their creators. The phrase is from an old Quake map that me's long since forgotten the name of. --zeurkous. -- Friggin' Machines!
Re: pkg_outdated binary?
Hi Luke, On Mon, Mar 09, 2020 at 01:55:18PM -0600, Luke A. Call wrote: | Hi. I see a manual page for pkg_outdated, online and on my 6.6 stable | machine, but no binary, or result from "type pkg_outdated", even with, | as root: | cd / | find . -iname "*outdated*" 2>&1 | less | ...though that did find some perl things. | Check out the ports tree and try again. More specifically, look in /usr/ports/infrastructure/bin There's a number of tools there that are of use when porting, pkg_outdated is one such tool. It requires the ports tree to operate (it compares installed packages with versions found in the ports tree) and as such is only available in the ports tree itself. Cheers, Paul 'WEiRD' de Weerd -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
pkg_outdated binary?
Hi. I see a manual page for pkg_outdated, online and on my 6.6 stable machine, but no binary, or result from "type pkg_outdated", even with, as root: cd / find . -iname "*outdated*" 2>&1 | less ...though that did find some perl things. Am I looking the wrong way? Thanks much. dmesg: OpenBSD 6.6 (GENERIC.MP) #5: Sun Feb 16 01:56:11 MST 2020 r...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16033533952 (15290MB) avail mem = 15534886912 (14815MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebf90 (49 entries) bios0: vendor American Megatrends Inc. version "204" date 11/20/2014 bios0: ASUSTeK COMPUTER INC. X550ZA acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT ECDT MCFG MSDM HPET UEFI SSDT SSDT CRAT SSDT SSDT SSDT SSDT acpi0: wakeup devices LOM_(S4) SBAZ(S4) ECIR(S4) OHC1(S4) EHC1(S4) OHC2(S4) EHC2(S4) OHC3(S4) EHC3(S4) OHC4(S4) XHC0(S4) XHC1(S4) ODD8(S3) GLAN(S4) LID_(S5) SLPB(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 16 (boot processor) cpu0: AMD A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2496.12 MHz, 15-30-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,CPCTR,DBKP,PERFTSC,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu0: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 17 (application processor) cpu1: AMD A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2495.35 MHz, 15-30-01 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,CPCTR,DBKP,PERFTSC,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu1: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 18 (application processor) cpu2: AMD A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2495.36 MHz, 15-30-01 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,CPCTR,DBKP,PERFTSC,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu2: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 19 (application processor) cpu3: AMD A10-7400P Radeon R6, 10 Compute Cores 4C+6G, 2495.35 MHz, 15-30-01 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,CPCTR,DBKP,PERFTSC,ITSC,FSGSBASE,BMI1,XSAVEOPT cpu3: 96KB 64b/line 3-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache cpu3: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu3: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 21, 24 pins ioapic1 at mainbus0: apid 1 pa 0xfec01000, version 21, 32 pins acpiec0 at acpi0 acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PB21) acpiprt2 at acpi0: bus -1 (PB22) acpiprt3 at acpi0: bus -1 (PB31) acpiprt4 at acpi0: bus -1 (PB32) acpiprt5 at acpi0: bus -1 (PB33) acpiprt6 at acpi0: bus -1 (PB34) acpiprt7 at acpi0: bus 2 (PE20) acpiprt8 at acpi0: bus -1 (PE21) acpiprt9 at acpi0: bus 3 (PE22) acpiprt10 at acpi0: bus -1 (PE23) acpicpu0 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS acpicpu1 at
Re: heads up: amd64 snap
On Mon, Mar 09, 2020 at 07:28:10PM +0100, Paul de Weerd wrote: | Indeed it did :) My machine would not POST anymore (Dell Optiplex | 9020; dmesg at the end) I meant: dmesg in the follow-up e-mail... OpenBSD 6.6-current (GENERIC.MP) #38: Sat Mar 7 19:58:17 MST 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34243903488 (32657MB) avail mem = 33193492480 (31655MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec410 (88 entries) bios0: vendor Dell Inc. version "A22" date 02/01/2018 bios0: Dell Inc. OptiPlex 9020 acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT SLIC LPIT SSDT SSDT SSDT HPET SSDT MCFG SSDT ASF! DMAR acpi0: wakeup devices UAR1(S3) RP01(S4) PXSX(S4) PXSX(S4) PXSX(S4) RP05(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S4) HDEF(S4) PEG0(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) i7-4770 CPU @ 3.40GHz, 3691.95 MHz, 06-3c-03 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,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 3691.47 MHz, 06-3c-03 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,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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) i7-4770 CPU @ 3.40GHz, 3691.47 MHz, 06-3c-03 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,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,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) i7-4770 CPU @ 3.40GHz, 3691.47 MHz, 06-3c-03 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,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins acpihpet0 at acpi0: 14318179 Hz acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus 2 (RP05) acpiprt3 at acpi0: bus -1 (PEG0) acpiprt4 at acpi0: bus -1 (PEG1) acpiprt5 at acpi0: bus -1 (PEG2) acpiec0 at acpi0: not present acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpitz0 at acpi0: critical temperature is 105 degC acpitz1 at acpi0: critical temperature is 105 degC acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x acpicmos0 at acpi0 acpibtn0 at acpi0: PWRB "PNP0C14" at acpi0 not configured acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD1F cpu0: using VERW MDS workaround (except on vmm entry) cpu0: Enhanced SpeedStep 3691 MHz: speeds: 3401, 3400, 3200, 3000, 2800, 2700, 2500, 2300, 2100, 1900, 1700, 1500, 1400, 1200, 1000, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06 drm0 at inteldrm0 inteldrm0: msi
Re: heads up: amd64 snap
On Mon, Mar 09, 2020 at 06:47:10PM +0100, Sebastien Marie wrote: | On Mon, Mar 09, 2020 at 04:51:00PM +, Anthony Campbell wrote: | > On 09 Mar 2020, Otto Moerbeek wrote: | > > On Mon, Mar 09, 2020 at 03:56:53PM +, Anthony Campbell wrote: | > > | > > > This discussion is very interesting. The same thing happened to me | > > > on 6 March, when after completing the upgrade my Dell Optiplex 3020 | > > > refused to boot. I assumed it was a hardware failure and spent the | > > > next three days bringing up an older Acer n460 which the Dell had | > > > replaced. | | yes, it looks like a hardware failure. Indeed it did :) My machine would not POST anymore (Dell Optiplex 9020; dmesg at the end) | in my case, 4 hosts with the same motherboard model failed at the same time (I | ran sysupgrade via ansible), so hardware failure was a bit excluded. I only have this one machine that showed the behaviour. Several VMs, my gateway and my laptop worked fine so I didn't really tie it to the bootloader changes (especially since the machine didn't POST). I couldn't boot from any other medium as long as the boot disk (an SSD) was connected; my conclusion was that a failed SSD prevented the system from POSTing (something I've seen in the past with failed HDDs). | > > > I don't have the facility at present to put the disk in another | > > > machine so it looks like I'm stuck. | | I agree it could be difficult. If the disk is plugged, bios stuck. If the disk | is unplugged, bios is fine, but you can't modify the disk data. | | As sthen@ said, you could try to change bios setting to make the bios to not | look at the disk. I dunno if it would work or not. I played around with that a little bit, but didn't get to a working machine. | Alternatively, if you disk support hotplugging (sata disk should), try to | connect the disk after the bios started could help. If so, I would try to plug | it as soon as possible after bios init. That was a bit of a scary option for me :) | Depending your configuration, you could also try to use USB/SATA or USB/IDE | adapter (depending your disk), in order to plug the disk after bios init. For | me, I had problem with this method too: when my sata disk is plugged in sata | connector it is showed with 512 bytes/sector, whereas with USB/SATA connector it | showed with 4096 bytes/sector and so disklabel is incoherent. In the end, after reading Otto's mail about reverting his changes, I connected the SSD from my not-booting machine to my laptop and upgraded the snapshot on it. That allowed my desktop machine to boot properly again. I've seen Otto's commit message from earlier today, so I will test out the next snap on my machine tomorrow. At least now I know not to jump to conclusions about failing hardware :) Thanks to Otto for his work on this area; looking forward to running my machine on all-ffs2. Cheers, Paul -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: heads up: amd64 snap
On Mon, Mar 09, 2020 at 04:51:00PM +, Anthony Campbell wrote: > On 09 Mar 2020, Otto Moerbeek wrote: > > On Mon, Mar 09, 2020 at 03:56:53PM +, Anthony Campbell wrote: > > > > > This discussion is very interesting. The same thing happened to me > > > on 6 March, when after completing the upgrade my Dell Optiplex 3020 > > > refused to boot. I assumed it was a hardware failure and spent the > > > next three days bringing up an older Acer n460 which the Dell had > > > replaced. yes, it looks like a hardware failure. in my case, 4 hosts with the same motherboard model failed at the same time (I ran sysupgrade via ansible), so hardware failure was a bit excluded. > > > I don't have the facility at present to put the disk in another > > > machine so it looks like I'm stuck. I agree it could be difficult. If the disk is plugged, bios stuck. If the disk is unplugged, bios is fine, but you can't modify the disk data. As sthen@ said, you could try to change bios setting to make the bios to not look at the disk. I dunno if it would work or not. Alternatively, if you disk support hotplugging (sata disk should), try to connect the disk after the bios started could help. If so, I would try to plug it as soon as possible after bios init. Depending your configuration, you could also try to use USB/SATA or USB/IDE adapter (depending your disk), in order to plug the disk after bios init. For me, I had problem with this method too: when my sata disk is plugged in sata connector it is showed with 512 bytes/sector, whereas with USB/SATA connector it showed with 4096 bytes/sector and so disklabel is incoherent. I hope it helps. -- Sebastien Marie
Re: heads up: amd64 snap
On 09 Mar 2020, Anthony Campbell wrote: > On 09 Mar 2020, Otto Moerbeek wrote: > > On Mon, Mar 09, 2020 at 03:56:53PM +, Anthony Campbell wrote: > > > > > On 07 Mar 2020, Amit Kulkarni wrote: > > > [snip] > > > > > > > > > > > will do as you suggest. > > > > > > > > Thanks > > > > > > > > > > > > > > This discussion is very interesting. The same thing happened to me > > > on 6 March, when after completing the upgrade my Dell Optiplex 3020 > > > refused to boot. I assumed it was a hardware failure and spent the > > > next three days bringing up an older Acer n460 which the Dell had > > > replaced. > > > > > > > > > I don't have the facility at present to put the disk in another > > > machine so it looks like I'm stuck. > > > > > > > > > Anthony > > > > > > -- > > > Anthony Campbell http://www.acampbell.uk > > > > > > > There are other ways: dd a miniroot to a usb stick, boot from that > > into boot> > > boot the harddisk and do an upgrade. See the boot(8) man page for details. > > > > -Otto > > > > > > Unfortunately I can't access the BIOS at all to tell it to boot from > the stick. Pressing F2 during boot is supposed to do this but I've > tried about a hundred times without success. > Sorry, I misunderstood - I've just tried it out and I see that the Dell will boot from the stick without needing to be told to do so by the BIOS. I'll take that route. Apologies for the noise. Anthony > -- > Anthony Campbell http://www.acampbell.uk -- Anthony Campbellhttp://www.acampbell.uk
Re: heads up: amd64 snap
On 2020-03-09, Anthony Campbell wrote: > > Unfortunately I can't access the BIOS at all to tell it to boot from > the stick. Pressing F2 during boot is supposed to do this but I've > tried about a hundred times without success. Try unplugging the disk and see if you can then get into the bios menu. Maybe with the boot order altered it will just boot from USB anyway, if not, I have had times in the past where I've had to get past POST and into a bootloader before powering up the disk in able to be able to wipe something that the bios didn't like. Not sure if this is 'recommended' but it has got me out of a hole before.
Re: heads up: amd64 snap
Anthony Campbell wrote: > On 09 Mar 2020, Otto Moerbeek wrote: > > On Mon, Mar 09, 2020 at 03:56:53PM +, Anthony Campbell wrote: > > > > > On 07 Mar 2020, Amit Kulkarni wrote: > > > [snip] > > > > > > > > > > > will do as you suggest. > > > > > > > > Thanks > > > > > > > > > > > > > > This discussion is very interesting. The same thing happened to me > > > on 6 March, when after completing the upgrade my Dell Optiplex 3020 > > > refused to boot. I assumed it was a hardware failure and spent the > > > next three days bringing up an older Acer n460 which the Dell had > > > replaced. > > > > > > > > > I don't have the facility at present to put the disk in another > > > machine so it looks like I'm stuck. > > > > > > > > > Anthony > > > > > > -- > > > Anthony Campbell http://www.acampbell.uk > > > > > > > There are other ways: dd a miniroot to a usb stick, boot from that > > into boot> > > boot the harddisk and do an upgrade. See the boot(8) man page for details. > > > > -Otto > > > > > > Unfortunately I can't access the BIOS at all to tell it to boot from > the stick. Pressing F2 during boot is supposed to do this but I've > tried about a hundred times without success. Wow sounds like quite a drama.. it must have been IMPOSSIBLE to install openbsd in the first place /sarc...
Re: heads up: amd64 snap
On 09 Mar 2020, Otto Moerbeek wrote: > On Mon, Mar 09, 2020 at 03:56:53PM +, Anthony Campbell wrote: > > > On 07 Mar 2020, Amit Kulkarni wrote: > > [snip] > > > > > > > > will do as you suggest. > > > > > > Thanks > > > > > > > > > > This discussion is very interesting. The same thing happened to me > > on 6 March, when after completing the upgrade my Dell Optiplex 3020 > > refused to boot. I assumed it was a hardware failure and spent the > > next three days bringing up an older Acer n460 which the Dell had > > replaced. > > > > > > I don't have the facility at present to put the disk in another > > machine so it looks like I'm stuck. > > > > > > Anthony > > > > -- > > Anthony Campbellhttp://www.acampbell.uk > > > > There are other ways: dd a miniroot to a usb stick, boot from that > into boot> > boot the harddisk and do an upgrade. See the boot(8) man page for details. > > -Otto > > Unfortunately I can't access the BIOS at all to tell it to boot from the stick. Pressing F2 during boot is supposed to do this but I've tried about a hundred times without success. -- Anthony Campbellhttp://www.acampbell.uk
Re: heads up: amd64 snap
On Mon, Mar 09, 2020 at 03:56:53PM +, Anthony Campbell wrote: > On 07 Mar 2020, Amit Kulkarni wrote: > [snip] > > > > > will do as you suggest. > > > > Thanks > > > > > > This discussion is very interesting. The same thing happened to me > on 6 March, when after completing the upgrade my Dell Optiplex 3020 > refused to boot. I assumed it was a hardware failure and spent the > next three days bringing up an older Acer n460 which the Dell had > replaced. > > > I don't have the facility at present to put the disk in another > machine so it looks like I'm stuck. > > > Anthony > > -- > Anthony Campbell http://www.acampbell.uk > There are other ways: dd a miniroot to a usb stick, boot from that into boot> boot the harddisk and do an upgrade. See the boot(8) man page for details. -Otto
Re: heads up: amd64 snap
On 07 Mar 2020, Amit Kulkarni wrote: [snip] > > will do as you suggest. > > Thanks > > This discussion is very interesting. The same thing happened to me on 6 March, when after completing the upgrade my Dell Optiplex 3020 refused to boot. I assumed it was a hardware failure and spent the next three days bringing up an older Acer n460 which the Dell had replaced. I don't have the facility at present to put the disk in another machine so it looks like I'm stuck. Anthony -- Anthony Campbellhttp://www.acampbell.uk
Re: Compiler warning in ctype.h
On 2020/03/09 11:34, Janne Johansson wrote: > Den fre 6 mars 2020 kl 12:29 skrev Thomas de Grivel : > > > Hello, > > > > I was using base gcc but switching to base clang fixes the warnings on > > -current at least. > > Is base gcc not supported anymore ? > > > > I think you are supposed to use whatever gets used when you call "cc" on > the OpenBSD platform you are on, and if need be, get gcc from ports for an > uptodate version of it. Some arches (aarch64) only ever had clang. Some arches (i386, armv7) moved to clang and have removed gcc. Some arches (amd64, mips64 [sgi,octeon]) have moved to clang but still have /usr/bin/gcc present, mostly so that people making changes to the base OS have some easy way to check if their changes don't negatively impact gcc 4.2.1 arches. (However this does make it harder to pick up on things in ports which hardcode "gcc" and fail if not present!). For these arches, clang is the supported compiler. Some arches still use gcc. gcc 3 for m88k. gcc 4.2.1 for alpha hppa mips64el powerpc sh sparc64. Of these, mips64el powerpc sparc64 *also* have clang built, but have not switched to it as the main system compiler. For all of these arches, gcc is the supported compiler. > Since arches are moving from gcc into clang (at various speeds), its not > unthinkable for some of them to have both over the transition, but the > "supported" one is always the binary that gets run if you use "cc" for > compiler and nothing else. yep.
Re: Compiler warning in ctype.h
Den fre 6 mars 2020 kl 12:29 skrev Thomas de Grivel : > Hello, > > I was using base gcc but switching to base clang fixes the warnings on > -current at least. > Is base gcc not supported anymore ? > I think you are supposed to use whatever gets used when you call "cc" on the OpenBSD platform you are on, and if need be, get gcc from ports for an uptodate version of it. Since arches are moving from gcc into clang (at various speeds), its not unthinkable for some of them to have both over the transition, but the "supported" one is always the binary that gets run if you use "cc" for compiler and nothing else. -- May the most significant bit of your life be positive.
