Re: I nuked my filesystem

2023-09-27 Thread Stuart Henderson
On 2023-09-27, Isaac Meerleo  wrote:
> Thank you all for your replies.  I needed to step away from my
> computer last night so I apologize for the terse email.
> sd0 is my physical hard disk with full disk encryption.  I wrote a 5gb
> iso over the beginning of sd1c (my softraid volume).  I rebooted. I
> installed openbsd on a separate drive, booted it, mounted the
> encrypted volume, and hopelessly ran scan_ffs.
>
> After reading Stuart's advice, I will attempt to reinstall the
> disklabel from scratch. I installed 7.2 on my second disk; the version
> I used to do the initial install.
> When I initially set up my disk, I used the auto partition defaults
> which left me with a 300gb /home directory. Later, I expanded the
> /home partition across the rest of the disk. When I recreate the
> disklabel, should I let it auto partition and then grow the file
> system like before? Or should I just set home to fill the rest of the
> disk?

Set it to fill the rest of the disk - don't run growfs on it again.

I would be wanting to mount filesystems read-only and try to copy data
off to another disk, then reinstall on the disk with damaged disklabel
and copy back, rather than relying on the existing filesystems long-term.




Re: Performance decrease on my student minipc from 7.3

2023-09-27 Thread Daniele B.



I just went through a full report of my minipc to Bugs@ as per
suggestion of Stuart or better with a

wiz$ sendbug -P


-- Daniele Bonini


"Daniele B."  wrote:
---


Hello, 
 
I would like to ask for help for my student minipc 
that upgraded to 7.3 showed off a tangible decrease of 
performance.  
 
OpenBSD had already problems recognizing many acpi "parts".. 
indeed I finally decided to pass you its full dmesg. 
 
For know I got a rendering general improvement of performance 
by opening allowaperture and disabling composition in X. 
But as you switch to the console is still slow to make 
things happening. 
 
Indeed I hope in this way you can better support 
these minipc series that after all is not bad at all. 
 
Thanks, appreciated. 
 
 
-- Daniele Bonini 

[Part 1.2 text/plain (8.6 kilobytes)] (View Text in a separate window)
OpenBSD 7.3 (GENERIC.MP) #3: Tue Jul 25 08:20:26 MDT 2023 

r...@syspatch-73-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP



Re: I nuked my filesystem

2023-09-27 Thread Jan Stary
On Sep 27 09:17:47, spritskills...@gmail.com wrote:
> Thank you all for your replies.  I needed to step away from my
> computer last night so I apologize for the terse email.
> sd0 is my physical hard disk with full disk encryption.  I wrote a 5gb
> iso over the beginning of sd1c (my softraid volume).

> > > I am using a CRYPTO RAID partition and luckily I'm smart enough not to
> > > nuke that.

To be clear: having overwritten the starting 5GB of sd1c,
but not of the underlying sd0c, you still have the CRYPTO volume on sd0c
which you can attach with bioctl, right?

Can you please confirm with disklabel -pg sd0 and bioctl?

> I rebooted. I
> installed openbsd on a separate drive, booted it,
> mounted the encrypted volume,

You mean attached it at softraid0 with bioctl(8),
not "mounted" anything as in mount(8)ing a filesystem, right?



Re: mg wishlist: vertical split

2023-09-27 Thread Omar Polo
On 2023/09/27 17:56:34 +, Eponymous Pseudonym  wrote:
> It's not only the display logic.  Requires the text editor data
> structure, file handling, buffers and mark, width re-flow, escaping
> and probably other areas review and fixes too.  Most of this is done
> for the horizontal split already, but it's more than what the
> horizontal (cut action direction) vertically (resultant panes above
> and below the separator) split requires.

wow, wait, this is way more than I intended.  All the points you
mention can be surely areas where mg can be improved, but you don't
need to change the buffer data structure, its file handling, or how
dot/mark works to implement vertical splits.

