Slackware-13.37 vs Slackware-14

Philip Lacroix · 06-27-2013, 12:29 PM

Quote:

Originally Posted by rng

Also, there was a problem in having write access to ntfs partitions.

Did you mount them using ntfs-3g? This gives you write access to ntfs filesystems (unless you use the ro option).

Code:

ntfs-3g [-o option[,...]] volume mount_point
mount -t ntfs-3g [-o option[,...]] volume mount_point

Philip

rng · 06-27-2013, 12:52 PM

I asked this in a separate thread: http://www.linuxquestions.org/questi...os-4175467172/

Kallaste · 06-27-2013, 08:05 PM

Quote:

Originally Posted by hitest

Slackware-current is amazing right now.

+1. Sure is working for me!

STDOUBT · 06-27-2013, 08:05 PM

Quote:

Originally Posted by rng

Are there any major disadvantages of slackware-13.37 at this time?

Since no one has addressed this, I would like to say that 13.37 still gets security updates, so from that perspective, the answer seems to be "no".
However, in 13.37, Firefox is held back to 17.0.6 (ESR) since (I assume this is the reason) Firefox 21 lamentably requires GConf.

The inclusion of NetworkManager and GConf in 14.0 caused me much grieving and agitation, and I'm still considering a return to 13.37 for my personal machine.

volkerdi · 06-27-2013, 08:39 PM

Quote:

Originally Posted by STDOUBT

Since no one has addressed this, I would like to say that 13.37 still gets security updates, so from that perspective, the answer seems to be "no".
However, in 13.37, Firefox is held back to 17.0.6 (ESR) since (I assume this is the reason) Firefox 21 lamentably requires GConf.

It actually requires python-2.7, and an upgrade to that would require recompiling a large number of other packages.

And on that note... I've been struggling with firefox-22.0 here for a few days. On 14.0, it crashes immediately under KDE if oxygen-gtk2 is installed (see https://bugs.kde.org/show_bug.cgi?id=321679). Unless a solution can be found, 14.0 will have to move to the ESR release as well.