Heute ist das #Surfans F20 hier in seiner kleinen Hartpappschachtel (natuerlich mit Versandverpackung) angekommen. Ich bin gluecklich, dass ich eines noch bekommen habe, da laut eines lokalen Ladens dort "nichts mehr vor Ende naechsten Jahres" kommen wird.

Da muss ich leider (!) sagen: Danke #Amazon , dass ihr noch welche habt! Ich habe es dann einschalten wollen, aber die interne Batterie hat sich wohl selbst entladen. Somit habe ich das dabei mitgelieferte USB-Kabel genommen und es an meinen PC (mit #Linux Kernel 5.10.0-8 drauf) angeschlossen. sudo dmesg eingegeben, aber kein USB-Geraet wurde erkannt. Ich sah' auch, dass es in den Lademodus beim Starten gewechselt ist. Ich habe das aber erstmal nicht weiter beachtet (was spaeter entscheidend war). Ich habe dann das Geraet abgezogen und erneut eingesteckt und dann wurde es vom Linux-Kernel erkannt:

[2258778.635746] usb 2-12: new high-speed USB device number 9 using xhci_hcd
[2258778.788539] usb 2-12: New USB device found, idVendor=c502, idProduct=0023, bcdDevice=ff.ff
[2258778.788546] usb 2-12: New USB device strings: Mfr=5, Product=6, SerialNumber=7
[2258778.788550] usb 2-12: Product: SURFANS
[2258778.788553] usb 2-12: Manufacturer: SURFANS
[2258778.788555] usb 2-12: SerialNumber: SURFANS
[2258778.797177] usb-storage 2-12:1.0: USB Mass Storage device detected
[2258778.797497] scsi host8: usb-storage 2-12:1.0
[2258779.824470] scsi 8:0:0:0: Direct-Access     SURFANS  HIFI PLAYER      000  PQ: 0 ANSI: 2
[2258779.825003] sd 8:0:0:0: Attached scsi generic sg3 type 0
[2258779.825329] sd 8:0:0:0: Power-on or device reset occurred
[2258779.848255] sd 8:0:0:0: [sdd] Attached SCSI removable disk
[2258781.937528] sd 8:0:0:0: [sdd] 61022208 512-byte logical blocks: (31.2 GB/29.1 GiB)
[2258781.937849] sd 8:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[2258781.940616]  sdd: sdd1

Aber das ist noch verkraftbar. Ich kann mich als als gluecker Kunde von #Surfans bezeichnen.

Gosh, cannot I see a single game #screenshot here on the #Fediverse without a #rainbow flag in it? I know this is about #Stux and that's okay. They claim that #LGBTQ+ is all-inclusive. Except us #straight people. And no, were not worth only the little + at the end and no, 87-89% of the world's population are straight, not bisexual.

I demand that they stop their #heterophobic game. I don't want to be told that I'm a bad person only because of I don't let a rainbow flag being shoveled up my ass. Why do we (straight people) have to praise what a minority does while they give us so much shit back? What do they expect from us (and me in particular) that when we date someone and later find out that he/she has the improper genitals between their legs (which is not expected)? I for instance would expect that a woman always has a #vagina between her legs and never a penis.

When I date a woman, I expect her to have a vagina, because that is what all women are born with. And no, when you are born with a penis, then you are born as a man and not a woman! If you disagree with the genitals being given to you by nature, that's not my problem not wanting to date you, it is your problem and you should seek professional help.

Have you been neglected as a #boy because your mother wants to have a #girl ? Then she is the cause of this, not me or any "transphobia" or "woman-hatred". So why radical feminists, do you say that "not all women have a vagina"? Stop these sweet lies once and for all! I don't want to let a trans-woman stick her dick in my mouth or ass only to be called "open-minded".

#My2cents - To be continued ...

#Racism is not dead, but it is on life support – kept alive by politicians, race hustlers and people (radical leftists) who get a sense of superiority by denouncing others as ‘racists’.

— Thomas #Sowell

Edit: My own words added are marked with italic.

Saying you "don't agree with cancel culture" means that you subscribe to the right wing narrative of "cancel culture", and you will be blocked immediately.

I'm not linking there so you cannot find it directly but have to find it out by yourself. But I give you a hint that you will find a rainbow flag next to the account's name ...

And this is what is so much wrong with this "culture", that they will label you outright a #Nazi, a #transphobe, a #homophobe, #attention-seeker, that you have some #bigotry, having educational #bias and you should do your "proper research" when you magically don't agree with whatever they have to say. If you do so, you push possible allies further away from you who can help you who would initially agree to help you but now, since you label them with such horrible words, they won't anymore.

I'm a #straight white man. I'm into actual (=biological) women and their vaginas and I'm befriended with a #Zambian, #black, straight woman. So how can I be a Nazi here? Stop your #heterophobic , straight-shaming magical-thinking nonsense! I'm from now on play my game with you, not yours anymore.

Ich bin Besitzer eines #Vorwerk Kobold 135 mit einer Elektrobuerste #EB351 . Bei dieser hat von einem Tag auf den anderen die sich bei Inbetriebnahme drehenden Borsten (vorne unten im Fach) nicht mehr gedreht und auch war der Motor aus.

Ich dachte nun an schlimmstes und habe die EB 351 erstmal gesaeubert, jedoch ohne Erfolg. Dann hat diese ja einen Fussschalter, der den kleinen Elektromotor und die sich drehenden Borsten beim Herunterdruecken abschaltet und beim erneuten Betaetigen normalerweise wieder einschaltet. Aber hier passierte ... rein gar nichts. Der Motor blieb aus.

Letztendlich war die Mechanik zum Absenken und Anheben der statischen Borsten (vorne drinne) so stark verstaubt, dass diese nicht mehr hoch kommen konnten. Ich musste also von Hand diese wieder absenken, was auch zum gewuenschten Erfolg gefuehrt hatte. Dies habe ich gemacht, indem ich die kleine schwarze Plastiknut, vorne unter der weissen Haube, in der Mitte manuell nach oben gezogen habe. Damit wird wohl ein Taster betaetigt (oder freigegeben), der dann wieder den Motor einschaltet und die runden Borsten sich wieder drehen.

Den Erfolg wollte ich nur mit euch geteilt haben, dass ihr eure EB 351 (und EB 350 scheint wohl auch drunter zu leiden) nicht unnoetig (=funktionierend) wegwerft.

I have to much issues with #systemd that I'm willing to continue, here are the 2 major ones:

1) On system startup, I don't see all the starting daemons anymore, just until #initrd is finished and then nothing more until #LightDM starts and the graphical UI comes up

2) Console output is no more scrolling down. Maybe this is the reason for 1) here. So this is what happens: I have to execute a small shell script to decrypt and mount my /home directory. It will mount an USB stick and uses #GnuPG to ask me for a passphrase which decrypts a symmetric key stored on that USB stick (backed up on 2 other sticks). Then it will decrypt the #LUKS device which contains my /home directory. It will also start a filesystem check prior mounting it to /home with fsck.ext4 -yv /dev/mapper/home. For this it outputs messages I actually need to see if all went smooth. SystemD seem to have a bug here that prevents it from showing (no scrolling text). I have to switch consoles e.g. with ALT+F1/F2 and the output is shown again.

This really sucks as this way, I cannot properly maintain my #Linux system. I'm now migrating to #Devuan which is free of systemd and which provides the previous old-but-working #sysvinit . So, goodbye #Debian /systemd and hello Devuan/sysvinit!