|
Code:
I am not saying you are not honest: you need to prove it before I can use multilib in a production environment. |
Oh, i remember!
Anyone try to use backuppc server? i use it some times, and it looks very good free backup solution for various situations, including laptops with dynamic IP, supports samba, nfs, restoring files from client side via web -interface, incrementals, deduplications, and so on. some years ago, i try compile backuppc inder slackware ( 11.0 or similar version - maybe even 10.2), and cannot get success. for that reason i used debian for my backuppc server, because in debisan backuppc is in packages, and easy install. i think, if backuppc soft be available for slack, it be very good thing! it consumes small space, but gives big possibilities! |
Systemd just to see what the fuss is about :)
|
Quote:
|
Quote:
|
Quote:
That's one of the great things about Slackware. You can recreate it from scratch if you really want to, because everything which was used to obtain the final product is provided to you. It is the only Linux distribution which installs the complete build environment by default, as well as providing the complete set of build scripts, source code and any patches which were applied. Disclaimer: I've never rebuilt Slackware, and nor do I see a need to. Been using it for almost 14 years, and my house is still standing, so I figure that it must be OK... Do you personally know Steve Ballmer or Tim Cook? If not, how do you know that you can "trust" Microsoft Windows or MacOSX? Answer: You don't. They don't provide their source code or build scripts. There could be anything in the "binary only" operating systems they provide. Try to get this level of information from Microsoft or Apple: http://slackware.com/~alien/multilib/source/. Eric spells out all of the problems you might encounter and how to overcome them, down to which lines to edit in which files... and why! What else do you want? |
imlib2 could be pretty fun in the Slackware tree. ^.^
|
like to see a link to vmlinuz-generic
I do this some times when repackaging the kernel create a link to vmlinuz-generic-xxxxx link to vmlinuz-generic it makes things simple for my lilo and grub installs.
I just have to remmeber to create an initrd.img first. This is a old thread but I think it is a good one. just like the vmlinuz-huge-xxx link to vmlinuz. food for thought. |
I add "-generic" as CONFIG_LOCALVERSION when I build my kernel, and then have a lilo entry as follows:
Code:
########################################################################kernel-3.10.y-generic-3.10.50-x86_64-1_local which also contains the kernel's modules. I find it easier to manage than the way the stock packages are done. |
Just food for thought, I wonder if there's any packages in Slackware that could effectively be removed without any penalty?
|
I guess that lots of the smaller ones in A/ and AP/ can be removed without creating a missing dependency for other programs. A lot of the stuff in D/ can be removed safely, all of KDE/ KDEI/ TCL/ XFCE/ and Y/ as well. The K/ too if you are not going to build new kernels or kernel modules. Many of the progams in XAP/ have no interdependencies.
I would be more careful with packages in L/ N/ and X/ although the real critical libraries are duplicated in the a/aaa_elflibs package. Eric |
I mean any packages that could be removed without any noticeable different in a full installation that would effectively trim Slackware up without sacrificing too much.
As it is Slackware is big as an installation. Adding more in only would bloat the system. |
There should be an official LQ drinking game.
Bloat ............. drink 3 cans of gassy weak lager |
I don't think I can stomach Hieneken anymore... thanks but no thanks.
|
Quote:
Code:
root@T61:~# echo "output" | awk '{print}' |
| All times are GMT -5. The time now is 06:56 PM. |