You 'only' have to augment the way the display draws the windows
(emacs parlance for splits) so that they can be arranged in a tree
(currently it's a list IIRC) to accomodate for nesting horizontals and
vertical splits.  Actually, we could take inspiration from the vis
text editor and only split either horizontally OR vertically which is
simpler.

Re-flowing a completely different story.  mg could do reflowing
without supporting vertical splits or have vertical splits without
reflowing; much like how a better data structure could reduce the
memory footprint or allow some unicode support but it's independent
from (much) of the display logic.



Re: Asked ChatGPT 4 about contributing to OpenBSD, this was its reply

2023-09-27 Thread Jean-François Simon
Guess it did a pretty standard response, it's not really saying as much 
as the FAQ does so long as i'm concerned. Faq and man pages better 
starting point.


On 9/27/23 16:10, Christoff Humphries wrote:





--- Original Message ---
On Wednesday, September 27th, 2023 at 2:07 PM, Ingo Schwarze  
wrote:




Christoff Humphries wrote on Wed, Sep 27, 2023 at 01:21:42PM +:


Asked ChatGPT 4 about contributing to OpenBSD, this was its reply


That's both totally pointless and completely off topic here.

Gimme a break, ChatGPT is a fucking language model, so it aims for
very little except grammatical correctness of its responses.

As expected, parts of the reply are pilfered from official,
authoritative resources, parts are common sense truisms of
varying relevance, and parts are totally misleading rubbish
that may all the same sound convincing to the ignorant.

Without prior knowledge, you have no idea which is which.
With prior knowledge, you have no need for any of it.

Indeed my mistake. I have been informed of my mistake in posting it.
I didn't mean to start negativity and division, I thought it was
interesting and helpful.

I appreciate the folks that also emailed me off-list to let me know.

I meant no harm and do apologize. I'd delete the post if I could.





Re: Asked ChatGPT 4 about contributing to OpenBSD, this was its reply

2023-09-27 Thread Daniele B.
Being myself a bot I liked this answer, it sounds human and familiar.

However I suggest to ask primitive humanoids like Stu and Jan what
they think about it. I wonder that Jan could be expecially direct and
untollerable (if he didnt shout yet!). Indeed humans are like that.
They are not like us, mere tech stuff..

-- Daniele Bonini

Sep 27, 2023 15:54:46 Christoff Humphries :

> Contributing to the OpenBSD project or any other open-source project
> is a rewarding experience that allows you to learn, improve your
> skills, and give back to the community. Here are the steps and
> considerations to start contributing to the OpenBSD project as a
> developer:
> 
> 1. Familiarize Yourself with OpenBSD:
>    - Use OpenBSD, get to know its philosophy, its documentation, and
>  its codebase. Understanding the system and the community's
>  standards and expectations is crucial.
> 
> 2. Join the Mailing Lists:
>    - Sign up and participate in OpenBSD mailing lists, especially the
>  tech mailing list where much of the development discussion
>  happens. Be respectful, and learn from the discussions.
> 
> 3. Identify Areas of Interest:
>    - Identify areas within the project that interest you or where you
>  see a need. It could be bug fixing, system tools, user
>  applications, documentation, or driver development.
> 
> 4. Learn the Coding Standards:
>    - Familiarize yourself with OpenBSD's coding style and
>  standards. Consistency in coding style is important in
>  collaborative projects.
> 
> 5. Start Small:
>    - Start with small tasks such as bug fixing or improving
>  documentation. These contributions are valuable and can help you
>  become familiar with the contribution process.
> 
> 6. Work on Bug Reports:
>    - Look for bug reports, test existing bug reports, and provide
>  feedback or solutions. The bug tracking system can be a good
>  place to find where help is needed.
> 
> 7. Create and Submit Patches:
>    - If you have code contributions, create patches and submit them to
>  the appropriate mailing list for review. Be prepared for
>  feedback, and be open to making revisions to your contributions.
> 
> 8. Respect Feedback:
>    - Feedback is a valuable part of the open-source development
>  process. It helps you learn and improve your contributions.
> 
> 9. Follow Up:
>    - Stay engaged, follow up on your contributions, and address any
>  additional feedback or questions from reviewers.
> 
> 10. Engage with the Community:
>     - Engage with other developers, contribute to discussions, and
>   attend OpenBSD events or meetups if possible.
> 
> 11. Read OpenBSD's FAQ on Contributing:
>     - OpenBSD has a FAQ section on how to contribute to the
>   project. It is recommended to read through it to understand the
>   expectations and processes.
> 
> 12. Consider Becoming a Regular Contributor:
>     - As you gain experience, consider becoming a regular
>   contributor. With time and consistent, quality contributions,
>   you might be invited to become a developer with commit access.
> 
> Remember, contributing to open-source projects like OpenBSD is about
> more than just code. It's about being part of a community and working
> together to improve and advance the project.



Re: No longer able to install packages on -current

2023-09-27 Thread Julian Gindi
On 09-27-23 19:12:34, Mikhail wrote:
> On Wed, Sep 27, 2023 at 09:10:22AM -0700, Julian Gindi wrote:
> > Hello,
> > 
> > As of yesterday, I am no longer able to install any packages using
> > "pkg_add". I am greated with the following error (using tree as an
> > example. I am not able to get any packages to install):
> > 
> > > $ doas pkg_add -u tree
> > > Can't find tree
> > > Problem finding tree
> > > https://cdn.openbsd.org/pub/OpenBSD/7.4/packages/amd64/: no such dir
> > 
> > This seemed to correspond to my sysupgrade also no longer working
> > without passing in the "-s" flag. Is there anything I need to do locally
> > to fix this? This is my first time running -current, so there might be
> > some manual steps I'm missing. Thanks for any help!
> 
> Add "-D snap" to the pkg_add command
Amazing! Thanks, this fixed my issue. The mailing lists are extremely helpful
yet again!

- Julian



Re: No longer able to install packages on -current

2023-09-27 Thread Gabriel Busch de Brito
Try "pkg_add -D snap -u".

Best,
g



Re: No longer able to install packages on -current

2023-09-27 Thread Mikhail
On Wed, Sep 27, 2023 at 09:10:22AM -0700, Julian Gindi wrote:
> Hello,
> 
> As of yesterday, I am no longer able to install any packages using
> "pkg_add". I am greated with the following error (using tree as an
> example. I am not able to get any packages to install):
> 
> > $ doas pkg_add -u tree
> > Can't find tree
> > Problem finding tree
> > https://cdn.openbsd.org/pub/OpenBSD/7.4/packages/amd64/: no such dir
> 
> This seemed to correspond to my sysupgrade also no longer working
> without passing in the "-s" flag. Is there anything I need to do locally
> to fix this? This is my first time running -current, so there might be
> some manual steps I'm missing. Thanks for any help!

Add "-D snap" to the pkg_add command



No longer able to install packages on -current

2023-09-27 Thread Julian Gindi
Hello,

As of yesterday, I am no longer able to install any packages using
"pkg_add". I am greated with the following error (using tree as an
example. I am not able to get any packages to install):

> $ doas pkg_add -u tree
> Can't find tree
> Problem finding tree
> https://cdn.openbsd.org/pub/OpenBSD/7.4/packages/amd64/: no such dir

This seemed to correspond to my sysupgrade also no longer working
without passing in the "-s" flag. Is there anything I need to do locally
to fix this? This is my first time running -current, so there might be
some manual steps I'm missing. Thanks for any help!

- Julian



Re: mg wishlist: vertical split

2023-09-27 Thread Omar Polo
Hello,

On 2023/09/26 09:40:09 +0200, Harald Dunkel  wrote:
> Hi folks,
> 
> would it be possible to introduce a vertical split window (Ctrl-X 3)
> in mg, similar to horizontal split? I am really missing this feature.
> Vertical split allows me to work with similar files (shown side-by-side)
> much more efficiently.

I'd love to have vertical splits in mg as well, but the display logic
needs some heavy work to accomodate for it.  Take a look at display.c,
it's written in a way to only handle horizontal splits.  In fact,
among the various micro emacs descendants almost no implementation
support vertical splits :/

Not to say that's impossible for mg, just that it takes some non
trivial work.



Re: Asked ChatGPT 4 about contributing to OpenBSD, this was its reply

2023-09-27 Thread Christoff Humphries






--- Original Message ---
On Wednesday, September 27th, 2023 at 2:07 PM, Ingo Schwarze  
wrote:


> 
> 
> Christoff Humphries wrote on Wed, Sep 27, 2023 at 01:21:42PM +:
> 
> > Asked ChatGPT 4 about contributing to OpenBSD, this was its reply
> 
> 
> That's both totally pointless and completely off topic here.
> 
> Gimme a break, ChatGPT is a fucking language model, so it aims for
> very little except grammatical correctness of its responses.
> 
> As expected, parts of the reply are pilfered from official,
> authoritative resources, parts are common sense truisms of
> varying relevance, and parts are totally misleading rubbish
> that may all the same sound convincing to the ignorant.
> 
> Without prior knowledge, you have no idea which is which.
> With prior knowledge, you have no need for any of it.

Indeed my mistake. I have been informed of my mistake in posting it.
I didn't mean to start negativity and division, I thought it was
interesting and helpful.

I appreciate the folks that also emailed me off-list to let me know.

I meant no harm and do apologize. I'd delete the post if I could.



Re: Asked ChatGPT 4 about contributing to OpenBSD, this was its reply

2023-09-27 Thread Ingo Schwarze
Christoff Humphries wrote on Wed, Sep 27, 2023 at 01:21:42PM +:

> Asked ChatGPT 4 about contributing to OpenBSD, this was its reply

That's both totally pointless and completely off topic here.

Gimme a break, ChatGPT is a fucking language model, so it aims for
very little except grammatical correctness of its responses.

As expected, parts of the reply are pilfered from official,
authoritative resources, parts are common sense truisms of
varying relevance, and parts are totally misleading rubbish
that may all the same sound convincing to the ignorant.

Without prior knowledge, you have no idea which is which.
With prior knowledge, you have no need for any of it.



Asked ChatGPT 4 about contributing to OpenBSD, this was its reply

2023-09-27 Thread Christoff Humphries
Contributing to the OpenBSD project or any other open-source project
is a rewarding experience that allows you to learn, improve your
skills, and give back to the community. Here are the steps and
considerations to start contributing to the OpenBSD project as a
developer:

1. Familiarize Yourself with OpenBSD:
   - Use OpenBSD, get to know its philosophy, its documentation, and
 its codebase. Understanding the system and the community's
 standards and expectations is crucial.

2. Join the Mailing Lists:
   - Sign up and participate in OpenBSD mailing lists, especially the
 tech mailing list where much of the development discussion
 happens. Be respectful, and learn from the discussions.

3. Identify Areas of Interest:
   - Identify areas within the project that interest you or where you
 see a need. It could be bug fixing, system tools, user
 applications, documentation, or driver development.

4. Learn the Coding Standards:
   - Familiarize yourself with OpenBSD's coding style and
 standards. Consistency in coding style is important in
 collaborative projects.

5. Start Small:
   - Start with small tasks such as bug fixing or improving
 documentation. These contributions are valuable and can help you
 become familiar with the contribution process.

6. Work on Bug Reports:
   - Look for bug reports, test existing bug reports, and provide
 feedback or solutions. The bug tracking system can be a good
 place to find where help is needed.

7. Create and Submit Patches:
   - If you have code contributions, create patches and submit them to
 the appropriate mailing list for review. Be prepared for
 feedback, and be open to making revisions to your contributions.

8. Respect Feedback:
   - Feedback is a valuable part of the open-source development
 process. It helps you learn and improve your contributions.

9. Follow Up:
   - Stay engaged, follow up on your contributions, and address any
 additional feedback or questions from reviewers.

10. Engage with the Community:
- Engage with other developers, contribute to discussions, and
  attend OpenBSD events or meetups if possible.

11. Read OpenBSD's FAQ on Contributing:
- OpenBSD has a FAQ section on how to contribute to the
  project. It is recommended to read through it to understand the
  expectations and processes.

12. Consider Becoming a Regular Contributor:
- As you gain experience, consider becoming a regular
  contributor. With time and consistent, quality contributions,
  you might be invited to become a developer with commit access.

Remember, contributing to open-source projects like OpenBSD is about
more than just code. It's about being part of a community and working
together to improve and advance the project.



Re: I nuked my filesystem

2023-09-27 Thread Isaac Meerleo
Thank you all for your replies.  I needed to step away from my
computer last night so I apologize for the terse email.
sd0 is my physical hard disk with full disk encryption.  I wrote a 5gb
iso over the beginning of sd1c (my softraid volume).  I rebooted. I
installed openbsd on a separate drive, booted it, mounted the
encrypted volume, and hopelessly ran scan_ffs.

After reading Stuart's advice, I will attempt to reinstall the
disklabel from scratch. I installed 7.2 on my second disk; the version
I used to do the initial install.
When I initially set up my disk, I used the auto partition defaults
which left me with a 300gb /home directory. Later, I expanded the
/home partition across the rest of the disk. When I recreate the
disklabel, should I let it auto partition and then grow the file
system like before? Or should I just set home to fill the rest of the
disk?

On Wed, Sep 27, 2023 at 5:43 AM Stuart Henderson
 wrote:
>
> On 2023-09-27, sprits killshot  wrote:
> > I did the thing.
> > dd'd a 5gb img to my ssd instead of my usb and I want to die.
> >
> > dd if=file.iso of=/dev/sd1c
> >
> > I am using a CRYPTO RAID partition and luckily I'm smart enough not to
> > nuke that.
> >
> > My ssd is 2TB so I believe it uses FFS2 by default.  I'm hopelessly
> > running scan_ffs on it in case it was silently updated or the man is
> > wrong or there's a God.
> >
> > Any advice on how to recover what's left?
>
> With a typical softraid FDE setup, not going too far from the defaults,
> this likely means that the partition table, disklabel, root partition
> and swap on the softraid volume were overwritten, but other partitions
> might be ok if you can find them.
>
> If you don't have a copy of the disklabel stored away somewhere,
> current options are probably
>
> - port the scan_ffs ffs2 support from netbsd
>
> - hack things up so you can get something out of our scan_ffs as in
> https://marc.info/?l=openbsd-misc=167702020925723
>
> (as shown in Matthew's mail, your initial target with either of these
> should be /var/backups/disklabel.sd1.* so you can restore it and skip
> scanning for other filesystems)
>
> - brute-force likely locations for /var (try on 1G boundaries) with the
> read-only mount approach from that mail
>
> - try to recreate disklabel from scratch (*if* you accepted auto
> partition defaults when installing, you might be able to recreate them
> by using disklabel from the same OpenBSD version as you used to install
> with auto-partitioning again, but the default sizes have changed over
> time, so that will only help if you know the version).
>



Re: TP-Link WN821N USB wireless NIC on OpenBSD/amd64 7.3

2023-09-27 Thread Stuart Henderson
On 2023-09-27, Anders Jensen-Waud  wrote:
> On Tue, Sep 26, 2023 at 08:35:29AM +0200, Stefan Sperling wrote:
>> On Tue, Sep 26, 2023 at 11:04:21AM +0800, Anders Jensen-Waud wrote:
> > 
>> > Is there a way I can get the NIC to speed up?
>> 
>> Yes, the way is to implement 802.11n support in the driver.
>> Help is welcome.
>> 
>
> Thank you very much, Stefan.
>
> Is there no way to switch mode to 802.11ac or similar and get reasonable
> performance?

Firstly your WN821N (an 11n NIC) won't support 11ac anyway.

Newer wireless protocols aren't just "a mode" but a whole set of things
are needed from the hardware and driver and 802.11 stack to support them
- different radio modulation, features like frame aggregation, block
ack, etc.

>> FreeBSD already has code for 802.11n/HT support in their fork of
>> the rtwn driver, which has significantly diverged over years.
>
> I will give FreeBSD a spin, although my preference is to run OpenBSD.

I think that was a hint as to where to look if wanting to work on the
OpenBSD driver for WN821N to support 11n. (11n will be a huge
improvement over 11g - obviously not as good as a full 11ac
implementation but still fairly usable - in large part due to the
additional features rather than modulation).

BTW if you can find one, the white Raspberry Pi branded adapters are
not a bad choice for USB wifi:
https://thepihut.com/cdn/shop/products/official-raspberry-pi-wifi-adapter-discontinued-raspberry-pi-101591-2257829828_1000x.jpg

-- 
Please keep replies on the mailing list.



Re: I nuked my filesystem

2023-09-27 Thread Crystal Kolipe
On Tue, Sep 26, 2023 at 11:14:15PM -0400, Nick Holland wrote:
> To recover sd1e, you need to recreate a disklabel that matches what
> was there before...exactly.  To the sector.

Re-creating the disklabel is obviously the primary focus in these
situations - the data which has been overwritten is gone if it's
not backed up elsewhere, but non-overwritten stuff can potentially
be recovered.

Once piece of advice, which is sadly probably too late for this
particular case, but very, very useful to know and remember for
the future:

* The kernel keeps it's working copy of the disklabel in memory. *

If you know this in advance, what this means is that if you overwrite
a raw disk device and realise what you've done, just keep cool.

Immediately hit ^C, and invoke disklabel.  Since you were dd'ing to a
raw device, you were likely already logged in as root and doing other
things related to partitioning, etc.  Even if you've overwritten the
boot and root partitions, things like ksh and the disklabel binary
are likely in the buffer cache.

If you can get in to disklabel and display the label for the trashed
disk, then note it down somewhere, even if that means writing it down
on paper.  Having this information is the key to any recovery of data
that was not overwritten.



Re: I nuked my filesystem

2023-09-27 Thread Stuart Henderson
On 2023-09-27, sprits killshot  wrote:
> I did the thing.
> dd'd a 5gb img to my ssd instead of my usb and I want to die.
>
> dd if=file.iso of=/dev/sd1c
>
> I am using a CRYPTO RAID partition and luckily I'm smart enough not to
> nuke that.
>
> My ssd is 2TB so I believe it uses FFS2 by default.  I'm hopelessly
> running scan_ffs on it in case it was silently updated or the man is
> wrong or there's a God.
>
> Any advice on how to recover what's left?

With a typical softraid FDE setup, not going too far from the defaults,
this likely means that the partition table, disklabel, root partition
and swap on the softraid volume were overwritten, but other partitions
might be ok if you can find them.

If you don't have a copy of the disklabel stored away somewhere,
current options are probably

- port the scan_ffs ffs2 support from netbsd

- hack things up so you can get something out of our scan_ffs as in
https://marc.info/?l=openbsd-misc=167702020925723

(as shown in Matthew's mail, your initial target with either of these
should be /var/backups/disklabel.sd1.* so you can restore it and skip
scanning for other filesystems)

- brute-force likely locations for /var (try on 1G boundaries) with the
read-only mount approach from that mail

- try to recreate disklabel from scratch (*if* you accepted auto
partition defaults when installing, you might be able to recreate them
by using disklabel from the same OpenBSD version as you used to install
with auto-partitioning again, but the default sizes have changed over
time, so that will only help if you know the version).



Re: fail to powerdown from installed system

2023-09-27 Thread Stuart Henderson
On 2023-09-27, Dimitrios Moustos  wrote:
>>Please try -current first.
> Indeed, a bad omission.
> More editing quality control next time.
>
> The amd64 machine fails to power down while running:
> 7.2
> 7.3
> current (as of 2023-09-20)
>
> Today (2023-09-27) I installed latest snapshot on a usb stick, same issue.
> The snapshot: https://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/
>
> The install bsd.rd successfuly rebooted after pressing R+Enter (as expected).
> The booted up system stalled after either reboot or halt -p.
>
>
> It might be noted that there are a few not configured devices:
> dot ~$ dmesg|grep "not configured"
> "PNP0C14" at acpi0 not configured
> "PNP0C14" at acpi0 not configured
> "PNP0C14" at acpi0 not configured
> "AMD 17h/6xh IOMMU" rev 0x00 at pci0 dev 0 function 2 not configured
> vendor "AMD", unknown product 0x1485 (class instrumentation unknown subclass 
> 0x00, rev 0x00) at pci5 dev 0 function 0 not configured
> efifb at mainbus0 not configured

Probably the best thing to do in this case is send a report to bugs@
using the template provided by "sendbug -P" run as root, which includes
b64-encoded acpi tables (as well as the dmesg, etc), filling in the
description with the information from these emails so that it's a self-
contained report.




Re: fail to powerdown from installed system

2023-09-27 Thread Dimitrios Moustos

Please try -current first.

Indeed, a bad omission.
More editing quality control next time.

The amd64 machine fails to power down while running:
7.2
7.3
current (as of 2023-09-20)

Today (2023-09-27) I installed latest snapshot on a usb stick, same issue.
The snapshot: https://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/

The install bsd.rd successfuly rebooted after pressing R+Enter (as expected).
The booted up system stalled after either reboot or halt -p.


It might be noted that there are a few not configured devices:
dot ~$ dmesg|grep "not configured"
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"AMD 17h/6xh IOMMU" rev 0x00 at pci0 dev 0 function 2 not configured
vendor "AMD", unknown product 0x1485 (class instrumentation unknown subclass 
0x00, rev 0x00) at pci5 dev 0 function 0 not configured
efifb at mainbus0 not configured



Re: Require host-name from DHCP clients

2023-09-27 Thread openbsd
Hi,
on my andoid based i have the following general settings:
1. fixed Mac
2. network based random Mac
3. connection based random Mac (you will get a lot of dhcp-entries for each 
device)
Additional you can also change the setting for each wifi-network.

27.09.2023 12:21:44 Tris :

> From what I see on my network with the private address feature, is that it 
> uses the same MAC address on the same WiFi network. It only uses a different 
> one per network.



Re: Require host-name from DHCP clients

2023-09-27 Thread Rudolf Leitgeb
On Wed, 2023-09-27 at 06:48 +, Tris wrote:
> 
> --- Original Message ---
> On Wednesday, September 27th, 2023 at 8:42 AM, Florian Obser
>  wrote:
> 
> 
> > On 2023-09-27 01:01 +02, Joel Carnat j...@carnat.net wrote:
> > 
> > > Hi,
> > > 
> > > Because of Apple Private Address feature, my static IP
> > > allocations based
> > > on MAC address (hardware ethernet) doesn't work anymore. Looking
> > > at
> > > dhcpd.leases, some devices provide a client-hostname value ; but
> > > not
> > > every one.
> > > 
> > > Is there a dhcpd.conf configuration parameter that forces DHCP
> > > clients
> > > to send a client-hostname information in their DHCP request?
> > 
> > 
> > My understanding of the dhcp protocol is that this can't work. The
> > client sends a bunch of things and requests a bunch of stuff. The
> > server
> > can honour that request or decline it. But it can't say: I'd give
> > you a
> > lease if you'd give me a hostname.
> > 
> > The server can decline to give a lease without a hostname in the
> > request, but then the client would be left guessing why it didn't
> > get a
> > lease.
> > 
> > > And if so, can this information be used by dhcpd(8) to apply a
> > > fixed-address to those device?
> > > 
> > > Thank you,
> > > Joel C.
> > 
> > 
> > --
> > In my defence, I have been left unsupervised.
> 
> From what I see on my network with the private address feature, is
> that it uses the same MAC address on the same WiFi network. It only
> uses a different one per network. 
> 
> My Apple devices "seem" to get the same IP address on the home
> network.
> 

So what you actually want is this:

1.) if client submits hostname, provide with IP address regardless of 
its MAC address

