Re: use pfctl to reread /etc/mail/spamd-white table
On Fri, Oct 29, 2021 at 09:49:43AM +0200, Peter N. M. Hansteen wrote: > > How do you maintain the contents of the /etc/mail/spamd-white file? > > As in, do you have a cron job or similar that dumps the contents of the > table there? > This little tidbit of necessary information is not really mentioned anywhere. (Forgive the noise if that has changed) My assumption years ago was that pf would update the files itself. Obviously, I didn't realize that for a while. Neither did my files. -- Chris Bennett
Re: Dhcp client configuration in 7.0
On Fri, Oct 29, 2021 at 09:57:26PM +0300, Samarul Meu wrote:
> On Fri, Oct 29, 2021 at 8:30 PM Zé Loff wrote:
>
> > This works for me:
> >
> >
> > /etc/hostname.em0:
> >
> > inet autoconf
> >
> >
> > /etc/resolv.conf:
> >
> > nameserver 127.0.0.1
> >
> >
> > /etc/dhcpleased.conf:
> >
> > interface em0 {
> > ignore dns
> > }
> >
> >
> My dhcpleased.conf is similar (interface urtwn0 ignore dns), but it does
> not seem to work. resolvd just overwrites the resolv.conf with the ISP DNS.
> If I disable resolvd and I leave only nameserver 127.0.0.1 the unbound
> works as expected.
>
> Now, my question is when ignore dns from dhcpleased.conf is considered? The
> man page states "Ignore nameservers from leases on this interface" but
> maybe I am not reading it correctly?
Is that the exact contents of your dhcpleased.conf? Reading the man
page, it seems that the curly brackets are mandatory, and if I change my
config to "interface em0 ignore dns" dhcpleased warns about the syntax
error (and doesn't start).
--
Re: Audio codec support for new(er) Framework laptops?
Thank you! :) On October 29, 2021 4:31:29 AM CDT, Alexandre Ratchov wrote: >On Fri, Oct 29, 2021 at 09:13:57AM +, aval...@posteo.net wrote: >> Hi Misc! >> >> Does anyone know whether the Tempo 92HD95B audio codec is supported? >> >> https://temposemi.com/products/pclaptop-hd/92hd95/ >> >> I'm considering getting the Framework laptop and Joshua Stein's >website >> indicates that at this point, it's pretty well supported >> >> https://jcs.org/2021/08/06/framework >> >> But Framework is changing audio codecs on their next batches of >> machines. >> >> https://frame.work/blog/solving-for-silicon-shortages >> >> Thus far, I haven't been able to find a way to check whether the new >> audio chip is supported, as "fully supported in both Windows and >Linux" >> doesn't actually say much, and Tempo's answer to "how do I get a >driver" >> is "Ask our OEM partner that actually made the computer in question" >> >> I *have* identified that the chip is compatible with Intel's HD audio >> interface, so from what I'm reading in azalia's man page, I think it >> *should* have support already under azalia, but I'll admit, the >> technical specs go a bit over my head. >> >> If anyone can clarify this for me, I'd really appreciate it. >> > >Short answer: virtually any HDA codec is supported and there are good >chances that sound will just work on this laptop. > >Long answer: The HDA spec. allows the driver (i.e. azalia(4)) to >control all HDA-compatible codecs in a uniform way, so any past or >future codec is supposed to just work with the current driver, >provided the codec is HDA compatible. > >There are rare hardware bugs or "creative" ways of connecting the >codec to the HDA host that cause problems, most of them are handled by >quirks in the azalia(4) driver. > >There are few laptops that have HDA codecs that require firmware to >make advanced features work. Certain recent laptops come with >microphones that are not physically connected to the HDA codec >(instead they use a secondary audio device OpenBSD doesn't support >yet). -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: Dhcp client configuration in 7.0
On Fri, Oct 29, 2021 at 8:30 PM Zé Loff wrote:
> This works for me:
>
>
> /etc/hostname.em0:
>
> inet autoconf
>
>
> /etc/resolv.conf:
>
> nameserver 127.0.0.1
>
>
> /etc/dhcpleased.conf:
>
> interface em0 {
> ignore dns
> }
>
>
My dhcpleased.conf is similar (interface urtwn0 ignore dns), but it does
not seem to work. resolvd just overwrites the resolv.conf with the ISP DNS.
If I disable resolvd and I leave only nameserver 127.0.0.1 the unbound
works as expected.
Now, my question is when ignore dns from dhcpleased.conf is considered? The
man page states "Ignore nameservers from leases on this interface" but
maybe I am not reading it correctly?
Re: Dhcp client configuration in 7.0
On Fri, Oct 29, 2021 at 03:37:56PM +0300, Samarul Meu wrote:
> Hello to you all!
>
> Prior to 7.0 I was using this line in /etc/dhclient.conf
> supersede domain-name-servers 127.0.0.1;
> so that I do not get the DNS from the ISP provider.
>
> I am using unbound to resolve my queries. With the new changes I can not
> get the same functionality.
>
> I tried to add this in /etc/dhcpleased.conf
> interface urtwn0 ignore dns
> where urtwn0 is my interface or disable resolvd.
>
> If resolvd is on I get my ISP DNS server, if not when unbound starts
> resolvd adds the ISP DNS server to resolv.conf.
>
> Can you please tell me what am I doing wrong and how can I have only
> 127.0.0.1 on the resolv.conf file?
>
> Thank you!
This works for me:
/etc/hostname.em0:
inet autoconf
/etc/resolv.conf:
nameserver 127.0.0.1
/etc/dhcpleased.conf:
interface em0 {
ignore dns
}
--
Re: Dhcp client configuration in 7.0
On Fri, Oct 29, 2021 at 03:37:56PM +0300, Samarul Meu wrote: > Hello to you all! > > Prior to 7.0 I was using this line in /etc/dhclient.conf > supersede domain-name-servers 127.0.0.1; > so that I do not get the DNS from the ISP provider. > > I am using unbound to resolve my queries. With the new changes I can not > get the same functionality. > > I tried to add this in /etc/dhcpleased.conf > interface urtwn0 ignore dns > where urtwn0 is my interface or disable resolvd. > > If resolvd is on I get my ISP DNS server, if not when unbound starts > resolvd adds the ISP DNS server to resolv.conf. > > Can you please tell me what am I doing wrong and how can I have only > 127.0.0.1 on the resolv.conf file? If you want to list only specific nameservers in resolv.conf, then you don't need to run resolvd at all. > Thank you!
Dhcp client configuration in 7.0
Hello to you all! Prior to 7.0 I was using this line in /etc/dhclient.conf supersede domain-name-servers 127.0.0.1; so that I do not get the DNS from the ISP provider. I am using unbound to resolve my queries. With the new changes I can not get the same functionality. I tried to add this in /etc/dhcpleased.conf interface urtwn0 ignore dns where urtwn0 is my interface or disable resolvd. If resolvd is on I get my ISP DNS server, if not when unbound starts resolvd adds the ISP DNS server to resolv.conf. Can you please tell me what am I doing wrong and how can I have only 127.0.0.1 on the resolv.conf file? Thank you!
Re: proper way to grow softraid partition
On 10/27/21 1:11 PM, kasak wrote: Hello misc! I want to replace my two 2TB hdd, joined in raid1. I have two 4TB drives, and I want to replace smaller drives with them. it wouldn't be a problem, if i had some spare sata ports, but in my pc i have only one left. So, I can attach only one of this 4 tb drives at the same time. I think, maybe I can attach new 4 tb drive to old raid as a third volume, wait for it "repair", Unfortunately, unless something changed when I wasn't looking, you can't change the number of drives in a softraid RAID1 after creation. I really wish you could. and then remove 2 tb drives, add one more 4 tb and "repair" raid again. I don't know, will this operation actually grow my partition, or it is a bad idea from the beginning? nope, you would end up with a 2T RAID partition on a 4G drive. Which is fine, except you didn't achieve your goal. Alternate, can i create raid 1 volume from just one drive, rsync files between raids and after add another disk? Again, you can't change the number of drives in a softraid RAID1 set after creation. And you can't change the size of a softraid partition. What I would (and have) done is this, assuming this is your only computer available: * extract both your 2T drives. * insert both 4T drives, build a RAID1 set. * Insert ONE of the old 2T drives and ONE of the 4T drives into your system. On boot, you end up with two degraded arrays...but that will work for your purposes! * Copy the data from the old disks to the new disks * Change fstab * Remove the old 2T disk, and replace with the 4T disk left over, rebuild the degraded array onto the 4T disk. * DONE! Now...since you have ONE spare port still, I'd actually cheat and remove one 2T disk, and put both new disks in place, build the array, and copy over. Fix fstab, remove the old 2T disk, done. HOWEVER, something else to consider -- from later messages, sounds like you have a non-RAID boot drive and RAID data drives. I SUSPECT you could build out your new 4T array as a bootable softraid and move your boot drive data AND the 2T of old data all to the one 4T array and still have a lot of new space (a basic OpenBSD install is barely noticeable in a 4T disk!). Now you have redundancy in both boot and data, and one less disk, which will be a small power reduction, and one less point of failure. Nick.
Re: use pfctl to reread /etc/mail/spamd-white table
On 2021-10-28 12:06:24, Zé Loff wrote: From the man page: For the add, delete, replace, and test commands, the list of addresses can be specified either directly on the command line and/or in an unformatted text file, using the -f flag. So: pfctl -t spamd-white -T add -f /etc/mail/spamd-white should do it. I am deeply sorry; I was too blind to see. Thank you very much for the pointer. Regards Harri
Re: Audio codec support for new(er) Framework laptops?
On Fri, Oct 29, 2021 at 09:13:57AM +, aval...@posteo.net wrote: > Hi Misc! > > Does anyone know whether the Tempo 92HD95B audio codec is supported? > > https://temposemi.com/products/pclaptop-hd/92hd95/ > > I'm considering getting the Framework laptop and Joshua Stein's website > indicates that at this point, it's pretty well supported > > https://jcs.org/2021/08/06/framework > > But Framework is changing audio codecs on their next batches of > machines. > > https://frame.work/blog/solving-for-silicon-shortages > > Thus far, I haven't been able to find a way to check whether the new > audio chip is supported, as "fully supported in both Windows and Linux" > doesn't actually say much, and Tempo's answer to "how do I get a driver" > is "Ask our OEM partner that actually made the computer in question" > > I *have* identified that the chip is compatible with Intel's HD audio > interface, so from what I'm reading in azalia's man page, I think it > *should* have support already under azalia, but I'll admit, the > technical specs go a bit over my head. > > If anyone can clarify this for me, I'd really appreciate it. > Short answer: virtually any HDA codec is supported and there are good chances that sound will just work on this laptop. Long answer: The HDA spec. allows the driver (i.e. azalia(4)) to control all HDA-compatible codecs in a uniform way, so any past or future codec is supposed to just work with the current driver, provided the codec is HDA compatible. There are rare hardware bugs or "creative" ways of connecting the codec to the HDA host that cause problems, most of them are handled by quirks in the azalia(4) driver. There are few laptops that have HDA codecs that require firmware to make advanced features work. Certain recent laptops come with microphones that are not physically connected to the HDA codec (instead they use a secondary audio device OpenBSD doesn't support yet).
Audio codec support for new(er) Framework laptops?
Hi Misc! Does anyone know whether the Tempo 92HD95B audio codec is supported? https://temposemi.com/products/pclaptop-hd/92hd95/ I'm considering getting the Framework laptop and Joshua Stein's website indicates that at this point, it's pretty well supported https://jcs.org/2021/08/06/framework But Framework is changing audio codecs on their next batches of machines. https://frame.work/blog/solving-for-silicon-shortages Thus far, I haven't been able to find a way to check whether the new audio chip is supported, as "fully supported in both Windows and Linux" doesn't actually say much, and Tempo's answer to "how do I get a driver" is "Ask our OEM partner that actually made the computer in question" I *have* identified that the chip is compatible with Intel's HD audio interface, so from what I'm reading in azalia's man page, I think it *should* have support already under azalia, but I'll admit, the technical specs go a bit over my head. If anyone can clarify this for me, I'd really appreciate it. Thank you, - Avalon Woodard
