I'm not sure where the .la files are for Thunar, but according to Pat, we should only be removing the files in /lib{64}/ and /usr/lib{64}/. Any others should remain in place.

1 members found this post helpful.

I'm going to second adding 'mousepad' (text editor for XFCE). Setting up a KDE-free system on my new 2in1 has proved to me just how much I actually rely on KDE apps. I think it's kind of shocking that mousepad or a similar editor isn't included in the base XFCE distribution already, but that's beside the point. If you install all packagesets except kde and kdei, you get a DE with a file-manager (Thunar), a terminal emulator (xfce4-terminal), a web browser (Firefox) and a mailreader (Thunderbird), but no *simple* graphical text editor (and no, xedit doesn't count ;-)

The only dependency that isn't in Slackware already is gtksourceview, either 2.x or 3.x (should probably be an optional dependency IMO, but again, beside the point).

3 members found this post helpful.

Leafpad works well in Xfce without additional dependencies.

http://www.slackbuilds.org/repositor...ffice/leafpad/

2 members found this post helpful.

Arguably, you already get Gvim and that Emacs GUI with Xfce. However, mousepad is more appropriate if you are using Xfce IMHO.

1 members found this post helpful.

Yes leafpad would work too. Just figured mousepad is technically an official part of xfce, in the 'apps' dir on their ftp.

Sure you get emacs and vim which have X versions. But these are very advanced editors. Users migrating from Windows or Mac would expect a more simple text editor such as Notepad for jotting down quick notes or editing config files if they haven't learned Vi or emacs yet or have no interest in doing so.

3 members found this post helpful.

While it is not part of xfce i use SciTE https://scintilla.org/SciTE.html a really nice, fast and light weight editor.

xf86-video-nouveau 1.0.16

https://lists.freedesktop.org/archiv...ry/032053.html

Since the default file system seems to be ext4, why can't this just be built-in to the generic kernel? Then, there would be no need for an initrd to be built. Those that choose other file systems or perhaps raid or luks/lvm, would still need to create the initrd. It would just eliminate a step for a large portion of users.

The initrd is not hard, nor is rebuilding a kernel with ext4 built in. I reckon I'm just getting lazy in my older age. You'd think having recently retired I'd have all the time I need......

Hi,

I haven't installed fresh system for quite some time now, but I wouldn't bet on that statement.
As far as I remember, the default fs is the one you format your drive with ;-)

--
Best regards,
Andrzej Telszewski

My crystal ball predicts that in a not_so_distant future there will be no more huge kernel shipped in Slacwkare, but an initrd will be automatically built and installed whenever needed (i.e., at end of installation and after a kernel upgrade). If this happens, no worries about ext4, if needed it will be included in the initrd.

2 members found this post helpful.

Thunderbird-60.5.0

Tarball, https://ftp.mozilla.org/pub/thunderb....source.tar.xz

What's new, https://www.thunderbird.net/en-US/th.../releasenotes/

If you have unformatted space (but partitioned), the installer will prompt you to format the partition(s) and presents you several options, and I believe the first one is ext4.

+1

It's no more 1995 where disks costs and space were a premium, now days we get 2TB sata's for under 100 bux.

Though on servers I run custom images without bloat, but include basics like fs, ether, and other needed drivers, cant remember last time I ever loaded a module

What's wrong with the initrd, excluding the users' laziness to make one? It is around of 15 years since Fedora or Ubuntu requires one, and nobody died yet because of it.

Surprisingly is only that was a need of 15 years for Slackware to invent its own way to automatize this initrd creation.

I guess, nobody looked into Arch source code, meantime? Notably, they have a fine initrd management. With hooks.

whats the point of having one... and RedHat have always had one on their desktop platform, even back to redhat desktop 3 (I started on slackware, moved to RH on desktop about 3 and stayed until they EOL'd it at 9 and turned it into that clusterf### fedora).

Just because they do it doesnt mean it is needed, it isnt, clearly, and those running servers likely are also running custom kernels without it. in 2019 , heh, even if it way 2009, i'd still be saying, there is no point.

1 members found this post helpful.