fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

9.9K
active users

#address

1 post1 participant1 post today

My ISP gave me an interesting scare a couple of minutes ago. As you know if you do not want to pay them for a permanent IPv4 address, which I consider obsolete networking, they remotely reboot your gateway device and assign it a random IP out of one of their IPv4 pools.

This time it didn't take the usual long 30 to 90 Seconds to reboot the device and transfer credentials to obtain the new IP.
The Gateway got in an infinite loop somewhere and I had to Power it off, then had to wait 90 seconds to power cycle it before it took 180 seconds for the device to finally get the new IP.

Someone screwed up the login sequences for the xDSL devices of which the hashtag is in the toot and now we as the paying customer again have to pay for it in wasted time.

Luckily this power cycling off xDSL devices occurs only once in 6 weeks and usually I do not use the internet at that point in time.

In case you are wondering my Gateway uses obsolete technology, is forcibly assigned by the ISP and it's also cursed with a extremely low transfer speed.

I just included a speedtest after first draft of this toot

As you can see the speeds here are so low the connection is virtually unusable for anything where you have to move a big bites of data. They still manage to extort more than USD 30 a month for this connection

#xDSL#ISP#Services
Continued thread

mouse and keyboard are created as children of a phantom node:

children
node 0xfe0600c8
children
node 0xfe060620
name mouse
device_type mouse
reg [0, 0, 0, 1]
status okay
interrupts [12, 0, 0, 0]
#buttons [0, 0, 0, 3]
node 0xfe0604f0
name kbd
device_type keyboard
reg [0, 0, 0, 0]
status okay
interrupts [1, 0, 0, 0]
language [69, 78, 0]

which then gets its attributes pointer assigned later:

node 0xfe0600c8
name fdc
device_type [98, 108, 111, 99, 107, 0, 0]
#address-cells [0, 0, 0, 1]
status okay
reg [0, 0, 3, 240, 0, 0, 0, 2]
interrupts [0, 0, 0, 6]
children
node 0xfe060620
name mouse
device_type mouse

my hypothesis seeing this is that a procedure for creating the 8042 tree node failed and the node was freed, but the current node pointer was left at that position. kbd and mouse were meant to be created as children of that node. once the node was re-allocated as fdc, the children came with it.

ok new strategy for finding the last wrong bits of solaris boot. for every memory access in reverse order, i'm dumping the ofw tree along with the pc address where it was modified.

Hoping to see _exactly_ where it gets messed up.

*** PC = fe01c1c0 T = 308779
node 0xfe058050
children
node 0xfe0697b8
name packages
children
node 0xfe0698a8
name disk-label
node 0xfe069858
name deblocker
node 0xfe069808
name obp-tftp
node 0xfe0696a0
name chosen
stdin [0, 0, 0, 0]
node 0xfe069658
name options
node 0xfe069560
node 0xfe058750
node 0xfe058578
name pci
device_type pci
status okay
#address-cells [0, 0, 0, 3]
#size-cells [0, 0, 0, 2]
ranges [1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 128, 0, 0, 0, 0, 0, 0, 0, 62, 128, 0, 0, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 192, 0, 0, 0, 0, 0, 0, 0, 63, 0, 0, 0]
bus-range [0, 0, 0, 0, 0, 0, 0, 0]
name pci1057,1
device_type host
status okay
reg [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
vendor-id [0, 0, 16, 87]
device-id [0, 0, 0, 1]
revision-id [0, 0, 0, 36]
class-code [0, 6, 0, 0]
min-grant [0, 0, 0, 0]
max-latency [0, 0, 0, 0]
devsel-speed [0, 0, 0, 0]
children
node 0xfe067210
name pci1014,a
device_type isa
status okay
reg [0, 0, 120, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
vendor-id [0, 0, 16, 20]
device-id [0, 0, 0, 10]
revision-id [0, 0, 0, 2]
class-code [0, 6, 1, 0]
min-grant [0, 0, 0, 0]
max-latency [0, 0, 0, 0]
devsel-speed [0, 0, 0, 0]
#address-cells [0, 0, 0, 1]
ranges [0, 0, 0, 0, 253, 4, 156, 96, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 128, 0, 0, 0, 254, 3, 220, 20, 0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0]

Email aliases are alternative email addresses, except when email is sent to an alias, it still arrives in your main inbox. Use them in conjunction with filters and folders as a powerful way to organize incoming messages.

#email #address #alias #inbox
pcworld.com/article/2535032/us

PCWorldWant a tidier inbox? Start using email aliases. Here's howHow to set up email aliases for newsletters, receipts, and more.
Progress!
I've got a basic #emulator working for my #Pat80 #homebrew #zilog #z80 #computer !
This should ease the os development as I can test the changes without having to: remove the #eeprom from the computer (without bending the pins), program it in the #TL866 programmer, place it again on the computer (aligning pins correctly), test, notice it's not working and have no idea why, start debugging with the logic probe on the #address and #data pins, swear in arcane languages... 😅

https://git.ichibi.eu/penguin86/pato-z80-home-computer/commits/branch/c-emulator

GitHub 的 IPv6...

因為在弄 IPv6-only 的機器連不上 GitHub,在找解法的時候發現了這個 incident:「GitHub Status - We are investigating reports of degraded performance.」。

去年年初的時候 GitHub 有試著上 IPv6 然後造成 incident:

This incident was the result of an infrastructure change that was made to our load balancers to prepare us for IPv6 enablement of GitHub.com. This ch

blog.gslin.org/archives/2025/0

Gea-Suan Lin's BLOG · GitHub 的 IPv6...因為在弄 IPv6-only 的機器連不上 GitHub,在找解法的時候發現了這個 incident:「GitHub Status - We are investigating reports of degraded performance.

A long, bitter summary of how #traveling and #privacy have become mutually exclusive:

»#PNR records are sent by most commercial #airlines to the destination country some 48 to 72 hours before departure. […] the traveler’s #address, cell #phone number, date of flight #booking, where the ticket was purchased, credit card and other #payment information, billing address, #baggage information, frequent flyer information, general remarks related to the passenger, date of intended travel, complete travel #itinerary, names of accompanying travelers, travel agency information […]

[on face scanning:] “Everybody should be able to go out of his own country and into any country and come back without having to queue in line and being able to use only his #face,” […]

[on "AI":] “They're kind of black boxes, so they will tell you that this person is potentially risky and this person kind of looks different, but how it makes this decision is kind of a mystery.” […]

[on gray surveillance:] the company’s “risk assessment capability enables a government to export its border to every single point on the globe where passengers can board flights, ships or trains bound for their territory.”«

wired.com/story/inside-the-bla

WIRED · Inside the Black Box of Predictive Travel SurveillanceBy Caitlin Chandler