| Age | Commit message (Collapse) | Author |
|---|
|
|
|
correctly yet.
|
|
|
|
|
|
|
|
local/{functions,scripts} where they belong.
|
|
|
|
|
|
|
|
tree.
|
|
|
|
|
|
config/includes.binary_debian-installer for consistency with the other include directories.
|
|
archive structure.
|
|
|
|
|
|
binary environment.
|
|
proxies set them throught the apt pseudo-proxy options, and people using real proxies use config/environment.{chroot,binary} to set them.
|
|
order to ensure to take only the latest packages into account that get into the image, regardless if they come from the archive or are localy included.
|
|
consistency with the different hdd images later on.
|
|
|
|
|
|
chroots environment.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
since only firmware available within the configured archive area is included automatically, see manpage.
|
|
added and included in the source images.
|
|
While the actual firmware packages are automatically detected,
it is handy to have the firmware-linux meta package included
if non-free is enabled. That way, future upgrades to newer kernels
will keep having all available firmware packages pulled in too.
|
|
|
|
|
|
system.
|
|
|
|
needed for proper firmware package placement.
|
|
for proper firmware package placement.
|
|
debian-installer.
|
|
|
|
|
|
|
|
ubuntu mode.
|
|
been fixed in unstable.
|
|
syslinux theme packages.
|
|
multiple dots in the filename.
|
|
avoid other packages failing on non-existing fstab.
|