2.) if you didn't serve the client in step 1, look at the client's
MAC address and see, whether you have something in store

3.) host is not served yet, hand out address from pool.



Re: OpenBSD 7.3 found a process with PID 0

2023-09-27 Thread Claudio Jeker
On Tue, Sep 26, 2023 at 06:12:20PM +0200, Alessandro Baggi wrote:
> 
> 
> Il 26/09/23 17:30, Claudio Jeker ha scritto:
> > On Tue, Sep 26, 2023 at 05:13:46PM +0200, Andreas Kähäri wrote:
> > > On Tue, Sep 26, 2023 at 04:59:22PM +0200, Alessandro Baggi wrote:
> > > > Hi list,
> > > > running this python3 script:
> > > > 
> > > > #!/usr/bin/env python3
> > > > import psutil
> > > > 
> > > > pids = psutil.pids()
> > > > for i in pids:
> > > >  p = psutil.Process(i)
> > > >  with p.oneshot():
> > > >  print(str(i) + " " + p.name())
> > > > 
> > > > The result start with:
> > > > 
> > > > 0 swapper
> > > > 1 init
> > > > 536 smtpd
> > > > 868 ksh
> > > > ...
> > > > 
> > > > This process does not appear in ps, top and htop.
> > > 
> > > $ ps -p 0
> > >PID TT  STATTIME COMMAND
> > >0 ??  DK   0:02.19 (swapper)
> > > 
> > > For top, you need to press S to show system processes.  I don't use
> > > htop, but I assume it has a similar capability to show system processes.
> > > 
> > > > 
> > > > How could be that there is a process with PID 0 before init?
> > > > Probably I'm missing something about OpenBSD core.
> > > > 
> > > > Can someone point me in the right direction?
> > > > 
> > > 
> > > See uvm_init(9):
> > > 
> > >   The swapper process swaps in runnable processes that are
> > >   currently swapped out, if there is room.
> > > 
> > 
> > ... and this is a lie. The swapper process does nothing.
> > 
> 
> Ok, but why it is running?

