Conceivable systemd workarounds v0.9
A 0.90 revision on the thread 'brasero requires gvfs'. I see several viable options for those of us having to deal with systemd in Debian. I'll be upfront right from the startx; YMMV. 1. The obvious default choice is to deal with systemd as it is. In other words, "Try it, you'll like it, you're stuck with it anyway, now delve into it so you can configure and use it properly." 2. Use previously mentioned fixes for the systemd that is already installed in jessie. For example, removing systemd-logind if you don't need anything that depends on gnome-settings-daemon, libpam-systemd, lighttpd, live-config-systemd, sogo, systemd-cron, systemd-dbg, systemd-sysv, or systemd-ui ; apt-get removing binaries for non-gdm3 or non-lightdm X-display managers that require systemd libraries (such as libpam-systemd) ; installing and configuring systemd-shim together with sysvinit-core while you still can. On the last example, there is a running thread 'The future with Systemd' on the Debian User Forums (http://forums.debian.net/viewtopic.php?f=20&t=116860&start=60 ) that may prove to be helpful here. YMMV as above. 3. Revert from jessie/testing back to wheezy/stable and keep it at wheezy as long as possible using regularly scheduled apt-get updating. Practically speaking this means that you'd have to back up your jessie system and fully re-install wheezy from the beginning. To put it fairly mildly, such a reversion would be vastly simpler for single-user desktop systems than for complex multi-user and/or server systems. 4. Based upon post linked at https://lists.debian.org/debian-user/2014/09/msg00323.html, there are several full re-installation "escape route" alternatives. Subject: Re: brasero requires gvfs Date: Sun, 7 Sep 2014 14:09:04 -0400 On Sun, 07 Sep 2014 08:57:30 -0700 Carl Johnson wrote: > Steve Litt writes: > > > On Sun, 07 Sep 2014 09:31:46 +0200 > > Sven Joachim wrote: > > > >> > The concept of free software has become a myth :( > >> > >> There is always Gentoo if libraries you consider useless bother > >> you. Binary distributions tend to enable all possibly useful > >> features. > >> > >> Cheers, > >>Sven > > > > Gentoo isn't the only alternative. Just in case Jessie turns out to > > be unworkable for me when it goes stable, last night I made a very > > nice OpenBSD desktop computer that had most of what somebody could > > want on a desktop. However, try as I might, I couldn't get Sigil to > > compile on OpenBSD, and my business depends on Sigil for the next > > year or so. > > > > So what I'm now considering, as an escape route if systemd causes > > everything to go to hell in a handbasket (and we don't know whether > > that will happen), is that my main desktop is OpenBSD, with a > > virtual machine running Debian or Ubuntu in a VM in order to use > > Sigil and anything else I can't get to work on OpenBSD. > > > > I feel much better now that I know I have a Plan B. > > There is a FreeBSD port listed for sigil. If you don't want to run > FreeBSD, you could at least look at what their port does to get it to > compile. 4a and 4b. The Gentoo and OpenBSD alternatives are mentioned immediately above. 4c. There is also the Debian GNU/kFreeBSD alternative that similarly doesn't rely on systemd at the present time, see https://wiki.debian.org/Debian_GNU/kFreeBSD. Debian GNU/kFreeBSD uses the kernel of FreeBSD instead of the Linux kernel. 4d. There is the Slackware Linux alternative that relies on BSD-init instead of systemd at the present time. As an FYI, the links http://www.slackware.com/~alien/slackbuilds/sigil/ and http://slackbuilds.org/repository/14.1/office/sigil/ demonstrate that there is a maintained Sigil port for Slackware. 4e. Ubuntu and Ubuntu-derived distros such as Linux Mint are alternatives that might stave off for an indefinite while the immediate introduction of systemd. I'm certain that others can think of even more and better alternatives here. Again as before, YMMV. Cheers! -- Go Open Source Software Bears! _ Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com Join Linux Discussions! --> http://Community.LinuxWaves.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140908122918.43c65...@m0048138.ppops.net
Full CD ISO image of Testing for USB Booting?
Hey advanced Debian users, I would like to use a full CD ISO image of Testing/Wheezy (e.g., one of the downloaded CD images from an /iso-cd subfolder of [1]) to make a bootable USB stick onto a 1 GB, 2 GB or larger capacity stick. Several related questions really, all related to Section 4.3 of the Debian GNU/Linux Installation Guide, 'Preparing Files for USB Memory Stick Booting'[2] 1. How may I use the instructions in this Debian GNU/Linux Installation Guide while still retaining the capacity to put extra files on the same drive?? E.g., storing downloaded documents in various formats listed in the 'Installation Guide'[3] onto the same USB stick AFTER the bootable USB stick has already been created?? The reason for asking is that Section 4.3.1 of the Installation Guide 'Preparing a USB stick using a hybrid CD or DVD image' seems to indicate that once the recommended commands # cp debian.iso /dev/sdX # sync .. are carried out onto /dev/sdX, it may be impossible(?) to add new files onto the same device. Yes there are the instructions in Section 4.3.3. 'Manually copying files to the USB stick — the flexible way', but that too has its drawbacks, see question 3 below. 2. When is it better to use the command sequence 'dd if= of= bs=4M; sync' to make a bootable USB stick from the full CD ISO image rather than the pair of commands listed above from Section 4.3.1 of the Installation Guide?? The Frequently Asked Questions section 'How do I write a CD image to a USB flash drive?'[4] recommends this 'dd' method, although this too may make it impossible(?) to add new files onto the same default /dev/sdX device. 3. How could I use the steps listed in Section 4.3.3 'Manually copying files to the USB stick — the flexible way' for an EXT3 or EXT4 formatted USB device /dev/sdX1 (Linux type 82 partition) instead of for a FAT16-formatted device?? Besides requiring a FAT16-formatted drive, Section 4.3.3 also requires the installation+use of the dosfstools, syslinux and mtools packages for this method of creating a bootable USB onto /dev/sdX1. Again, the purpose of all this is use a full CD ISO image of Testing/Wheezy to make a bootable USB stick onto a 1 GB, 2 GB or larger capacity stick with room to spare for documentation files (e.g., files stored on /dev/sdX2) My preferences at this point would be to (a) use the 'dd' command to image-copy the full CD ISO onto a Linux type 82 partitioned /dev/sdX1 for USB-booting and then AFTERWARDS partition+format a separately accessible /dev/sdX2 for various stored files, if this is at all possible (b) use the steps listed in Section 4.3.3 'Manually copying files to the USB stick — the flexible way' adapted for an EXT3 or EXT4 formatted /dev/sdX1 bootable USB, and then afterwards partition+format a separately accessible /dev/sdX2 for various stored files (c) proceed with the steps listed in Section 4.3.3 for Manually copying files to the USB stick including the full CD ISO onto a bootable /dev/sdX1 (giving full consideration to its diskspace requirements), even though this REQUIRES FAT16 and its various MBR prepping tools, then separately partitioning+formatting a /dev/sdX2 with ext3 or ext4 as I please for storing extra files. Any further good recommendations?? Numbered References: [1] http://cdimage.debian.org/cdimage/weekly-builds/ [2] http://www.debian.org/releases/testing/i386/ch04s03.html.en [3] http://www.debian.org/releases/testing/installmanual [4] http://www.debian.org/CD/faq/#write-usb -A -- R.I.P. Aaron Swartz, January 11, 2013 YOU ARE NOT FORGOTTEN!! -- _ Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com Join Linux Discussions! --> http://Community.LinuxWaves.com
Multiple CD ISO-image USB Booting?
Thanks for previous responses concerning [1] and [2] on direct image-copying of Debian-Testing for USb booting. Single CD ISO-images of Testing boot fine on small USB drives using dd/cat/cp for copying the image to /dev/sdX. Another question I have is whether multiple images of Testing can be effectively used to boot a 4GB+ USB drive?? A common-use scenario for this is to have the capability to boot up separate instances (in their less-technical sense) of a particular architecture's desktops on the same portable USB drive, e.g., i386 KDE, i386 Xfce, i386 Lxde with an initial boot menu offering the bootup choices of any of these three full installation images. Theoretically, multiple *architectures* could also coexist and be made bootable on the same USB drive capacity-permitting, e.g., mixed ISOs of amd64, i386, ia64, ...etcetera. 'dd' imaging doesn't seem to allow for multiboot selection. Syslinux's EXTLINUX [3] "could" allow for multiboot selection using a decidedly *mounted* ext2/ext3/ext4/btrfs-formatted USB drive. Some [4] recommend that ext4 USB drives be preferably formatted using the command sequence 'mke2fs -t ext4 -O ^has_journal /dev/sdX1', although ext3 is probably the safest course here in case of any doubt. UNetbootin [5] allows native Testing/Wheezy onto USB through using EXTLINUX [6] on an ext2/ext3 partition (/dev/sdX1, /dev/sdX2,... ??) Perhaps instructions using UNetbootin and Syslinux for multibooting distros other than Debian's [7] can be easily adapted for EXTLINUX to boot multiple but separate desktop instances of Testing/Wheezy on ext2/ext3-formatted partitions instead of using the default fat32 format ?? Open to further hints here. -A Refs: [1] Re: Full CD ISO image of Testing for USB Booting?, http://lists.debian.org/debian-user/2013/01/msg00576.html [2] Re: Full CD ISO image of Testing for USB Booting? [3] Syslinux's EXTLINUX, http://www.syslinux.org/wiki/index.php/EXTLINUX [4] Sysresccd Manual's 'Installation from Linux using an ext3/ext4 filesystem', http://www.sysresccd.org/Sysresccd-manual-en_How_to_install_SystemRescueCd_on_an_USB-stick#D.29_Installation_from_Linux_using_an_ext3.2Fext4_filesystem [5] UNetbootin site, http://unetbootin.sourceforge.net/ [6] UNetbootin 'how it works' page, http://sourceforge.net/apps/trac/unetbootin/wiki/howitworks [7] 'MultiBootin With UNetbootin. A Multiboot Flash Drive Tutorial', http://tazbuntu.blogspot.com/2009/05/multibootin-with-unetbootin.html -- R.I.P. Aaron Swartz, January 11, 2013 YOU ARE NOT FORGOTTEN!! -- _ Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com Join Linux Discussions! --> http://Community.LinuxWaves.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130122212803.27b10...@resin03.mta.everyone.net
Reducing size of /lib following an 'apt-get upgrade'?
Have Debian Wheezy installed and recently performed an 'apt-get upgrade' to kernel 3.2.0 (3.2.0-2-686-pae in full). The system is a single-boot/Debian-only x86 machine with an intentionally-limited 400MB root partition (/), besides larger and separate partitions of /var, /usr, /home, /opt, /tmp, and swap. Before the 'apt-get upgrade', the root partition took up approximately 230MB space out of the 400MB initially allocated for this. Following the upgrade, the root partition is now 305MB full (~76% used up), with /lib taking up more than 250MB of this space. This system uses an initrd to boot its kernel (initrd.img-3.2.0-2-686-pae). Don't wish to mess up the current partition table, but *DO* wish to eventually upgrade the system with a higher kernel version, so ===> Which files and folders can one successfully mv out of /lib to a larger partition of a similar filesystem, i.e., through space-conserving symlinks (ln -sf), to reduce the size imprint of /lib ?? Any good ideas for this short of an absolute necessity to resize the root partition? TYIA, -A -- _ Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com Join Linux Discussions! --> http://Community.LinuxWaves.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120326170804.197c8...@m0005299.ppops.net
Re: Squeeze Release ?
* Subject: Re: Squeeze Release ?
* From: Ken Heard
* Date: Fri, 27 Nov 2009 13:36:37 -0500
Brent Clark wrote:
> Does anyone know if Squeeze is going be Frozen in December or
> know of anything for that matter.
No announcement of a freeze yet, but read the following:
-
The Debian Project http://www.debian.org/
Debian adopts time-based release freezes pr...@debian.org
July 29th, 2009 http://www.debian.org/News/2009/20090729
-
Debian decides to adopt time-based release freezes
The Debian project has decided to adopt a new policy of time-based
development freezes for future releases, on a two-year cycle.
...
...
--
For someone wanting a Debian installation now WITHOUT having to perform future
extensive steps such as running 'apt-get upgrade' once the new Squeeze is
("soon") released from its frozen status, is it better to
1. Install the _current_ debian-stable ("Lenny" v5.0.7) right now ??
-or-
2. Install the _current_ "Squeeze" (debian-testing) right now ??
In other words, the goal here is an up-to-date Debian install that AVOIDS the
need to perform future extensive steps such as 'apt-get upgrade' once Squeeze
is released as the new Debian "Stable".
Thanks for feedback.
_
Get your FREE, LinuxWaves.com Email Now! --> http://www.LinuxWaves.com
Join Linux Discussions! --> http://Community.LinuxWaves.com
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20101202113827.7a2f1...@resin12.mta.everyone.net
