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.
Don't know if anybody has already suggested this - but I'll add my vote for PostgreSQL. Great database system and much "free'er" than others ;-). I'm perfectly happy with the SBo build - but if it could be included by default it would be great. It would also save me from having to recompile PHP for it :-)
heh, but it will force me to rebuild it without
Click here to see the post LQ members have rated as the most helpful post in this thread.
yes, but it will mean that postgresql will become a dependency of php, and I don't want to install it on my webservers.
not that I have anything against postgresql: I used it in the past with postgis for grass.
just to make an example that what makes someone happy can also make someone else sad
I'm not sure I understand. Won't just commenting out the appropriate module in php.ini allow PHP run happily even if PostgreSQL is absent (while PHP is compiled with PostgreSQL support)?
I'll also add a vote for including ntfs-3g in the install disc. It is amazing how many times I've used the Slack install disc as a quick rescue disc - and the lack of ntfs-3g / ntfs-rw capabilities is the main stumbling block I hit - having to switch instead to the install disc of that popular distro whose name starts with "U" - but I won't say which.
Then again - the Slack install disc is not really meant to be a rescue disc I guess - so I'll accept it if I'm told that's not really an appropriate request for the install disc.
Well, I tried :-)
Adding fuse to the installer seems like it might be overkill, but I can add ntfs.ko to the next update so that there's at least read-only NTFS support.
Adding fuse to the installer seems like it might be overkill, but I can add ntfs.ko to the next update so that there's at least read-only NTFS support.
Yes and this is good enough for installing slackware from a source (packages) tree on an NTFS partition. People like me who install slackware to a (destination) NTFS partition of course can "installpkg" fuse and ntfs-3g to the initrd. That is by no means a complex task.
I'll also vote for Exim (or at least Postfix, if that's your thing). I don't want to ruffle anybody's feathers - but as a sysadmin who got into Linux only in the last decade or so - I just couldn't muster enough masochism to learn Sendmail. Then again - there might be other reasons for having Sendmail around - such as legacy setups - so I'll just quietly go back to my corner :-)
I had my first computer on mid 2005, before that I was a musician (violoncellist to be exact) my knowledge about computers was zero. It took me six months to get bored of Windows (I hacked on it all what I could), I had my first linux installed on 2006. I had a web server running Slackware on 2011 using sendmail as mail server, all configured manually.
I prefer sendmail to exim or postfix.
Masochist is that human tendency to complicate things simplifying.
***
About PostgreSQL. The reason to choose MySQL is popularity. I don't know PostgreSQL but even knowing that is better I would be forced to use MySQL on my server just because is what most people use.
I'll also add a vote for including ntfs-3g in the install disc.
It has been a while, but I actually did this with the Slackware 13.1 install initrd.img so that I can PXE boot Windows machines with the installer and write to an NTFS formatted external USB drive. I have never bothered updating as subsequent versions were too large to boot on some hardware I had at the time.
I have since I upgraded the server box where I did this and so far have been unable to locate the exact details, but I believe that it was quite easy. It just required adding ntfs-3g to /bin, libntfs-3g.so to /lib and perhaps libntfs-3g.la to /usr/lib. Another nicety would be a symlink /sbin/mount.ntfs-3g -> /bin/ntfs-3g.
Dosbox would be a nice addition, not a very big program to take much space.
I know I am probably adding more fuel to the fire now, since I finally got my new Slack64 system up and running nicely, but now I would also like to throw my out there again and perhaps have multilib either in the install option or the very least in /extra.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.