You are not logged in.
Here are some more config changes I had to make to get squid-deb-proxy to work.
Path: /etc/squid-deb-proxy/mirror-dstdomain.acl
# mirror-dstdomain.conf
#
# network destinations that are allowed by this cache
# the default mirror names on debian are ftp[0-9]*\.[a-z]+\.debian\.org
# but that would require (slow) regexp matching, so for now we allow
# www.debian.org and friends here too
.debian.org
cdn.debian.net
http.debian.net
httpredir.debian.org
# default mirrors
#ftp.debian.org
security.debian.org
# additional destinations can be added to the directory:
# /etc/squid-deb-proxy/mirror-dstdomain.acl.d
Path: /etc/squid-deb-proxy/mirror-dstdomain.acl.d/20-extra [a new file]
# Devuan mirrors
.devuan.org
us.mirror.devuan.org
# Grml mirrors
.grml.org
deb.grml.org
# U.S. Debian mirrors
debian.gtisc.gatech.edu
ftp-chi.osuosl.org
mirror-0.csail.mit.edu
ftp-nyc.osuosl.org
Adjust the above to fit your situation.
Phil
@phil - what do you find better with squid-deb-proxy?
For me, apt-cacher-ng was flakey, and one of the features simply didn't work. When I was doing some research on the matter I found comments by others who had similar experiences with apt-cacher-ng. That research also led me to squid-deb-proxy, which I decided to try. After I figured out how to configure it, it has been working without problems. I did have a problem with it once, but it was probably my fault -- I installed it on a fresh system and it refused to start up using the old cache. After I deleted the old cache and let it create a new one, everything was fine.
Also, getting live-build to work with squid-deb-proxy was simple.
From my /etc/live/build.conf file:
# The line below is for squid-deb-proxy.
LB_APT_HTTP_PROXY="http://localhost:8000/"
LB_MIRROR_BOOTSTRAP="http://packages.devuan.org/merged"
LB_MIRROR_CHROOT_SECURITY="http://packages.devuan.org/merged"
LB_MIRROR_BINARY="http://packages.devuan.org/merged"
LB_MIRROR_BINARY_SECURITY="http://packages.devuan.org/merged"
Phil
I briefly played with apt-cacher-ng, but ended up dumping it. I am now using squid-deb-proxy instead.
Phil
Hi David,
Instead of an antivirus, considering using these things instead: AppArmor, FireHOL, Firejail, and NoScript or uBlock Origin.
Phil
Hi,
Even Tiny Core Linux would be (way) too big for that ancient machine. The EPROM in that computer only holds 32 KB of data!
Have you seen this website?:
http://www.web8201.com/
Phil
The version of live-build in Devuan Jessie is broken -- it tries to install live-config-systemd, which then fails.
Here's the workaround:
$ lb config -d jessie
$ sed -i 's|live-config-systemd|live-config-sysvinit|' config/package-lists/live.list.chroot
$ echo "sysvinit-core" >> config/package-lists/live.list.chroot
$ sudo lb build
This should also be helpful:
# The line below is for squid-deb-proxy.
#LB_APT_HTTP_PROXY="http://localhost:8000/"
LB_MIRROR_BOOTSTRAP="http://packages.devuan.org/merged"
LB_MIRROR_CHROOT_SECURITY="http://packages.devuan.org/merged"
LB_MIRROR_BINARY="http://packages.devuan.org/merged"
LB_MIRROR_BINARY_SECURITY="http://packages.devuan.org/merged"
That goes here:
/etc/live/build.conf
If you're using squid-deb-proxy, uncomment the second line and edit it (if needed).
Phil
I just used live-build ten days ago to build a default Devuan ISO. And according to the package list, there are no systemd files on it, not even libsystemd0. I did have to use a "trick" to get it to build, though. In the past I encountered the same problem that you did, but this time around I was more persistent and found the solution/workaround. More on that shortly...
Phil
Hi,
What is the reason for switching from live-build to live-sdk?
Phil