Hello can somebody help please? Server with out fqdn.
iked.conf:
ikev2 'local.pub' passive esp \
from 10.0.1.0/24 to 10.0.2.0/24 \
local 104.167.242.198 peer 24.80.177.18 \
srcid 104.167.242.198
ikev2 'local.pub' passive esp \
from any to dynamic \
local 104
Hi @misc
Today I was trying to delete EFI variables and got EPERM.
After some investigation I found at efi.c the below code
efiioc_var_set(struct efi_softc *sc, void *data)
...
if (securelevel > 0) {
error = EPERM;
goto leave;
}
So maybe a statement can be added to the securelevel(7) man page
s
I have a Samsung Galaxy Book4 Edge with a Snapdragon X Elite X1E84100
processor. The Bios configuration is controlled through the Aptio Setup
Utility. I'm trying to install OpenBSD 7.6 on the machine.
I completed the following steps using an install of OpenBSD 7.6 running in
VMware running on a
On Tue, Mar 04, 2025 at 09:59:31AM -0500, Kenneth Gober wrote:
> On Tue, Mar 4, 2025 at 3:27 AM Avon Robertson wrote:
>
> > The laptop concerned is a Dell M6600 circa 2011 that I have
> > owned since it was new. All internal components are original
> > including the 2 750Gb spinning disks.
> >
>
Thank you Stuart. See inline and below.
On Tue, Mar 04, 2025 at 10:32:41AM -, Stuart Henderson wrote:
> On 2025-03-04, Avon Robertson wrote:
> > On Tue, Mar 04, 2025 at 09:18:18AM +0100, Jan Stary wrote:
> >> > > wrdl5# fsck -t ffs /dev/sd1e
> >> > > ** /dev/rsd1e
> >> > >
> >> > > CANNOT R
On Tue, Mar 04, 2025 at 02:19:00PM +0100, Theo Buehler wrote:
> > Unfortunately I'm not an Emacs user and don't have time to dig into
> > this. If there is anything to do from the w3m side please make sure keep
> > me Cc'ed.
>
> It is definitely a problem in w3m, not directly OpenBSD related. It's
On Tue, Mar 4, 2025 at 3:27 AM Avon Robertson wrote:
> The laptop concerned is a Dell M6600 circa 2011 that I have
> owned since it was new. All internal components are original
> including the 2 750Gb spinning disks.
>
> Is the fsck failed partition recoverable, or should I assume
> the sd1 dis
On Tue, Mar 04, 2025 at 03:27:38PM +0100, Rene Kita wrote:
> On Tue, Mar 04, 2025 at 02:19:00PM +0100, Theo Buehler wrote:
> > > Unfortunately I'm not an Emacs user and don't have time to dig into
> > > this. If there is anything to do from the w3m side please make sure keep
> > > me Cc'ed.
> >
>
On Tue, Mar 04, 2025 at 11:55:02AM +, Stuart Henderson wrote:
> On 2025-03-04, Rene Kita wrote:
> > On Sat, Mar 01, 2025 at 07:34:31AM -0500, Jon Fineman wrote:
> >> I have been having some trouble with emacs/w3m for a while now.
> >>
> >> When I browse lobste.rs I get the below error message
> Unfortunately I'm not an Emacs user and don't have time to dig into
> this. If there is anything to do from the w3m side please make sure keep
> me Cc'ed.
It is definitely a problem in w3m, not directly OpenBSD related. It's
another instance of https://todo.sr.ht/~rkta/w3m/59
As mentioned by Je
On Tue, Mar 04, 2025 at 07:11:00AM -0500, John McCue wrote:
> On Sat, Mar 01, 2025 at 07:34:31AM -0500, Jon Fineman wrote:
> > I have been having some trouble with emacs/w3m for a while now.
> >
> > When I browse lobste.rs I get the below error message. Using the
> > command line w3m it works fine
Hi,
On Tue, Mar 04, 2025 at 11:55:02AM +, Stuart Henderson wrote:
> On 2025-03-04, Rene Kita wrote:
> > On Sat, Mar 01, 2025 at 07:34:31AM -0500, Jon Fineman wrote:
> >> I have been having some trouble with emacs/w3m for a while now.
> >>
> >> When I browse lobste.rs I get the below error
On Sat, Mar 01, 2025 at 07:34:31AM -0500, Jon Fineman wrote:
I have been having some trouble with emacs/w3m for a while now.
When I browse lobste.rs I get the below error message. Using the
command line w3m it works fine. duckduckgo.com and a few others also
fail.
This works on alpinelinux, so
On 2025-03-04, Rene Kita wrote:
> On Sat, Mar 01, 2025 at 07:34:31AM -0500, Jon Fineman wrote:
>> I have been having some trouble with emacs/w3m for a while now.
>>
>> When I browse lobste.rs I get the below error message. Using the
>> command line w3m it works fine. duckduckgo.com and a few othe
On 2025-03-04, Jan Stary wrote:
>
> A 2011 Dell will probably not even have slots for NVME,
I think the slots are miniPCIe rather than M.2. (Some laptops have
an M.2 slot typically meant for WWAN but in which you can sometimes use
an NVMe SSD, though they are usually quite short, 2230 or 2242 or
On 2025-03-04, Avon Robertson wrote:
> On Tue, Mar 04, 2025 at 09:18:18AM +0100, Jan Stary wrote:
>> > > wrdl5# fsck -t ffs /dev/sd1e
>> > > ** /dev/rsd1e
>> > >
>> > > CANNOT READ: BLK 128
>> > > CONTINUE? [Fyn] y
>> > >
>> > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 128, 129, 130, 131,
>
On Mar 04 22:47:19, avo...@xtra.co.nz wrote:
> Thank you Jan, see comments below.
>
> On Tue, Mar 04, 2025 at 09:18:18AM +0100, Jan Stary wrote:
> > To be sure: this is not "near the end of sysupgrade"
> > - the isntaller hasn't evene started upgrading anything,
> > as your filesystems can't even
Thank you Jan, see comments below.
On Tue, Mar 04, 2025 at 09:18:18AM +0100, Jan Stary wrote:
> To be sure: this is not "near the end of sysupgrade"
> - the isntaller hasn't evene started upgrading anything,
> as your filesystems can't even be mounted.
>
Very true Jan.
>
> On Mar 04 09:17:05, h
To be sure: this is not "near the end of sysupgrade"
- the isntaller hasn't evene started upgrading anything,
as your filesystems can't even be mounted.
On Mar 04 09:17:05, h...@stare.cz wrote:
> On Mar 04 20:57:04, avo...@xtra.co.nz wrote:
> > THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSIS
On Mar 04 20:57:04, avo...@xtra.co.nz wrote:
> THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY:
> ffs: fa50b3edace170b1.e (/var)
> Automatic file system check failed: help!
> Enter pathname of shell or RETURN for sh:
>
> wrdl5# fsck -t ffs /dev/sd1e
> ** /dev/rsd1e
>
> CANNOT READ
20 matches
Mail list logo
