Re: [gentoo-user] file system for new machine
On 28/4/23 21:21, Michael wrote: On Friday, 28 April 2023 13:54:37 BST Peter Humphrey wrote: On Friday, 28 April 2023 10:08:01 BST Philip Webb wrote: 230428 Peter Humphrey wrote: On Thursday, 27 April 2023 13:23:01 BST Philip Webb wrote: I've built & tested the new machine I was planning in 2022 & am at the point of designing the partitions. For many years, I've used Reiserfs, but it is now obsolescent, so I need to choose an alternative. Reiserfs seemed appropriate for a system with a large number of small files. Ext4 seems to be used by well-known binary distros. What would others recommend ? It depends: is this a UEFI machine? No, it isn't. I await your recommendation with bated breath (smile). In that case I have nothing to add to others' suggestions; sorry. :) It used to be the case btrfs would suffer corruption if you ran out of space. I don't know if this is the same today. Anecdotally, I've run out of space and the fs did not become corrupt on that partition. It corrupted another time though, but thankfully no significant data loss happened after I ran btrfs scrub, followed by btrfs check. Now I'm getting this warning on dmesg, but I have no idea what it means: BTRFS warning (device sdb3): devid 1 physical 0 len 4194304 inside the reserved space and the same on 3 other partitions on the same disk. :-/ NOTE: I don't recall ever having problems with ext4, for many years now. Filesystem choice is very much to do with your particular use case. I am not a fan of ext4 - lost too much data too many times. I ve found btrfs and xfs much tougher, and the online tools much more convenient. That said btrfs has its less than stellar moments. I still have systems that use ext4 and they "seem" reliable for light duty but I make sure I have backups and do not trust them with anything important - been bitten too many times! BillK
[gentoo-user] Re: chromium and dbus...
On 2023-04-28, jul...@jroy.ca wrote: > What login manager and DE/WM are you using? If you're using a WM, > it's your own reponsibility to setup dbus when starting your > session. A DE will do this for you. > > Typically, you can start your WM using `dbus-run-session `, at > least for Wayland. I'm not familiar with X11 but maybe you can use > the same command. > > That said, I'm not sure dbus is the problem with chromium, since > you're still having the same network error when starting it with > `dbus-launch chromium`... I have always seen lots of dbus errors from chromium and chrome (and various other apps). I don't run a "desktop environment", don't use a display manager, and don't start my WM (openbox) with a dbus session. There are probably some features of chromium/chrome that don't work because of that (but I don't know what they might be). Neither has ever any stability issues for me. Dbus does seem to auto-start and work enough that Thunderbird can tell me of incoming e-mails with desktop notifications... $ chromium [3339:3365:0428/52.793404:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [3339:3365:0428/52.794422:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [3339:3365:0428/52.847772:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [3339:3365:0428/52.847804:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [3339:3365:0428/52.882407:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [3339:3365:0428/52.882447:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [3339:3498:0428/53.007404:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files [3339:3498:0428/53.007565:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files [3339:3498:0428/53.007720:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files [3339:3363:0428/54.521351:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [3339:3339:0428/54.521447:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [3339:3363:0428/54.521569:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [3339:3339:0428/54.521635:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [3339:3363:0428/54.521753:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [3339:3339:0428/54.521816:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [3339:3363:0428/54.521933:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [3339:3339:0428/54.521992:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [3339:3363:0428/54.522125:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") [3339:3339:0428/54.522186:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: INFO: Created TensorFlow Lite XNNPACK delegate for CPU. > > Have you seen https://github.com/systemd/systemd/issues/3 ? > > The last comment sounds pertinent: >>
Re: [gentoo-user] chromium and dbus...
On Fri, 2023-04-28 at 11:15 -0400, Alan Grimes wrote: > So basically this is just a hack-layer to get around the inherent > fact > that linux is garbage. I don't think shitting on Linux will attract a lot of help on this mailing list. Nevertheless... > Dbus is in my runlevels and shows no errors when I poke it with the > script in /etc/init.d What login manager and DE/WM are you using? If you're using a WM, it's your own reponsibility to setup dbus when starting your session. A DE will do this for you. Typically, you can start your WM using `dbus-run-session `, at least for Wayland. I'm not familiar with X11 but maybe you can use the same command. That said, I'm not sure dbus is the problem with chromium, since you're still having the same network error when starting it with `dbus-launch chromium`... Have you seen https://github.com/systemd/systemd/issues/3 ? The last comment sounds pertinent: > after update package dev-libs/icu to version 72.1 and rebuild > chromium, chromium work well. > > Maybe an incompatible icu version caused this problem. -- Julien signature.asc Description: This is a digitally signed message part
[gentoo-user] Re: chromium and dbus...
On 2023-04-28, Alan Grimes wrote: > A decenently good OS would provide an IPC mechanism and little else. =| > So basically this is just a hack-layer to get around the inherent fact > that linux is garbage. Then one might wonder why you don't stop using it. -- Grant
[gentoo-user] chromium and dbus...
It looks like chromium has no freakin idea how to use dbus... A decenently good OS would provide an IPC mechanism and little else. =| So basically this is just a hack-layer to get around the inherent fact that linux is garbage. Dbus is in my runlevels and shows no errors when I poke it with the script in /etc/init.d I've been limping along on Konqueror and it is generating completely routine dbus traffic no issues: atg@tortoise ~ $ dbus-monitor --session [] signal time=1682692275.716176 sender=:1.5 -> destination=(null destination) serial=339394 path=/KonqHistoryManager; interface=org.kde.Konqueror.HistoryManager; member=notifyHistoryEntry array of bytes [ 00 00 00 68 00 68 00 74 00 74 00 70 00 73 00 3a 00 2f 00 2f 00 77 00 77 00 77 00 2e 00 66 00 72 00 65 00 65 00 64 00 65 00 73 00 6b 00 74 00 6f 00 70 00 2e 00 6f 00 72 00 67 00 2f 00 77 00 69 00 6b 00 69 00 2f 00 49 00 6e 00 74 00 72 00 6f 00 64 00 75 00 63 00 74 00 69 00 6f 00 6e 00 54 00 6f 00 44 00 42 00 75 00 73 00 2f ff ff ff ff ff ff ff ff 00 00 00 01 00 00 00 00 00 25 89 9f 02 41 f0 04 00 00 00 00 00 00 25 89 9f 02 41 f0 04 00 00 00 00 08 00 3a 00 31 00 2e 00 35 ] signal time=1682692276.678553 sender=:1.5 -> destination=(null destination) serial=339395 path=/KonqHistoryManager; interface=org.kde.Konqueror.HistoryManager; member=notifyHistoryEntry array of bytes [ 00 00 00 68 00 68 00 74 00 74 00 70 00 73 00 3a 00 2f 00 2f 00 77 00 77 00 77 00 2e 00 66 00 72 00 65 00 65 00 64 00 65 00 73 00 6b 00 74 00 6f 00 70 00 2e 00 6f 00 72 00 67 00 2f 00 77 00 69 00 6b 00 69 00 2f 00 49 00 6e 00 74 00 72 00 6f 00 64 00 75 00 63 00 74 00 69 00 6f 00 6e 00 54 00 6f 00 44 00 42 00 75 00 73 00 2f ff ff ff ff 00 00 00 24 00 49 00 6e 00 74 00 72 00 6f 00 64 00 75 00 63 00 74 00 69 00 6f 00 6e 00 54 00 6f 00 44 00 42 00 75 00 73 00 00 00 00 00 00 00 00 00 25 89 9f 02 41 f3 c6 00 00 00 00 00 00 25 89 9f 02 41 f3 c6 00 00 00 00 08 00 3a 00 31 00 2e 00 35 ] method call time=1682692306.604101 sender=:1.82 -> destination=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello Today's update did nothing to chromium. Apparently by doing nothing whatsoever, I managed to make the only system in the world that can't run chromium in this way but seems fine on all other apps. =\ -- Beware of Zombies. =O #EggCrisis #BlackWinter White is the new Kulak. Powers are not rights.
[gentoo-user] Re: Gcc 13.1 and chromium
On 27/04/2023 21:40, Alan Grimes wrote: I rebuilt my system on gcc 13.1. I think the compiler is good but it exposed some bugs in a handful of packages, these are: Tracker bugs are always useful for knowing what will break before you upgrade: https://bugs.gentoo.org/865117
Re: [gentoo-user] file system for new machine
On Friday, 28 April 2023 13:54:37 BST Peter Humphrey wrote: > On Friday, 28 April 2023 10:08:01 BST Philip Webb wrote: > > 230428 Peter Humphrey wrote: > > > On Thursday, 27 April 2023 13:23:01 BST Philip Webb wrote: > > >> I've built & tested the new machine I was planning in 2022 > > >> & am at the point of designing the partitions. > > >> For many years, I've used Reiserfs, but it is now obsolescent, > > >> so I need to choose an alternative. Reiserfs seemed appropriate > > >> for a system with a large number of small files. > > >> Ext4 seems to be used by well-known binary distros. > > >> What would others recommend ? > > > > > > It depends: is this a UEFI machine? > > > > No, it isn't. I await your recommendation with bated breath (smile). > > In that case I have nothing to add to others' suggestions; sorry. :) It used to be the case btrfs would suffer corruption if you ran out of space. I don't know if this is the same today. Anecdotally, I've run out of space and the fs did not become corrupt on that partition. It corrupted another time though, but thankfully no significant data loss happened after I ran btrfs scrub, followed by btrfs check. Now I'm getting this warning on dmesg, but I have no idea what it means: BTRFS warning (device sdb3): devid 1 physical 0 len 4194304 inside the reserved space and the same on 3 other partitions on the same disk. :-/ NOTE: I don't recall ever having problems with ext4, for many years now.
Re: [gentoo-user] file system for new machine
On Friday, 28 April 2023 10:08:01 BST Philip Webb wrote: > 230428 Peter Humphrey wrote: > > On Thursday, 27 April 2023 13:23:01 BST Philip Webb wrote: > >> I've built & tested the new machine I was planning in 2022 > >> & am at the point of designing the partitions. > >> For many years, I've used Reiserfs, but it is now obsolescent, > >> so I need to choose an alternative. Reiserfs seemed appropriate > >> for a system with a large number of small files. > >> Ext4 seems to be used by well-known binary distros. > >> What would others recommend ? > > > > It depends: is this a UEFI machine? > > No, it isn't. I await your recommendation with bated breath (smile). In that case I have nothing to add to others' suggestions; sorry. :) -- Regards, Peter.
Re: [gentoo-user] file system for new machine
230428 Peter Humphrey wrote: > On Thursday, 27 April 2023 13:23:01 BST Philip Webb wrote: >> I've built & tested the new machine I was planning in 2022 >> & am at the point of designing the partitions. >> For many years, I've used Reiserfs, but it is now obsolescent, >> so I need to choose an alternative. Reiserfs seemed appropriate >> for a system with a large number of small files. >> Ext4 seems to be used by well-known binary distros. >> What would others recommend ? > It depends: is this a UEFI machine? No, it isn't. I await your recommendation with bated breath (smile). Thanks to everyone else who has replied. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] file system for new machine
On Thursday, 27 April 2023 13:23:01 BST Philip Webb wrote: > I've built & tested the new machine I was planning in 2022 > & am at the point of designing the partitions. > > For many years, I've used Reiserfs, but it is now obsolescent, > so I need to choose an alternative. Reiserfs seemed appropriate > for a system with a large number of small files. > Ext4 seems to be used by well-known binary distros. > > What would others recommend ? It depends: is this a UEFI machine? -- Regards, Peter.
Re: [gentoo-user] file system for new machine
On 27.04.23 14:23, Philip Webb wrote: I've built & tested the new machine I was planning in 2022 & am at the point of designing the partitions. For many years, I've used Reiserfs, but it is now obsolescent, so I need to choose an alternative. Reiserfs seemed appropriate for a system with a large number of small files. Ext4 seems to be used by well-known binary distros. What would others recommend ? I usually have a boot partition with ext2, a root partition containing everything that is necessary for booting on ext4 and everything else on zfs. Andreas
