Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

Ignore this toot just testing something.#FreeBSD

Uncategorized
32 9 114

Gli ultimi otto messaggi ricevuti dalla Federazione
  • Magnetic-Suspension Hoverboard is Only 11 Years Late

    Anyone who saw Back to the Future II was disappointed when 2015 rolled around with nary a hoverboard in sight. There have been various attempts to fake it, but none of them quite have the feel of floating about wherever you’d like to go that the movie conveys. The little-known YouTuber [Colin Furze] has a new take on the idea: use magnets. Really big magnets.

    If you’re one of [Colin]’s handful of subscribers, then you probably saw his magnetic-suspension bike. We passed on that one, but we couldn’t resist the urge to cover the hoverboard version, regardless of how popular [Colin] might be on YouTube. It’s actually stupidly simple: the suspension is provided by the repulsive force between alarmingly large neodymium magnets. In this case, two are on the base plate that holds the skateboard ‘trucks’, and two are on the wooden ‘deck’ that [Colin] rides upon.

    Of course magnetic repulsion is a very unstable equilibrium, so [Colin] had to reduce the degrees of freedom. In his first test, that was with a pair of rods and linear bearings. That way the deck could only move in the z-axis, providing the sensation of hovering without allowing the deck to slide off its magnetic perch. Unfortunately those pins transferred too much vibration from the ground into the deck, ruining the illusion of floating on air.

    After realizing that he’d never be able to ollie (jump) this massive beast of a skateboard, [Colin] decides he might as well use a longboard instead. Longboards, as the name implies, are long skateboards, and are for transportation, not tricks. The longboard gets the same massive magnets, but after a couple of iterations to find a smoother solution — including a neat but unsuccessful tensegrity-inspired version — ends up with a pair of loosely-fitted pins once again, though relocated to the rear of the board. From the rider’s perspective, it looks exactly like a hoverboard, since you can’t see underneath from that angle. According to [Colin], it feels like a hoverboard, too.

    The only way to do better would be with eddy currents over copper, or superconductors over a magnetic track, but both of those methods limit you to very specific locations. This might be a bit of a fakeout, but its one with a degree of freedom. One, to be specific. You have to admit, it’s still less of a fake than the handle-less Segway we got in 2015, at least.

    youtube.com/embed/yzXZ7cZXifo?…

    hackaday.com/2026/03/15/magnet…

    read more

  • @exador23 I i didn't know that you worked on either of those!

    read more

  • @evan what part? lol.

    read more

  • @exador23 wait what

    read more

  • @BathysphereHat this one gets it

    read more

  • Gli LLM sono una forza opposta ai social media?

    Secondo un'opinione controcorrente, le loro risposte sui temi importanti seguirebbero il consenso degli esperti.

    https://wp.me/p6hcSh-9s5

    read more

  • Really happy for Paul Thomas Anderson. He should have won that Best Picture and Best Director Oscar many times over before finally getting it tonight.

    Full disclosure: I worked on the Punch Drunk Love soundtrack, and while we were recording Fiona Apple's 2nd record, he was filming Magnolia and dating Fiona. He's a good guy.

    read more

  • @evan None of the above... yet

    read more
