Search
1000 results for “torsten”
-
A little bit of Flickr Love: Gravelbike --> Roadbike
https://www.flickr.com/photos/huegelreiter/53294312923/in/dateposted-public/
#custom #Titanium #Rennrad #roadbike #gravel #bike #gravelbike #allroad #allroadbike #22bikes #Drifter
-
A little bit of Flickr Love: Gravelbike --> Roadbike
https://www.flickr.com/photos/huegelreiter/53294312923/in/dateposted-public/
#custom #Titanium #Rennrad #roadbike #gravel #bike #gravelbike #allroad #allroadbike #22bikes #Drifter
-
The by far two most beloved steeds in my stable.
One is a mountain bike - which is the best and most fun Gravelbike for me.
And the other is a gravel bike - which is the best and most fun Roadbike for me. Munching all the miles with comfort and speed, regardless of the road.https://www.instagram.com/p/Cy3ygbescvn/?img_index=1
.
.
#cycling #radfahren
#22bikes #Drifter
#Titaniumbikes
#Gravel
#DropbarMTB #29er
#Adventurebike #Allroadbike #Gravelbike
#roadbikes #Rennrad -
The by far two most beloved steeds in my stable.
One is a mountain bike - which is the best and most fun Gravelbike for me.
And the other is a gravel bike - which is the best and most fun Roadbike for me. Munching all the miles with comfort and speed, regardless of the road.https://www.instagram.com/p/Cy3ygbescvn/?img_index=1
.
.
#cycling #radfahren
#22bikes #Drifter
#Titaniumbikes
#Gravel
#DropbarMTB #29er
#Adventurebike #Allroadbike #Gravelbike
#roadbikes #Rennrad -
The by far two most beloved steeds in my stable.
One is a mountain bike - which is the best and most fun Gravelbike for me.
And the other is a gravel bike - which is the best and most fun Roadbike for me. Munching all the miles with comfort and speed, regardless of the road.https://www.instagram.com/p/Cy3ygbescvn/?img_index=1
.
.
#cycling #radfahren
#22bikes #Drifter
#Titaniumbikes
#Gravel
#DropbarMTB #29er
#Adventurebike #Allroadbike #Gravelbike
#roadbikes #Rennrad -
The by far two most beloved steeds in my stable.
One is a mountain bike - which is the best and most fun Gravelbike for me.
And the other is a gravel bike - which is the best and most fun Roadbike for me. Munching all the miles with comfort and speed, regardless of the road.https://www.instagram.com/p/Cy3ygbescvn/?img_index=1
.
.
#cycling #radfahren
#22bikes #Drifter
#Titaniumbikes
#Gravel
#DropbarMTB #29er
#Adventurebike #Allroadbike #Gravelbike
#roadbikes #Rennrad -
The by far two most beloved steeds in my stable.
One is a mountain bike - which is the best and most fun Gravelbike for me.
And the other is a gravel bike - which is the best and most fun Roadbike for me. Munching all the miles with comfort and speed, regardless of the road.https://www.instagram.com/p/Cy3ygbescvn/?img_index=1
.
.
#cycling #radfahren
#22bikes #Drifter
#Titaniumbikes
#Gravel
#DropbarMTB #29er
#Adventurebike #Allroadbike #Gravelbike
#roadbikes #Rennrad -
Die sehr kluge und sehr gute Maja Göpel hat einen Podcast, in dem sie mit ebenfalls sehr klugen Menschen spricht.
Mit dem sehr guten Bijan Moini von der Gesellschaft für Freiheitsrechte zum Beispiel über Demokratie und Freiheit.https://www.mission-wertvoll.org/neu-denken-folge-6-demokratische-sicherheit-mit-bijan-moini/
Ist keine verschwendete Zeit. Versprochen!
-
Ich entdecke gerade immer wieder neue Dinge und merke schon, dass mir das alte #twlz und die Inputs sehr fehlen...
Gerade auch für #sopaed|s war das schon immer sehr cool.
Ich werd mich mal bemühen, wieder aktiver beizutragen.
Da kann man gerne mit den coolen Apps von @Lernsachen anfangen: https://lernsachen.online/apps/
#FediLZ -
Ich entdecke gerade immer wieder neue Dinge und merke schon, dass mir das alte #twlz und die Inputs sehr fehlen...
Gerade auch für #sopaed|s war das schon immer sehr cool.
Ich werd mich mal bemühen, wieder aktiver beizutragen.
Da kann man gerne mit den coolen Apps von @Lernsachen anfangen: https://lernsachen.online/apps/
#FediLZ -
Ich entdecke gerade immer wieder neue Dinge und merke schon, dass mir das alte #twlz und die Inputs sehr fehlen...
Gerade auch für #sopaed|s war das schon immer sehr cool.
Ich werd mich mal bemühen, wieder aktiver beizutragen.
Da kann man gerne mit den coolen Apps von @Lernsachen anfangen: https://lernsachen.online/apps/
#FediLZ -
Ich entdecke gerade immer wieder neue Dinge und merke schon, dass mir das alte #twlz und die Inputs sehr fehlen...
Gerade auch für #sopaed|s war das schon immer sehr cool.
Ich werd mich mal bemühen, wieder aktiver beizutragen.
Da kann man gerne mit den coolen Apps von @Lernsachen anfangen: https://lernsachen.online/apps/
#FediLZ -
Ich entdecke gerade immer wieder neue Dinge und merke schon, dass mir das alte #twlz und die Inputs sehr fehlen...
Gerade auch für #sopaed|s war das schon immer sehr cool.
Ich werd mich mal bemühen, wieder aktiver beizutragen.
Da kann man gerne mit den coolen Apps von @Lernsachen anfangen: https://lernsachen.online/apps/
#FediLZ -
Europe must strengthen its own security, unity, and strategic independence. Partnership requires trust — and trust must be earned. #Europe #TransatlanticRelations #SecurityPolicy #MunichSecurityConference #Geopolitics #StrategicAutonomy
-
https://www.fdr.uni-hamburg.de/record/18530
🌱 #Cannabis #Evaluation2026 #Teillegalisierung #positiv 😀
#SPD #DIELINKE #CSU #CDU #FW #Grüne #Warken #NinaWarken #Streeck
https://bsky.app/profile/did:plc:blii7yr7kom5w3vxkb6nvtwz/post/3migmexx6w22i
#Hanfverband #DeutscherHanfverband #Deutschland #Germany #Klimaschutz #Klimapflanze #warondrugs #Merz #Söder #Klingbeil #ThorstenFrei #CarmenWegge #Cannabisklage #Grundrechte #Menschenrechte #Gesundheit #Medizin #Hanfwissen #Hanfgeschichten #Fridaysforfuture #Klimaschutz #Demokratie #CanG #Hanf #hemp #ABERdieKINDER #fff
-
Half of the support for the #initrd (not to be confused with #initramfs!) was removed from #Linux 7.0 through a #vfs merge from @brauner:
https://git.kernel.org/torvalds/c/996812c453cafa042f2e674738dbf8fa495661f3 and https://git.kernel.org/torvalds/c/ef12d0573a7f5e7a495e81d773ae5f3e98230cd4
""Remove the deprecated linuxrc-based initrd code path and related dead code. The linuxrc initrd path was deprecated in 2020 and this series completes its removal. If we see real-life regressions we'll revert. […]
The no-op load_ramdisk= and prompt_ramdisk= parameters are dropped, and noinitrd and ramdisk_start= gain deprecation warnings.
Initramfs is entirely unaffected. The non-linuxrc initrd path (root=/dev/ram0) is preserved but now carries a deprecation warning targeting January 2027 removal""
-
Half of the support for the #initrd (not to be confused with #initramfs!) was removed from #Linux 7.0 through a #vfs merge from @brauner:
https://git.kernel.org/torvalds/c/996812c453cafa042f2e674738dbf8fa495661f3 and https://git.kernel.org/torvalds/c/ef12d0573a7f5e7a495e81d773ae5f3e98230cd4
""Remove the deprecated linuxrc-based initrd code path and related dead code. The linuxrc initrd path was deprecated in 2020 and this series completes its removal. If we see real-life regressions we'll revert. […]
The no-op load_ramdisk= and prompt_ramdisk= parameters are dropped, and noinitrd and ramdisk_start= gain deprecation warnings.
Initramfs is entirely unaffected. The non-linuxrc initrd path (root=/dev/ram0) is preserved but now carries a deprecation warning targeting January 2027 removal""
-
Half of the support for the #initrd (not to be confused with #initramfs!) was removed from #Linux 7.0 through a #vfs merge from @brauner:
https://git.kernel.org/torvalds/c/996812c453cafa042f2e674738dbf8fa495661f3 and https://git.kernel.org/torvalds/c/ef12d0573a7f5e7a495e81d773ae5f3e98230cd4
""Remove the deprecated linuxrc-based initrd code path and related dead code. The linuxrc initrd path was deprecated in 2020 and this series completes its removal. If we see real-life regressions we'll revert. […]
The no-op load_ramdisk= and prompt_ramdisk= parameters are dropped, and noinitrd and ramdisk_start= gain deprecation warnings.
Initramfs is entirely unaffected. The non-linuxrc initrd path (root=/dev/ram0) is preserved but now carries a deprecation warning targeting January 2027 removal""
-
Half of the support for the #initrd (not to be confused with #initramfs!) was removed from #Linux 7.0 through a #vfs merge from @brauner:
https://git.kernel.org/torvalds/c/996812c453cafa042f2e674738dbf8fa495661f3 and https://git.kernel.org/torvalds/c/ef12d0573a7f5e7a495e81d773ae5f3e98230cd4
""Remove the deprecated linuxrc-based initrd code path and related dead code. The linuxrc initrd path was deprecated in 2020 and this series completes its removal. If we see real-life regressions we'll revert. […]
The no-op load_ramdisk= and prompt_ramdisk= parameters are dropped, and noinitrd and ramdisk_start= gain deprecation warnings.
Initramfs is entirely unaffected. The non-linuxrc initrd path (root=/dev/ram0) is preserved but now carries a deprecation warning targeting January 2027 removal""
-
#VFS support for generic I/O error reporting was merged for #Linux 7.0 by @brauner
https://git.kernel.org/torvalds/c/dd466ea0029961ee0ee6e8e468faa1506275c8a9
""Filesystems currently have no standard mechanism for reporting metadata corruption and file I/O errors to userspace via fsnotify. Each filesystem (xfs, ext4, erofs, f2fs, etc.) privately defines EFSCORRUPTED, and error reporting to fanotify is inconsistent or absent entirely.
This introduces a generic fserror infrastructure built around struct super_block that gives filesystems a standard way to queue metadata and file I/O error reports for delivery to fsnotify.
Errors are queued via mempools and queue_work to avoid holding filesystem locks in the notification path; unmount waits for pending events to drain. A new super_operations::report_error callback lets filesystem drivers respond to file I/O errors themselves (to be used by an upcoming XFS self-healing patchset).
On the uapi side, EFSCORRUPTED and EUCLEAN are promoted from private per-filesystem definitions to canonical errno.h values across all architectures""
-
#VFS support for generic I/O error reporting was merged for #Linux 7.0 by @brauner
https://git.kernel.org/torvalds/c/dd466ea0029961ee0ee6e8e468faa1506275c8a9
""Filesystems currently have no standard mechanism for reporting metadata corruption and file I/O errors to userspace via fsnotify. Each filesystem (xfs, ext4, erofs, f2fs, etc.) privately defines EFSCORRUPTED, and error reporting to fanotify is inconsistent or absent entirely.
This introduces a generic fserror infrastructure built around struct super_block that gives filesystems a standard way to queue metadata and file I/O error reports for delivery to fsnotify.
Errors are queued via mempools and queue_work to avoid holding filesystem locks in the notification path; unmount waits for pending events to drain. A new super_operations::report_error callback lets filesystem drivers respond to file I/O errors themselves (to be used by an upcoming XFS self-healing patchset).
On the uapi side, EFSCORRUPTED and EUCLEAN are promoted from private per-filesystem definitions to canonical errno.h values across all architectures""
-
#VFS support for generic I/O error reporting was merged for #Linux 7.0 by @brauner
https://git.kernel.org/torvalds/c/dd466ea0029961ee0ee6e8e468faa1506275c8a9
""Filesystems currently have no standard mechanism for reporting metadata corruption and file I/O errors to userspace via fsnotify. Each filesystem (xfs, ext4, erofs, f2fs, etc.) privately defines EFSCORRUPTED, and error reporting to fanotify is inconsistent or absent entirely.
This introduces a generic fserror infrastructure built around struct super_block that gives filesystems a standard way to queue metadata and file I/O error reports for delivery to fsnotify.
Errors are queued via mempools and queue_work to avoid holding filesystem locks in the notification path; unmount waits for pending events to drain. A new super_operations::report_error callback lets filesystem drivers respond to file I/O errors themselves (to be used by an upcoming XFS self-healing patchset).
On the uapi side, EFSCORRUPTED and EUCLEAN are promoted from private per-filesystem definitions to canonical errno.h values across all architectures""
-
#VFS support for generic I/O error reporting was merged for #Linux 7.0 by @brauner
https://git.kernel.org/torvalds/c/dd466ea0029961ee0ee6e8e468faa1506275c8a9
""Filesystems currently have no standard mechanism for reporting metadata corruption and file I/O errors to userspace via fsnotify. Each filesystem (xfs, ext4, erofs, f2fs, etc.) privately defines EFSCORRUPTED, and error reporting to fanotify is inconsistent or absent entirely.
This introduces a generic fserror infrastructure built around struct super_block that gives filesystems a standard way to queue metadata and file I/O error reports for delivery to fsnotify.
Errors are queued via mempools and queue_work to avoid holding filesystem locks in the notification path; unmount waits for pending events to drain. A new super_operations::report_error callback lets filesystem drivers respond to file I/O errors themselves (to be used by an upcoming XFS self-healing patchset).
On the uapi side, EFSCORRUPTED and EUCLEAN are promoted from private per-filesystem definitions to canonical errno.h values across all architectures""
-
Support for non-blocking timestamp updates in the #vfs was merged for #Linux 7.0 by @brauner:
https://git.kernel.org/torvalds/c/74554251dfc9374ebf1a9dfc54d6745d56bb9265
""[…] commit 66fa3cedf16a [made] non-blocking direct writes impossible on file systems with granular enough timestamps, which in practice means all of them.
This reworks the timestamp update path to propagate IOCB_NOWAIT through ->update_time so that file systems which can update timestamps without blocking are no longer penalized. […]XFS implements non-blocking timestamp updates by using the new ->sync_lazytime and […]""
-
Support for non-blocking timestamp updates in the #vfs was merged for #Linux 7.0 by @brauner:
https://git.kernel.org/torvalds/c/74554251dfc9374ebf1a9dfc54d6745d56bb9265
""[…] commit 66fa3cedf16a [made] non-blocking direct writes impossible on file systems with granular enough timestamps, which in practice means all of them.
This reworks the timestamp update path to propagate IOCB_NOWAIT through ->update_time so that file systems which can update timestamps without blocking are no longer penalized. […]XFS implements non-blocking timestamp updates by using the new ->sync_lazytime and […]""
-
Support for non-blocking timestamp updates in the #vfs was merged for #Linux 7.0 by @brauner:
https://git.kernel.org/torvalds/c/74554251dfc9374ebf1a9dfc54d6745d56bb9265
""[…] commit 66fa3cedf16a [made] non-blocking direct writes impossible on file systems with granular enough timestamps, which in practice means all of them.
This reworks the timestamp update path to propagate IOCB_NOWAIT through ->update_time so that file systems which can update timestamps without blocking are no longer penalized. […]XFS implements non-blocking timestamp updates by using the new ->sync_lazytime and […]""
-
Support for non-blocking timestamp updates in the #vfs was merged for #Linux 7.0 by @brauner:
https://git.kernel.org/torvalds/c/74554251dfc9374ebf1a9dfc54d6745d56bb9265
""[…] commit 66fa3cedf16a [made] non-blocking direct writes impossible on file systems with granular enough timestamps, which in practice means all of them.
This reworks the timestamp update path to propagate IOCB_NOWAIT through ->update_time so that file systems which can update timestamps without blocking are no longer penalized. […]XFS implements non-blocking timestamp updates by using the new ->sync_lazytime and […]""
-
Either someone found the vanilla #linux-next builds fpr #s390x useful, which I enabled a few days ago in my #Fedora Linux #copr[1] – or it was just some AI crawler that made the number in the download stats go up from 0 to 32. 🤷
These days you never know. #moderntimes #kernel #LinuxKernel
[1] https://copr.fedorainfracloud.org/coprs/g/kernel-vanilla/next/
-
@thorsten4future Danke🌿 Weisst du ich erlebe diesen Film gerade in live! #prüf
-
@thorsten4future Danke🌿 Weisst du ich erlebe diesen Film gerade in live! #prüf