From: Mark Wielaard <mark@klomp.org>
To: Brian Inglis <Brian.Inglis@shaw.ca>,
Brian Inglis <Brian.Inglis@systematicsw.ab.ca>,
overseers@sourceware.org
Subject: Re: [PATCH] fhandler/proc.cc(format_proc_cpuinfo): add Linux 6.1 cpuinfo
Date: Wed, 21 Dec 2022 00:56:56 +0100 [thread overview]
Message-ID: <Y6JLyKwj35KjKSC6@wildebeest.org> (raw)
In-Reply-To: <Y6F3IfneiW2xkORX@calimero.vinschen.de>
Hi Corinna,
On Tue, Dec 20, 2022 at 09:49:37AM +0100, Corinna Vinschen via Overseers wrote:
> [Cc overseers, please see especially the end of this mail]
> [...]
> > $ host -a cygwin.com
> > Trying "cygwin.com"
> > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6814
> > ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
> >
> > ;; QUESTION SECTION:
> > ;cygwin.com. IN ANY
> >
> > ;; ANSWER SECTION:
> > cygwin.com. 2630 IN SOA dns1.p01.nsone.net.
> > hostmaster.nsone.net. 1669177740 200 7200 1209600 3600
> > cygwin.com. 2630 IN A 8.43.85.97
> > cygwin.com. 2630 IN MX 10 sourceware.org.
> >
> > Received 139 bytes from 64.59.135.148#53 in 12 ms
> > $ host -a nsone.net
> > Trying "nsone.net"
> > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47686
> > ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
> >
> > ;; QUESTION SECTION:
> > ;nsone.net. IN ANY
> >
> > ;; ANSWER SECTION:
> > nsone.net. 2941 IN NSEC \000.nsone.net. A NS SOA MX
> > TXT AAAA RRSIG NSEC DNSKEY
> >
> > Received 61 bytes from 64.59.135.148#53 in 14 ms
>
> My cygwin.com info looks a bit different, but there are nsone.net
> entries, too:
>
> $ host -a cygwin.com
> Trying "cygwin.com"
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11763
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 6
>
> ;; QUESTION SECTION:
> ;cygwin.com. IN ANY
>
> ;; ANSWER SECTION:
> cygwin.com. 63712 IN MX 10 sourceware.org.
> cygwin.com. 63712 IN NS dns4.p01.nsone.net.
> cygwin.com. 63712 IN NS dns2.p01.nsone.net.
> cygwin.com. 63712 IN NS dns3.p01.nsone.net.
> cygwin.com. 63712 IN NS dns1.p01.nsone.net.
> cygwin.com. 1026 IN A 8.43.85.97
> cygwin.com. 63712 IN TXT "v=spf1 a mx -all"
> cygwin.com. 63712 IN TXT "00918568 domainadmin@redhat.com"
>
> ;; ADDITIONAL SECTION:
> sourceware.org. 7054 IN A 8.43.85.97
> dns3.p01.nsone.net. 7414 IN A 198.51.44.65
> dns4.p01.nsone.net. 7414 IN A 198.51.45.65
> dns1.p01.nsone.net. 7414 IN A 198.51.44.1
> dns2.p01.nsone.net. 7414 IN A 198.51.45.1
> sourceware.org. 7054 IN AAAA 2620:52:3:1:0:246e:9693:128c
>
> Received 344 bytes from 192.168.129.6#53 in 1 ms
>
> Is that all correct now, after the changes by Red Hat IT?
Yes, that looks correct.
You might also want to check the default dkim key can be found:
$ host -t txt default._domainkey.cygwin.com
default._domainkey.cygwin.com descriptive text "k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDLwqjBbSGRiaqBX0INRfT5J8UMusxb6w5PYxMQXlZmRP+stvUoXCEreR2Uw7ARHSTuKUkrpXcQ+cvmsWuktF1xLJh7rO4H6aeK8VngapZTL1YhRztHS7cTkiwgVZeXcYNJM+0eFsJ4PkjsggagyuH4JQEkR7evRMIVnEpx4h1qkwIDAQAB"
Cheers,
Mark
next prev parent reply other threads:[~2022-12-20 23:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b2366e8d-f9c3-fc60-bf5d-9131e73360ae@Shaw.ca>
2022-12-20 8:49 ` Corinna Vinschen
2022-12-20 23:33 ` Mark Wielaard
2022-12-21 8:54 ` Corinna Vinschen
2022-12-20 23:56 ` Mark Wielaard [this message]
2022-12-21 8:56 ` Corinna Vinschen
2022-12-21 16:24 Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2022-12-20 21:16 Brian Inglis
2022-12-19 22:55 Brian Inglis
2022-12-19 23:25 ` Mark Wielaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y6JLyKwj35KjKSC6@wildebeest.org \
--to=mark@klomp.org \
--cc=Brian.Inglis@shaw.ca \
--cc=Brian.Inglis@systematicsw.ab.ca \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).