Post suggeriti
  • call for testing

    Uncategorized freebsd sylve openzfs zfs bhyve cft
    3
    0 Votes
    3 Posts
    4 Views
    @grahamperrin this looks interesting!Cc: @FreeBSDFoundation
  • 0 Votes
    1 Posts
    4 Views
    NEW VIDEO - The Uncomfortable Truth About Windows Server vs. Open Source.#FreeBSD #Windows #Linux #Opensource #garyhtechhttps://youtu.be/JMc1KC7lNJM?si=512atXRIe3yKhua0 via @YouTube
  • 0 Votes
    1 Posts
    7 Views
    I've got a weird issue on my #FreeBSD ThinkPad. Since setting up lagg yesterday which worked fine. I powered off last night and then switched it on this morning. I noticed that I had no network access on either the re1 interface or wlan0. I powered off and on and it worked. I have since discovered that if it doesn't work if I just doas service netif restart it starts to work again.This is my lagg setup in /etc/rc.conf# WiFiwlans_iwlwifi0="wlan0"ifconfig_wlan0="WPA SYNCDHCP"cloned_interfaces="lagg0"ifconfig_lagg0="up laggproto failover laggport re1 laggport wlan0 DHCP"This is the output of ifconfig when it's working:re0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE> ether 8c:8c:aa:bd:bb:f0 media: Ethernet autoselect (none) status: no carrier nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>re1: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500 options=80088<VLAN_MTU,VLAN_HWCSUM,LINKSTATE> ether 8c:8c:aa:bd:bb:ef inet 192.168.0.194 netmask 0xffffff00 broadcast 192.168.0.255 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>wlan0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500 options=0 ether 8c:8c:aa:bd:bb:ef hwaddr 70:9c:d1:af:ad:93 inet 192.168.0.194 netmask 0xffffff00 broadcast 192.168.0.255 groups: wlan ssid Smithies channel 40 (5200 MHz 11a vht/80-) bssid f0:9f:c2:ab:8d:c3 regdomain FCC country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit AES-CCM ucast:128-bit txpower 17 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi -ldpctx ldpcrx -uapsd vht vht40 vht80 vht160 -vht80p80 wme roaming MANUAL parent interface: iwlwifi0 media: IEEE 802.11 Wireless Ethernet VHT mode 11ac status: associated nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>lagg0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500 options=0 ether 8c:8c:aa:bd:bb:ef hwaddr 00:00:00:00:00:00 inet 192.168.0.194 netmask 0xffffff00 broadcast 192.168.0.255 laggproto failover lagghash l2,l3,l4 laggport: re1 flags=5<MASTER,ACTIVE> laggport: wlan0 flags=0<> groups: lagg media: Ethernet autoselect status: active nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>This is the output when not working on first boot:re0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE> ether 8c:8c:aa:bd:bb:f0 media: Ethernet autoselect (none) status: no carrier nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>re1: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500 options=80088<VLAN_MTU,VLAN_HWCSUM,LINKSTATE> ether 8c:8c:aa:bd:bb:ef inet 192.168.0.194 netmask 0xffffff00 broadcast 192.168.0.255 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>wlan0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500 options=0 ether 8c:8c:aa:bd:bb:ef hwaddr 70:9c:d1:af:ad:93 inet 192.168.0.194 netmask 0xffffff00 broadcast 192.168.0.255 groups: wlan ssid Smithies channel 40 (5200 MHz 11a vht/80-) bssid f0:9f:c2:ab:8d:c3 regdomain FCC country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit AES-CCM ucast:128-bit txpower 17 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi -ldpctx ldpcrx -uapsd vht vht40 vht80 vht160 -vht80p80 wme roaming MANUAL parent interface: iwlwifi0 media: IEEE 802.11 Wireless Ethernet VHT mode 11ac status: associated nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>lagg0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500 options=0 ether 8c:8c:aa:bd:bb:ef hwaddr 00:00:00:00:00:00 inet 192.168.0.194 netmask 0xffffff00 broadcast 192.168.0.255 laggproto failover lagghash l2,l3,l4 laggport: re1 flags=5<MASTER,ACTIVE> laggport: wlan0 flags=0<> groups: lagg media: Ethernet autoselect status: active nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>I should note that running doas service netif restart once it's working makes it fail again.Any ideas ??
  • 0 Votes
    1 Posts
    13 Views
    so Raptor gave me access to a Talos II to do some work on FreeBSD/ppc64le. first thing i noticed: the boot process is *very* unusual. it doesn't use the FreeBSD loader at all; instead it has a Linux-based firmware loader called Petitboot which can load and kexec() the FreeBSD kernel directly. however it needs a rather odd partition layout to do that:# Device Mountpoint FStype Options Dump Pass#/dev/nda0p2 / ufs rw 1 1/dev/nda0p1 /boot msdosfs rw 2 2i assume this is because Petitboot can't read FreeBSD UFS, so we need the kernel (which is in /boot/kernel) to be on FAT. Raptor suggested we should make the loader kexec()able instead, which seems like a good idea, but from what i can tell this platform doesn't use OpenFirmware at all, and i'm not even sure we have a PowerNV-native loader.(as you can tell, i know very little about either POWER or FreeBSD/powerpc, so this is going to be an interesting learning experience.)#FreeBSD