You are not logged in.
I'm sure it's been discussed, either behind the scenes or on here, but a quick search didn't turn up the discussion.
Given the number of newer machines with no optical drive at all, & the likely age of machines with only a CD drive & no ability to boot from USB, I'm asking because I'm wondering if it's worth the bother this time around.
Yes I still own a machine that could use a CD & not a DVD, but for those rare cases, I'm wondering if we should point people at the same method that's being used for the current experimental installs, i.e. a bare Debian netinstall, followed by the metapackage or the netinstall script, once it's updated.
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
Good question. There hasn't been a lot of discussion.
After the main iso is made, I plan to run the usual build scripts and tweaks that squeezed the file size down to 700MB and see what comes out. Debian gets bigger every release so there's a good chance it'll be way over with no hope of slimming it down. In that case, if we still want a 32bit "lite" iso, we can just release it as something to put on a usb stick I guess.
Don't plan to go to a huge degree of bother, but some kind of slightly-lighter-weight iso is probably worth having, no?
Let's see what other people have to say about this...
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
It's like the periodic table, every element gets heavier.
Harder to slim down.
I'm sure there'll be demand for a lightweight version, one thing I'd personally think was a bad idea to drop from such an iso's live session content would be GParted. that comes in very handy if people want to resize Windows to make space to actually install, & I know Windows has native tools to do it, but frankly GParted is somewhat more intuitive, more reliable too in my experience. It also saves people having to create a whole second "GParted Live" disk/stick...
I'm sure others will chime in, now it's been mentioned.
If people really want actual CD size images to burn coasters with, a 2 cd set is possible, live session on one, installer on the other...
Last edited by Bearded_Blunder (2022-01-22 07:39:49)
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
^Gparted likely the last candidate to be dropped from a lightweight live/installer. Relax.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
For older machines which usually are 32 bit then just include the basics along with the installer. Include some recovery tools as well in case users need to do recovery tasks on their older machines from that cd.
Real Men Use Linux
Offline
This is our current package list for the "lite" metapackage:
alsa-utils,
amd64-microcode,
anacron,
apt-transport-https,
arandr,
arj,
at,
at-spi2-core,
bash-completion,
btrfs-progs,
chntpw,
colordiff,
conky-all,
cpufrequtils,
cryptsetup,
curl,
crda,
dbus-user-session,
dbus-x11,
dillo,
dmz-cursor-theme,
dosfstools,
efibootmgr,
eject,
evince,
f2fs-tools,
fbxkb,
feh,
file-roller,
firmware-b43-installer,
firmware-b43legacy-installer,
firmware-linux,
firmware-realtek,
firmware-iwlwifi,
fonts-inconsolata,
fonts-liberation,
fuse3,
galculator,
galternatives,
gddrescue,
gdebi,
gigolo,
gmrun,
gnome-keyring,
gparted,
gsimplecal,
gtk2-engines-pixbuf,
gvfs,
gvfs-backends,
gvfs-fuse,
hardinfo,
hdparm,
hddtemp,
hfsprogs,
htop,
hwdata,
i965-va-driver,
intel-microcode,
inxi,
jgmenu,
less,
libinput-tools,
libpam-gnome-keyring,
libnotify-bin,
libqt5svg5,
lightdm,
lightdm-gtk-greeter,
lightdm-gtk-greeter-settings,
light-locker,
lm-sensors,
locales,
lsb-release,
lshw,
lvm2,
lxappearance,
mlocate,
modemmanager,
mousepad,
mpv,
network-manager,
network-manager-gnome,
nitrogen,
ntfs-3g,
obconf,
openbox,
openssh-client,
p7zip-full,
pavucontrol,
pciutils,
pcmciautils,
pnmixer,
policykit-1,
policykit-1-gnome,
pulseaudio,
python3,
python3-xdg,
qt5-style-plugins,
rfkill,
ristretto,
rsync,
rxvt-unicode,
rzip,
scrot,
smartmontools,
suckless-tools,
sudo,
synaptic,
thunar,
thunar-archive-plugin,
thunar-gtkhash,
thunar-volman,
tint2,
transmission-gtk,
unace,
unalz,
unar,
unrar,
unzip,
update-inetd,
usb-modeswitch,
usbutils,
user-setup,
uuid-runtime,
va-driver-all,
wireless-tools,
xbindkeys,
xcape,
xdg-user-dirs,
xdg-utils,
xfburn,
xfce4-clipman,
xfce4-notifyd,
xfce4-power-manager,
xfsprogs,
xinput,
xorg,
xsel,
xserver-xorg-input-all,
xserver-xorg-input-synaptics,
xserver-xorg-input-evdev,
xserver-xorg-input-wacom,
xserver-xorg-video-all,
xserver-xorg-video-intel,
xserver-xorg-video-qxl,
xsettingsd,
xz-utils,
yad,
zip,
bunsen-common,
bunsen-configs-lite,
bunsen-conky,
bunsen-docs,
bunsen-exit,
bunsen-fortune,
bunsen-images,
bunsen-keyring,
bunsen-paper-icon-theme,
bunsen-pipemenus,
bunsen-themes,
bunsen-thunar,
bunsen-utilities,
bunsen-welcome
Either cut that down further, while still keeping some kind of system that's usable out of the box, or else have an additional "meta-bunsen-base" metapackage that leaves it up to the user to install some of the essential tools (like a web browser)? Then decide which of -lite or -base goes in the 32-bit installer?
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
I'm wondering if we should point people at the same method that's being used for the current experimental installs, i.e. a bare Debian netinstall, followed by the metapackage or the netinstall script, once it's updated.
Yes, seems like a reasnoble solution.
Offline