Jigdo is the preferred way of downloading and maintaining debian ISOs for those who can't use torrents (e.g. company policies etc.). The advantage is that you only need to download what has changed since you last used jigdo, thus saving on traffic.
What I'm showing here is also described on the debian website -- my contribution is just to provide another, perhaps more detailed, example.
Anyway, it's fairly easy to use jigdo:
sudo apt-get install jigdo-file
mkdir ~/debiso
cd ~/debiso
jigdo-lite
Pick a url from here: http://www.debian.org/CD/jigdo-cd/#which
I'll use a jigdo file for amd64 testing by clicking here http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-cd/ and picking the following url:
http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-cd/debian-testing-amd64-CD-1.jigdo
You also need to pick a mirror -- your country mirror or a nearby university are good choices. I picked ftp://ftp.au.debian.org/debian.
Here's how it works:
me@beryllium:~/jigdo$ jigdo-lite
Jigsaw Download "lite"
Copyright (C) 2001-2005 | jigdo@
Richard Atterer | atterer.net
Loading settings from `/home/me/.jigdo-lite'
-----------------------------------------------------------------
To resume a half-finished download, enter name of .jigdo file.
To start a new download, enter URL of .jigdo file.
You can also enter several URLs/filenames, separated with spaces,
or enumerate in {}, e.g. `http://server/cd-{1_NONUS,2,3}.jigdo'
jigdo [http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-cd/debian-testing-amd64-CD-1.jigdo]: http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-cd/debian-testing-amd64-CD-1.jigdo
Not downloading .jigdo file - `debian-testing-amd64-CD-1.jigdo' already present
-----------------------------------------------------------------
Images offered by `http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-cd/debian-testing-amd64-CD-1.jigdo':
1: 'Debian GNU/Linux testing "Wheezy" - Official Snapshot amd64 CD Binary-1 20120220-05:20 (20120220)' (debian-testing-amd64-CD-1.iso)
Further information about `debian-testing-amd64-CD-1.iso':
Generated on Mon, 20 Feb 2012 05:33:08 +0000
-----------------------------------------------------------------
If you already have a previous version of the CD you are
downloading, jigdo can re-use files on the old CD that are also
present in the new image, and you do not need to download them
again. Mount the old CD ROM and enter the path it is mounted under
(e.g. `/mnt/cdrom').
Alternatively, just press enter if you want to start downloading
the remaining files.
Files to scan:
-----------------------------------------------------------------
The jigdo file refers to files stored on Debian mirrors. Please
choose a Debian mirror as follows: Either enter a complete URL
pointing to a mirror (in the form
`ftp://ftp.debian.org/debian/'), or enter any regular expression
for searching through the list of mirrors: Try a two-letter
country code such as `de', or a country name like `United
States', or a server name like `sunsite'.
Debian mirror [http://sluglug.ucsc.edu/debian/]: ftp://ftp.au.debian.org/debian
Downloading .template file
--2012-02-28 10:22:04-- http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-cd/debian-testing-amd64-CD-1.template
Resolving cdimage.debian.org (cdimage.debian.org)... 2001:6b0:e:2018::138, 2001:6b0:e:2018::163, 130.239.18.163, ...
Connecting to cdimage.debian.org (cdimage.debian.org)|2001:6b0:e:2018::138|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 48901055 (47M) [text/plain]
Saving to: `debian-testing-amd64-CD-1.template'
100%[===================================================================================================================================================>] 48,901,055 4.92M/s in 15s
2012-02-28 10:22:19 (3.16 MB/s) - `debian-testing-amd64-CD-1.template' saved [48901055/48901055]
[....]
FINISHED --2012-02-28 10:37:02--
Total wall clock time: 4.1s
Downloaded: 3 files, 311K in 2.4s (128 KB/s)
Found 3 of the 3 files required by the template
Successfully created `debian-testing-amd64-CD-1.iso'
-----------------------------------------------------------------
Finished!
The fact that you got this far is a strong indication that `debian-testing-amd64-CD-1.iso'
was generated correctly. I will perform an additional, final check,
which you can interrupt safely with Ctrl-C if you do not want to wait.
OK: Checksums match, image is good!
All the necessary packages are downloaded so it takes a while. Once it's done, the iso is automatically built.
If you want to update your iso - delete it and run jigdo-lite again.
Lindqvist - a blog about Linux and Science. Mostly.
28 February 2012
83. Configuring route for multiple network interfaces on Debian Testing
In my previous post I got rid of network-manager.
On my main desktop, which serves as a gateway for two subnets and serves them with access to the internet and has three ifs (eth0 goes to outside world, eth1 serves 192.168.0-127 and provides inet passthrough, eth2 serves 192.168.128-255), I had issues getting the internet connection to work once network-manager was gone -- the issue was the routing table.
Here's what I did to diagnose and solve it:
When I got rid of network manager I set up my /etc/network/interfaces like this:
sudo route -n
A quick fix is to do
sudo route add default dev eth0
which adds this as the first line:
Turns out you can just add the route options to your /etc/network/interfaces file
The script gives us a nice, compact routing table on doing
sudo service networking restart
sudo route -n
Edit::
An earlier version of this post used a separate script (see below). This works fine on boot. However, sudo service networking restart
does not invoke it -- so you may end up with a faulty route table. Thus, it is preferable to use the method above in which the route options are added to the end of /etc/network/interfaces
The following (below) is kept for posterity only:
We put the commands below into /etc/routing_table.sh:
On my main desktop, which serves as a gateway for two subnets and serves them with access to the internet and has three ifs (eth0 goes to outside world, eth1 serves 192.168.0-127 and provides inet passthrough, eth2 serves 192.168.128-255), I had issues getting the internet connection to work once network-manager was gone -- the issue was the routing table.
Here's what I did to diagnose and solve it:
When I got rid of network manager I set up my /etc/network/interfaces like this:
auto loBut it gives
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet static
address 192.168.1.1
netmask 255.255.255.0
gateway 192.168.1.1
auto eth2
iface eth2 inet static
address 192.168.1.129
netmask 255.255.255.128
gateway 192.168.1.129
sudo route -n
Kernel IP routing tableThe problem is that I DON'T want all traffic via eth2 and eth1. I want the default gateway to be my eth0. Inverting the order of the ifs in /etc/network/interfaces doesn't fix it either.
Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.129 0.0.0.0 UG 0 0 0 eth2 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1 0.0.0.0 XXX.XXX.XXX.254 0.0.0.0 UG 0 0 0 eth0 XXX.XXX.XXX.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.1.128 0.0.0.0 255.255.255.128 U 0 0 0 eth2
A quick fix is to do
sudo route add default dev eth0
which adds this as the first line:
Destination Gateway Genmask Flags Metric Ref Use IfaceIt looks like we might want to manually configure route.
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 eth0
Turns out you can just add the route options to your /etc/network/interfaces file
auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp auto eth1 iface eth1 inet static address 192.168.1.1 netmask 255.255.255.0 gateway 192.168.1.1 auto eth2 iface eth2 inet static address 192.168.1.129 netmask 255.255.255.128 gateway 192.168.1.129 auto wlan0 iface wlan0 inet static address 192.168.2.1 netmask 255.255.255.0 gateway 192.168.2.1 post-up ip route flush all post-up route add default dev eth0 post-up route add -net 169.254.0.0 netmask 255.255.0.0 dev eth0 metric 1000 post-up route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.1.1 eth1 post-up route add -net 192.168.1.128 netmask 255.255.255.128 gw 192.168.1.129 eth2 post-up route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1 wlan0
The script gives us a nice, compact routing table on doing
sudo service networking restart
sudo route -n
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 192.168.1.0 192.168.1.1 255.255.255.0 UG 0 0 0 eth1 192.168.1.128 192.168.1.129 255.255.255.128 UG 0 0 0 eth2
Edit::
An earlier version of this post used a separate script (see below). This works fine on boot. However, sudo service networking restart
does not invoke it -- so you may end up with a faulty route table. Thus, it is preferable to use the method above in which the route options are added to the end of /etc/network/interfaces
The following (below) is kept for posterity only:
We put the commands below into /etc/routing_table.sh:
#!/bin/sh
sudo ip route flush all
sudo route add default dev eth0
sudo route add -net 169.254.0.0 netmask 255.255.0.0 dev eth0 metric 1000
sudo route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.1.1 eth1
sudo route add -net 192.168.1.128 netmask 255.255.255.128 gw 192.168.1.129 eth2
exit 0We change the atttributes:sudo chmod o-rwx /etc/routing_table.shsudo chmod g-rwx /etc/routing_table.shsudo chmod u+rwx /etc/routing_table.shHere user is root. This way only root can execute and edit the table. I guess the 'sudo' is a bit superfluous in our script.
To make it start on boot, add a line to your /etc/rc.local
My rc.local now looks like this:The firewall-rules.sh script is described in another post on ip tables.#!/bin/sh -e echo "1" > /proc/sys/net/ipv4/ip_forward sh /etc/firewall-rules.sh sh /etc/routing_table.sh exit 0
27 February 2012
82. Getting rid of network-manager (and trying wicd) on Debian Testing
Network-manager is a fine program, but it interferes with the 'linux' way of doing things by using text files for configuration.
While network-manager makes it easy to do easy things, /etc/network/interfaces makes it easy to do everything since it makes every setting transparent.
The main problem with remove network-manager is that gnome-core depends on it. Remove network-manager, everything in gnome goes. No good, and completely unnecessary.
I'm still a bit hesitant about configuring WPA on the command line, so I want to have wicd as a backup once network manager is gone.
--START HERE --
So
sudo apt-get install wicd-cli wicd-curses wicd-gtk wpasupplicant
Turn off network-manager (temporarily) and restart your network
sudo service networking restart && sudo service network-manager stop
Start wicd-gtk and configure your wireless network (if that's what you need) to make sure that everything is in working order and you can live without network-manager.
sudo apt-get install rcconf
sudo rcconf
Uncheck network-manager and exit.
After your next reboot you can check whether network-manager has started:
sudo service network-manager status
While network-manager makes it easy to do easy things, /etc/network/interfaces makes it easy to do everything since it makes every setting transparent.
The main problem with remove network-manager is that gnome-core depends on it. Remove network-manager, everything in gnome goes. No good, and completely unnecessary.
I'm still a bit hesitant about configuring WPA on the command line, so I want to have wicd as a backup once network manager is gone.
--START HERE --
So
sudo apt-get install wicd-cli wicd-curses wicd-gtk wpasupplicant
Turn off network-manager (temporarily) and restart your network
sudo service networking restart && sudo service network-manager stop
Start wicd-gtk and configure your wireless network (if that's what you need) to make sure that everything is in working order and you can live without network-manager.
sudo apt-get install rcconf
sudo rcconf
Uncheck network-manager and exit.
update-rc.d: using dependency based boot sequencingYou can use sysv-rc-conf instead. Don't worry about the warning about the LSB default -start values -- (2 3 4 5) just means that by default network-manager should be running at runlevels 2-5 (i.e. normal operation). 0 would be halt, 1 would effectively be rescue mode ('single-user mode') and 6 is system reboot. Anyway, here's sysv-rc-conf:
update-rc.d: warning: network-manager start runlevel arguments (none) do not match LSB Default-Start values (2 3 4 5)
update-rc.d: warning: network-manager stop runlevel arguments (0 1 2 3 4 5 6) do not match LSB Default-Stop values (0 1 6)
After your next reboot you can check whether network-manager has started:
sudo service network-manager status
[sudo] password for me:
NetworkManager is not running ... failed!
You can make wicd-gtk autostart on starting gnome:
start gnome-sessions-manager and add wicd-gtk if it isn't /already/ there.
The wicd network manager icon will show up in the notification area in gnome (lower right) instead of top right (see picture above). You can supposedly use this to move it: http://blog.norida.me/blog/2011/12/05/move-wicds-icon-to-gnome-shells-status-bar-top-bar/
Given that I use Faenza I also use this: http://gnome-look.org/content/show.php/Faenza+Wicd+Iconset?content=133821
(unzip it, go to the directory and do sh install )
Anyway, the real advantage of wicd is hat there are cli and curses versions available e.g. wicd-curses:
Links to this post:
http://eulez.blogspot.com.es/2013/07/de-ubuntu-debian.html
start gnome-sessions-manager and add wicd-gtk if it isn't /already/ there.
The wicd network manager icon will show up in the notification area in gnome (lower right) instead of top right (see picture above). You can supposedly use this to move it: http://blog.norida.me/blog/2011/12/05/move-wicds-icon-to-gnome-shells-status-bar-top-bar/
Given that I use Faenza I also use this: http://gnome-look.org/content/show.php/Faenza+Wicd+Iconset?content=133821
(unzip it, go to the directory and do sh install )
Anyway, the real advantage of wicd is hat there are cli and curses versions available e.g. wicd-curses:
Links to this post:
http://eulez.blogspot.com.es/2013/07/de-ubuntu-debian.html
Subscribe to:
Posts (Atom)