> Not every detail gets into the FAQ. The difference between
> 'join' and 'nwid' is described in the ifconfig(8) man page.
Thank you for the helpful response Ken.
If anyone is inclined, a quick patch to include what I
thought could also be helpful to others without going
on too long. Hopefully
I think it would be better to be consistent for either use case -
all 'nwid' or all 'join' (I prefer 'join').
https://www.openbsd.org/faq/faq6.html#Wireless
section: "Configuring a Wireless Adapter"
tux2bsd
p.s. Below has no real point other than to share the tale. It's how I
ended up no
> I'm not sure their "Geekfeminism Code of Conduct"
> (https://hikari.acmelabs.space/coc.html) works well with OpenBSD.
Any idiot that adheres gender and race ideologies can get fucked, they are all
societal fire starters.
tux2bsd
It'd be good to sort this, a bit of a meta remote hole...
This = bad. Only people with necessary access can fix.
$ host -t a openbsd.org 199.185.230.19
Using domain server:
Name: 199.185.230.19
Address: 199.185.230.19#53
Aliases:
Host openbsd.org not found: 2(SERVFAIL)
$ host -t a
rouble shooting.
> (btw there's another small problem with the zone which you didn't spot ;)
You're implying I was checking each little thing, I wasn't. Feel free to spill
the beans.
tux2bsd
Mailing list expansion problem:
tux2bsd
>you claim the SOA serial being a timestamp would have helped in
diagnosis.
Actually, I did not.
tux2bsd:
>> The SOA record could do with some attention too.
...
>> That is true but it doesn't help when trouble shooting.
Those comments were simply an observation passed along
What would be interesting is finding out what
happened, what it a mistake or a software problem?
tux2bsd
ost openbsd.org not found: 2(SERVFAIL)
Someone should prevent that from happening again.
tux2bsd
cdn.openbsd.org (which is served by Fastly)
A few days ago I posted in tech@ to raise the Cloudflare issue that you've also
noticed. Whoever operates the Cloudflare mirror needs to pull finger.
tux2bsd
> On 12/5/24 08:26, tux2bsd wrote:
> > No post about the 7.5 release on https://twitter.com/openbsd
> >
> > Seemed strange, if deliberate then exceptionally petty.
> >
> Twitter is dead.
That's your leftism talking, not reality.
have been a normal person's
response, not immediately *I blocked you*.
tux2bsd
On Sunday, May 12th, 2024 at 11:04 AM, T.J. Townsend wrote:
> On Sat, May 11, 2024 at 10:26:49PM +0000, tux2bsd wrote:
>
> > Seemed strange, if deliberate then exceptionally petty.
> Wasting everyone's time by complaining on a mailing list that
> we didn't post a tweet seems
I'm a bit late remembering to follow this up.
No post about the 7.5 release on https://twitter.com/openbsd
Seemed strange, if deliberate then exceptionally petty.
IIRC I saw it on OSNews on the day.
Triumphantly they regales "I blocked tux2bsd
based on a single email which made this they felt personally attacked. This
they sure showed tux2bsd!!!".
Meanwhile, Stuart Longland is lost somewhere in at the commune looking for
they's bourgeoisie reading glasses.
tux2bsd
ngular) announcement via Twitter. At no point in time did I
suggest it was not announced via standard channels.
You and T.J. Townsend have a personal issue with Twitter, so much so that the
pair of you are being irrational.
tux2bsd
mporary unique filenames like this:
delete_list=$(mktemp)
source_list=$(mktemp)
target_list=$(mktemp)
# Do your code. If you want to keep something you do
# that appropriately then:
rm $delete_list $source_list $target_list
tux2bsd
typewriters in days, weeks at most.
tux2bsd
18 matches
Mail list logo
