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.
@Kikinovak: I see that you plan to include system-wide adblocking in MLED, which I would personally consider a great addition. It might be worth considering a system based on a dnsmasq + pixelserv approach instead of browserplugins such as adblock plus that you mention.
This type of system-level approach works great for me as it prevents children to switch it off, etc. Moreover it has the advantage that it is indepedent of the browser someone is using. Drawback with my own quick and dirty approach is that it is hard to do whitelisting when needed as that requires manual editing of the adblock file dsnmasq uses. However it appears that others have solved this (see below).
@Kikinovak: I see that you plan to include system-wide adblocking in MLED, which I would personally consider a great addition. It might be worth considering a system based on a dnsmasq + pixelserv approach instead of browserplugins such as adblock plus that you mention.
This type of system-level approach works great for me as it prevents children to switch it off, etc. Moreover it has the advantage that it is indepedent of the browser someone is using. Drawback with my own quick and dirty approach is that it is hard to do whitelisting when needed as that requires manual editing of the adblock file dsnmasq uses. However it appears that others have solved this (see below).
For school and SME networks, I'm already using the Squid + SquidGuard + SquidAnalyzer solution, along with categorized URL lists provided by the University of Toulouse. This solution is "industrial-grade" and works perfectly. The proxy is setup on a Linux router and works transparently with Iptables redirection.
I fully agree if people understand what Adblock is there for and hence leave it switched on. Too often I found desktops here at home on which it got switched off by family members, with all associated crap showing. Yet they come to me to fix it.
Hence my personal preference for the filtering at the system level, without going for a full industrial grade approach as that is overkill for a desktop. So far I can't complain about the pixelserv approach on my desktops...just need to figure out at some point howto make it work with NetworkManager on my laptop.
I'm not sure whether this is a bug or a feature, but I think this is what bit me when trying MLED out on a PC with an nvidia-card. This machined initially failed to boot, which I fixed with a nomodeset option in lilo.conf thinking the card was too new for 14.1. Unfortunately I didn't really explore further at that time and I needed that machine to test a hard-disk for RMA which needed Windows.
Now that I looked in more detail I see that in your tagfiles you remove both xf86-video-nouveau and xf86-video-nv from the x-series. However I don't see the nvidia-driver in the MLED repositories or a recommendation to install it in the install or migration guide. Does hardware acceleration for nvidia-cards indeed get installed somewhere, or is the removal of nouveau by default a mistake?
Now that I looked in more detail I see that in your tagfiles you remove both xf86-video-nouveau and xf86-video-nv from the x-series. However I don't see the nvidia-driver in the MLED repositories or a recommendation to install it in the install or migration guide. Does hardware acceleration for nvidia-cards indeed get installed somewhere, or is the removal of nouveau by default a mistake?
As I stated earlier in this thread, MLED is not Ubuntu. Meaning there's nothing to hold your hand when actually configuring the system, e. g. networking, video, audio, etc. I blacklisted the nouveau drivers since I never use them, I always configure the proprietary NVidia drivers. On a side note, with ATi/AMD it's the other way around, where I prefer the free radeon drivers to the proprietary fglrx drivers.
This being said, I think I will mention it somewhere in the Installation Guide.
This being said, I think I will mention it somewhere in the Installation Guide.
I would recommend this as this is a clear deviation from the Slackware install and moreover leads to a non-booting system if you don't install the nvidia proprietary drivers. This is hence likely to bite someone badly if not explicitly warned.
I used to think this until I started reading about uBlock. AdBlock Plus is just way too resource hungry. On large pages, it can actually take longer to open the page without ads than with them and it can cause a lot more RAM to be used. The developer of uBlock specifically set out to provide an option that uses less resources than AdBlock Plus. Have a look here for more info (with additional links at the bottom of that page if you want more info). And it has a decent list of pre-enabled blocklists, but it has a lot of additional ones you can enable (although, I haven't found a need to do so). It is also interesting to note that Mozilla noticed the increased memory usage of ABP and made a blog post on it (stating that for many, the extra RAM usage is worth it, but they're trying to inform the public that Firefox's large memory footprint isn't always due to Firefox itself, but rather addons people have installed).
Also, note that uBlock code ran into some issues with a turnover, so the uBlock you want is called uBlock Origins (you want the one by the original github author, gorhill, not chrisaljoudi).
Hey kikinovak what repos you using now with slackpkg+ because for a long time now I get gpg problems by bass that and i get dead urls so let us know.mled 64 14.1 KDE multi-lib. thanks.
Hey kikinovak what repos you using now with slackpkg+ because for a long time now I get gpg problems by bass that and i get dead urls so let us know.mled 64 14.1 KDE multi-lib. thanks.
what your saying is your enterprise that supported KDE. http://www.linuxquestions.org/questi...ed-4175486821/
no longer supporting it. so this means what. I mean what do we do format go ubuntu. Or have you made plans for us to merge back into slackwares kde.
so this means what. I mean what do we do format go ubuntu. Or have you made plans for us to merge back into slackwares kde.
I'm not sure if I understand you correctly, but if you want to turn your existing MLED installation into an updated MLED installation, here's a guide that I wrote and that will help you:
I know the how to i just set it up burn my cd that way not a problem. The problem is you add a kde to your enterprise and now you have gone back to only supporting xfce4 ? http://www.linuxquestions.org/questi...ed-4175486821/
I have been using MLED on one of my systems. I really like it and intend to deploy it on some of the other systems I support. I am having one issue, though, which is that firefox sometimes crashes. I'm assuming it is MLED related because I do not experience it on any of my other systems. The crashes are random. Do you have any ideas about this?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.