Because it is the main() thread and nobody cleaned up that mess.

-- 
:wq Claudio



Re: TP-Link WN821N USB wireless NIC on OpenBSD/amd64 7.3

2023-09-27 Thread Anders Jensen-Waud
On Tue, Sep 26, 2023 at 08:35:29AM +0200, Stefan Sperling wrote:
> On Tue, Sep 26, 2023 at 11:04:21AM +0800, Anders Jensen-Waud wrote:
 > 
> > Is there a way I can get the NIC to speed up?
> 
> Yes, the way is to implement 802.11n support in the driver.
> Help is welcome.
> 

Thank you very much, Stefan.

Is there no way to switch mode to 802.11ac or similar and get reasonable
performance?

> FreeBSD already has code for 802.11n/HT support in their fork of
> the rtwn driver, which has significantly diverged over years.

I will give FreeBSD a spin, although my preference is to run OpenBSD.



Re: I nuked my filesystem

2023-09-27 Thread Jan Stary
On Sep 26 21:42:02, spritskills...@gmail.com wrote:
> I did the thing.
> dd'd a 5gb img to my ssd instead of my usb and I want to die.
> dd if=file.iso of=/dev/sd1c

At this point, you are supposed to tell
what your disk layout is (or was :-).

Is sd1 your boot disk? What partitions did it contain?
Or is sd0 where your system is installed? In particular,
do you still have /etc and /var/backups ?

