SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There is definitely something wrong with SeaMonkey (2.39) or down the path.
I have clean installation of -current on ThinkPad R60 and SeaMonkey sometimes crashes there.
On another computer (ThinkPad T520i, Slackware 14.1) I have recompiled SeaMonkey with -Os and it still crashes, most often when attaching form's files.
On yet another computer (NUC5i3RYB, Slackware-current), guess what, it sometimes crashes
@pamu1 and atelszewski: this has already been requested, see posts #143 and #144.
I would add to my previous answer (#145) that as current has already been tagged beta 1 it could be too late now.
Fulfilling these requests would need changes, not in the installer itself but rather in the installed system, like adding caller scripts in /var/log/setup (the easy part) and config scripts in /usr/sbin or /sbin (the real work).
Maybe someone has a config script to propose? That could help, if not to fulfill the request for this development cycle, at least folks who prefer to change their boot loader or boot manager after installation (as some already do), possibly provided with a SlackBuild.
As a single script it could also be grabbed from an USB stick just after installation (before rebooting), then run after bind mounting dev, proc and sys like e.g. "chroot /mnt grubconfig" or "chroot /mnt/ extlinuxconfig". Just my
Last edited by Didier Spaier; 01-24-2016 at 07:30 AM.
@Didier I'm not pressing, I know at what stage we are already
And yes, it's quite some work to script-in all this stuff, so lets leave it for the moment.
I have NUC5i3RYB board and I came across BIOS setting that makes LILO fail to boot, but extlinux has no problems; that's the reason I switched to extlinux (the setting is about the amount of memory assigned to graphics, if set to something like 512MB, then LILO fails, it's not a real problem for the moment, as you can leave the memory at low level, LILO will boot and then the OS will adjust the needed amount of memory, but for me it marked the EOL for LILO and I wanted to move to something simple and operational, and extlinux seems to be the one).
Mplayer 1.2.1 is compatible with the FFmpeg 2.8.x releases. The tarball includes a copy of FFmpeg 2.8.5 (the latest at this date), so you don't need to fetch it separately.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.