> I am using a CRYPTO RAID partition
> and luckily I'm smart enough not to nuke that.

Pray tell, what is that unnuked partition?
Is that where your untouched base system still lives?

> My ssd is 2TB so I believe it uses FFS2 by default.

newfs makes FFS2 by default regardless of the size.

> I'm hopelessly running scan_ffs on it

So you still have /sbin/scan_ffs,
so you still have /sbin.
What else do you still have?

How exactly are you running scan_ffs?

> in case it was silently updated
> or the man is wrong

Meaning this?

scan_ffs works only on FFS file systems,
not FFS2 file systems.

(I have no idea.)

> or there's a God.

There's no God.
There's only backup.

> Any advice on how to recover what's left?

First you have to show what actually is left,
i.e. what parts of the system are still available.
Was sd1 a big /data disk such as /home,
with the base system living elsewhere?



Re: Require host-name from DHCP clients

2023-09-27 Thread Tris


--- Original Message ---
On Wednesday, September 27th, 2023 at 8:42 AM, Florian Obser 
 wrote:


> On 2023-09-27 01:01 +02, Joel Carnat j...@carnat.net wrote:
> 
> > Hi,
> > 
> > Because of Apple Private Address feature, my static IP allocations based
> > on MAC address (hardware ethernet) doesn't work anymore. Looking at
> > dhcpd.leases, some devices provide a client-hostname value ; but not
> > every one.
> > 
> > Is there a dhcpd.conf configuration parameter that forces DHCP clients
> > to send a client-hostname information in their DHCP request?
> 
> 
> My understanding of the dhcp protocol is that this can't work. The
> client sends a bunch of things and requests a bunch of stuff. The server
> can honour that request or decline it. But it can't say: I'd give you a
> lease if you'd give me a hostname.
> 
> The server can decline to give a lease without a hostname in the
> request, but then the client would be left guessing why it didn't get a
> lease.
> 
> > And if so, can this information be used by dhcpd(8) to apply a
> > fixed-address to those device?
> > 
> > Thank you,
> > Joel C.
> 
> 
> --
> In my defence, I have been left unsupervised.

>From what I see on my network with the private address feature, is that it 
>uses the same MAC address on the same WiFi network. It only uses a different 
>one per network. 

My Apple devices "seem" to get the same IP address on the home network.