Re: Raising volume past 100%
On Sun, 21 Aug 2022, Curt wrote: On 2022-08-18, David Griffith wrote: What I seek is 1) the ability to hover the mouse pointer over the volume applet and raise the volume past 100% using the mouse wheel and 2) the ability to click on the volume applet and use the slider that appears to raise the volume past 100%. I already know how to bring up a dialog to do this. I was able to do #1 before an untimely wipe and reinstall and am having trouble figuring out just what I did. A pulse audio applet called 'pasystray' can seemingly reach astronomical heights: However, pasystray lets you go up "forever". At least I never hit a ceiling. The only thing is that it doesn't exactly have a volume control slider. You go to the applet and use the mouse scroll wheel to go up/down. https://www.reddit.com/r/archlinux/comments/287cu3/raise_max_volume_above_150/ I'm pretty sure that was it! Thanks! My fiddling around with ~/.asoundrc was a red herring. Now I feel a compulsion to figure out if Alsa can be made to do what this thing does. Unlike what I've been trying with Alsa, this doesn't result in any distortion until you start up into the range where the physical amplifier starts clipping. But at least on my machinery, that's far higher than where I want the volume o o o *| |\ | | ) |__|/ -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Raising volume past 100%
On Fri, 19 Aug 2022, Cindy Sue Causey wrote: On 8/19/22, David Griffith wrote: I don't want to go through multiple clicks and the open/close of a dialog box. Sometimes I get files/streams that are so quiet that even the max provided by that method of 153% is not enough. I don't want a dialog popping over what I'm doing. I was previously able to do exactly what I wanted, so I know that it's possible. Also, I have come across repeated requests on how to do what I'm trying to rediscover, so I'd like to get the answer put out there for them. Hi.. This thread caught my eye because I'd been having trouble for a couple weeks. Have you always had this trouble, or is this something that just started happening in the last few weeks? Am asking because I started having a problem. I just assumed "Not Gonna Take It Anymore" blew out the speakers on my newest secondhand laptop. Might still be what happened, but it's that part about how low it is that makes me wonder. Mine's so low, I have to lean completely against the laptop to hear anything. Again, it's likely the hardware, but it's sure a funny coincidence to see that very thing stated on here, too. pavucontrol is my weapon of choice to get anything resembling sound. Didn't used to work for me. Had been using aumix for years then it stopped working. Now pavucontrol(-qt) works mostly dependably, although I have to log out and back in a couple times a week when it doesn't make its connection(s) for currently unknown reasons. For me, this problem seems to have started maybe six or seven years ago and has been getting progresively worse. Maybe automated normalization could help, but that's something I'd rather not get into any time soon. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Raising volume past 100%
On Fri, 19 Aug 2022, Bret Busby wrote: On 19/8/22 03:04, David Griffith wrote: On Fri, 19 Aug 2022, Bret Busby wrote: On 19/8/22 01:32, David Griffith wrote: My reply is at the bottom. Please put your reply there too. On Thu, 18 Aug 2022, Bret Busby wrote: On 18/8/22 16:15, David Griffith wrote: There is the continuing problem of built-in speakers on laptops being too quiet when running Linux. I managed to fix this with something in /etc/asound.conf and an extra mate-volume-control applet added to the panel. With this extra volume control, I was able to turn the audio far past 100% and even past 153%. The laptop I'm working on needed to be wiped and the OS reinstalled. Unfortunately I neglected to save or write down what I did to implement this volume control tweak. Before I discovered this, I used /etc/asound.conf (or ~/.asoundrc) to add a "Pre-Amp" slider to Alsa. This raises up the low end such that the really quiet audio stuff is loud enough. I'm not sure if that had anything to do with the volume control tweak. Would someone please help me with figuring out what I could have possibly done to make MATE's audio control applet to go as far past 100% as I cared to raise it? Do you have access to the MATE Control Center, through the applications menu? If so, in there, is the Hardware -> Sound settings configurator Also, in System -> Preferences -> Hardware -> Sound Whilst this is on a UbuntuMATE system, I expect that you should, if you are using the MATE desktop environment, have access the same way, to the same functionalities. I'm on a regular Debian system. What you pointed me to is the same thing that I get if I right-click on the volume control applet and select "sound preferences". I'm not clear on what I'm supposed to see there as it has no visible options to raise the maximum volume. 1. As a person whom strictly bottom posts as a rule, and, as this was clearly shown in the message above, your comment at the top of the message, is not appreciated. Sorry. That tag has been part of my reply header for some time. I'll reword it. 2. See attachment. The slider goes past 100%, which, from your wording in your request, is what I understand that you seek. What I seek is 1) the ability to hover the mouse pointer over the volume applet and raise the volume past 100% using the mouse wheel and 2) the ability to click on the volume applet and use the slider that appears to raise the volume past 100%. I already know how to bring up a dialog to do this. I was able to do #1 before an untimely wipe and reinstall and am having trouble figuring out just what I did. What is wrong with simply bringing up the Sound preferences window, and clicking on the position of the marker on the slider, and dragging it to the position wanted? Your original query did not specify that you wanted instead, to be using a mouseover and the mouse wheel, instead of the buttons on the mouse. I don't want to go through multiple clicks and the open/close of a dialog box. Sometimes I get files/streams that are so quiet that even the max provided by that method of 153% is not enough. I don't want a dialog popping over what I'm doing. I was previously able to do exactly what I wanted, so I know that it's possible. Also, I have come across repeated requests on how to do what I'm trying to rediscover, so I'd like to get the answer put out there for them. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Raising volume past 100%
On Fri, 19 Aug 2022, Bret Busby wrote: On 19/8/22 01:32, David Griffith wrote: My reply is at the bottom. Please put your reply there too. On Thu, 18 Aug 2022, Bret Busby wrote: On 18/8/22 16:15, David Griffith wrote: There is the continuing problem of built-in speakers on laptops being too quiet when running Linux. I managed to fix this with something in /etc/asound.conf and an extra mate-volume-control applet added to the panel. With this extra volume control, I was able to turn the audio far past 100% and even past 153%. The laptop I'm working on needed to be wiped and the OS reinstalled. Unfortunately I neglected to save or write down what I did to implement this volume control tweak. Before I discovered this, I used /etc/asound.conf (or ~/.asoundrc) to add a "Pre-Amp" slider to Alsa. This raises up the low end such that the really quiet audio stuff is loud enough. I'm not sure if that had anything to do with the volume control tweak. Would someone please help me with figuring out what I could have possibly done to make MATE's audio control applet to go as far past 100% as I cared to raise it? Do you have access to the MATE Control Center, through the applications menu? If so, in there, is the Hardware -> Sound settings configurator Also, in System -> Preferences -> Hardware -> Sound Whilst this is on a UbuntuMATE system, I expect that you should, if you are using the MATE desktop environment, have access the same way, to the same functionalities. I'm on a regular Debian system. What you pointed me to is the same thing that I get if I right-click on the volume control applet and select "sound preferences". I'm not clear on what I'm supposed to see there as it has no visible options to raise the maximum volume. 1. As a person whom strictly bottom posts as a rule, and, as this was clearly shown in the message above, your comment at the top of the message, is not appreciated. Sorry. That tag has been part of my reply header for some time. I'll reword it. 2. See attachment. The slider goes past 100%, which, from your wording in your request, is what I understand that you seek. What I seek is 1) the ability to hover the mouse pointer over the volume applet and raise the volume past 100% using the mouse wheel and 2) the ability to click on the volume applet and use the slider that appears to raise the volume past 100%. I already know how to bring up a dialog to do this. I was able to do #1 before an untimely wipe and reinstall and am having trouble figuring out just what I did. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Raising volume past 100%
My reply is at the bottom. Please put your reply there too. On Thu, 18 Aug 2022, Bret Busby wrote: On 18/8/22 16:15, David Griffith wrote: There is the continuing problem of built-in speakers on laptops being too quiet when running Linux. I managed to fix this with something in /etc/asound.conf and an extra mate-volume-control applet added to the panel. With this extra volume control, I was able to turn the audio far past 100% and even past 153%. The laptop I'm working on needed to be wiped and the OS reinstalled. Unfortunately I neglected to save or write down what I did to implement this volume control tweak. Before I discovered this, I used /etc/asound.conf (or ~/.asoundrc) to add a "Pre-Amp" slider to Alsa. This raises up the low end such that the really quiet audio stuff is loud enough. I'm not sure if that had anything to do with the volume control tweak. Would someone please help me with figuring out what I could have possibly done to make MATE's audio control applet to go as far past 100% as I cared to raise it? Do you have access to the MATE Control Center, through the applications menu? If so, in there, is the Hardware -> Sound settings configurator Also, in System -> Preferences -> Hardware -> Sound Whilst this is on a UbuntuMATE system, I expect that you should, if you are using the MATE desktop environment, have access the same way, to the same functionalities. I'm on a regular Debian system. What you pointed me to is the same thing that I get if I right-click on the volume control applet and select "sound preferences". I'm not clear on what I'm supposed to see there as it has no visible options to raise the maximum volume. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Raising volume past 100%
There is the continuing problem of built-in speakers on laptops being too quiet when running Linux. I managed to fix this with something in /etc/asound.conf and an extra mate-volume-control applet added to the panel. With this extra volume control, I was able to turn the audio far past 100% and even past 153%. The laptop I'm working on needed to be wiped and the OS reinstalled. Unfortunately I neglected to save or write down what I did to implement this volume control tweak. Before I discovered this, I used /etc/asound.conf (or ~/.asoundrc) to add a "Pre-Amp" slider to Alsa. This raises up the low end such that the really quiet audio stuff is loud enough. I'm not sure if that had anything to do with the volume control tweak. Would someone please help me with figuring out what I could have possibly done to make MATE's audio control applet to go as far past 100% as I cared to raise it? -- David Griffith d...@661.org
APT: suggested packages are required?
I just noticed an odd behavior of APT when I tried installing inform6-compiler and inform6-library. I used to think that recommended packages would be mentioned at installation, but wouldn't be added unless you explicitly asked for them. So, I tried to install the compiler and library on a headless machine and APT decided that it had to also install a zcode interpreter and picked one that wanted to pull in all sorts of graphical libraries. Is that really necessary? Also, why is there no "inform6" package that simply installs both the compiler and standard library? -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Removing libsystemd0 from a non-systemd system
On Tue, 8 May 2018, to...@tuxteam.de wrote: On Tue, May 08, 2018 at 02:23:57AM +0300, Abdullah Ramazanoğlu wrote: Is anyone working on a mechanism to allow for install-time selection of a desired init? I brought this up a few times since systemd came to Debian, but I've never heard anything more on this. I asked that question when Jessie debuted. No one is. Certainly not Debian. The only suggestion I got was to build my own preseeded install disk, but that's not the answer -- You still have to install systemd first and convert. This is probably because Debian is commited to systemd and going that way further and further. The fact that today it is possible to convert to sysvinit is because systemd migration is still in transient. Upcoming release or the next one possibly won't even allow switching to sysvinit easily (or at all). I think that will depend on whether there are enough people willing to put in the necessary work to maintain two inits or not. I'm willing to put in the time and effort. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: regex in apt preferences
On Tue, 8 May 2018, Abdullah Ramazanoğlu wrote: On Mon, 7 May 2018 08:26:35 + (UTC) David Griffith said: Package: *systemd* Pin: release * Pin-Priority: -1 This will prevent anything requiring systemd from being accidentally installed. This also prevents libsystemd0 from being updated. Package: *systemd* Pin: release * Pin-Priority: -1 Package: libsystemd0 Pin: release a=testing Pin-Priority: 500 Second entry overrides the first one, so all *systemd* packages except libsystemd0 are given -1 priority. Through trial and error, I found that these worked in this order: Package: libsystemd0 Pin: release * Pin-Priority: 500 Package: *systemd* Pin: release * Pin-Priority: -1 In the order as you describe, EVERYTHING matching *systemd* was blocked, with no allowance for libsystemd0. When I followed your suggestion, I got this: 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. I have no clue what package is "not upgraded". Reversing the order of the pins did nothing. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: pointless systemd dependencies
On Mon, 7 May 2018, Brian wrote: [snip notes on analysing each and every systemd-touching package] I found someone who has already done most if not all of this analysis and has set up a repo containing non-systemd-using packages. Perhaps this can be used as a foundation for something official. Someone might be motivated if they could find what you are referring to. http://angband.pl/deb/archive.html This is nowhere near as radical as the Devuan approach and is something I think can be pulled into Debian proper without much hassle. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: pointless systemd dependencies
On May 7, 2018 4:39:22 AM PDT, The Wanderer <wande...@fastmail.fm> wrote: >On 2018-05-06 at 21:47, David Griffith wrote: > >> Could we start the process of identifying packages that have >> dependencies on systemd in some way that is are not actually >> required? > >This is a seriously nontrivial task. > >As I understand matters, the only sure way to do it would be something >like: > >1. Start with a systemd-free computer. > >2. Attempt to install a package. > >3. See whether it tries to install systemd, either by direct dependency >or by an indirect cascade of dependencies. > >4. If it tries to install systemd by direct dependency, analyze the >source and functionality of the package, to determine whether or not >there would be a way to get it to do what it needs to do without >referencing systemd in a way which would require the dependency. > >5. If it tries to install systemd by indirect dependency, identify the >package in the dependency chain which results in pulling in systemd, >and >then either: > >5a. Analyze that package in the same way as under step 4. > >5b. Analyze the package above that one in the dependency chain to >determine whether or not it can be made to do what it needs to do >without referencing that package in a way which would require the >dependency. > >5.b.1. If not, repeat step 5b for the next package up the chain, and >keep repeating for as many packages are in the chain. > >6. Repeat from step 2 with another package, until every package has >been >checked. > >And all of that is just to identify the packages in question. Modifying >them to remove the dependencies would be another nontrivial task in >many >cases; getting the package maintainer to accept patches which do so >would be still another nontrivial task. > > >I did notice when one package which I run on my primary (systemd-free) >computer developed an indirect dependency on libpam-systemd (as part of >fixing an arguably minor bug in a feature I don't use), reported that >as >a possible unintended result to the maintainer (asking whether there >was >any possibility of a way forward which wouldn't require me to build >that >package locally going forward in order to avoid systemd), and was >fortunate enough that the maintainer found an alternative dependency >which would avoid the indirect chain to libpam-systemd. > >But that was something I noticed in the course of checking a routine >dist-upgrade, not the result of embarking on a project to analyze the >archive in search of such packages - and even then, I was lucky that A: >an alternative solution could be found and B: the maintainer was >sufficiently non-unsympathetic to the desire to avoid systemd to be >willing to look for and implement one. > > >All of which is to say: I am not at all certain that this project would >be at all worth the time and effort it would require. > >But I am not one to tell others not to do work they think is >beneficial. > >-- > The Wanderer > >The reasonable man adapts himself to the world; the unreasonable one >persists in trying to adapt the world to himself. Therefore all >progress depends on the unreasonable man. -- George Bernard >Shaw I found someone who has already done most if not all of this analysis and has set up a repo containing non-systemd-using packages. Perhaps this can be used as a foundation for something official. -- David Griffith d...@661.org
Re: Backup problem using "cp"
On May 7, 2018 4:31:16 AM PDT, Richard Owlett <rowl...@cloud85.net> wrote: >On 05/06/2018 10:11 AM, Thomas Schmitt wrote: >> Hi, >> >> Richard Owlett wrote: >>> Thought I was doing that by specifying -x. >> >> Either cp -x has a bug or the target directory is not in a different >> filesystem than "/" and not a mount point of such a filesystem. >> >> Check the device numbers of "/" and "/media/richard/MISC...". >> E.g. like this >> >>$ stat / | fgrep Device >>Device: 803h/2051d Inode: 2 Links: 25 >>$ stat /bkp | fgrep Device >>Device: 814h/2068d Inode: 2 Links: 7 >> >> Here "/bkp" has a different device number (2068) than "/" (2051). >> So it (its inode, to be exacting) is in a different filesystem. >> >> As contrast see a directory in the same filesystem as "/": >> >>$ stat /home | fgrep Device >>Device: 803h/2051d Inode: 2228225 Links: 60 > >I get: >richard@debian-jan13:~$ stat / | fgrep Device >Device: 80eh/2062d Inode: 2 Links: 22 >richard@debian-jan13:~$ stat /media | fgrep Device >Device: 80eh/2062d Inode: 131073 Links: 5 >richard@debian-jan13:~$ > >I gather that "cp" is then an inappropriate tool. > >"tar" is inappropriate for my preferences - I was attempting to use >"cp" >as there would be multiple files &/or directories as input *and* >output. > >I suspect long term I want "rsync" [ *MUCH* reading to do! ] You will indeed want rsync. Essentially, "rsync -av [--delete] will serve most of your backup needs. -- David Griffith d...@661.org
Re: pointless systemd dependencies
On Mon, 7 May 2018, Andy Smith wrote: Hi David, On Mon, May 07, 2018 at 06:32:16AM +, David Griffith wrote: How many packages are there that could possibly need to be linked against systemd? Are you going to provide us with any examples of packages you think are needlessly linked against systemd? I expect there are some, but depending on whether they are easy or hard to find would seem like an easy first step in working out if this is a serious problem or not. to...@tuxteam.de pointed out how to get a list of packages that link to libsystemd0. I'll use that as a starting point. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
regex in apt preferences
In my saga of limiting the damage from remnents of systemd, I'm focusing in on libsystemd0. I want to allow only libsystemd0 to be upgradable and forbid the installation and/or upgrading of anything else matching *systemd*. Here's what I did so far: Following http://without-systemd.org/wiki/index.php/Debian_Stretch, it suggests adding this entry for /etc/apt/preferences.d/systemd: Package: *systemd* Pin: release * Pin-Priority: -1 This will prevent anything requiring systemd from being accidentally installed. This also prevents libsystemd0 from being updated. While I understand now that it's okay to leave it installed, not updating it bothers me. It has also resulted in a lot of confusion over apt-get(8)'s response of "1 not upgraded". So, I want to explicitly allow libsystemd0 to be upgraded. According to the apt_preferences(5) manpage in section "Regular expressions and glob(7) syntax", it seems to me that if I add a specific rule after the above rule, then libsystemd0 should be allowed yet other systemd stuff should be forbidden. For instance: Package: libsystemd0 Pin: release * Pin-Priority: 1001 But that doesn't work. All packages including libsystemd0 are blocked. Then I tried a single entry and a regex like this on the "Package:": /((?!.*libsystemd0).*systemd.*)/g or (^|[^l])(^|[^i])(^|[^b])systemd([^0]|$) Neither of these blocked anything. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: pointless systemd dependencies
On Mon, 7 May 2018, to...@tuxteam.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, May 07, 2018 at 01:47:51AM +, David Griffith wrote: Could we start the process of identifying packages that have dependencies on systemd in some way that is are not actually required? David, I understand your concerns. I, myself don't like systemd. But *if* you actually want something changed, you'll have to pick up some legwork yourself, like, for example, understand what libsystemd is actually doing in some package of your choice. But first of all, you'll have to accept that there are folks out there (who are at least as smart as you and me) who do like systemd, and that packagers want to cater to those folks as well. So if some binary wants to be able to work with systemd when it's there, perhaps linking against libsystemd is the right thing to do. A package maintainer won't keep around two versions of her package, one compiled against libsystemd and another without it. Especially because that doesn't scale well: someone might not like libdbus, someone else quibbles about libselinux -- and we are already at eight binary versions for one executable. Sometimes binary distributions do have a cost, convenient as they are. If "no systemd" purism is your thing, there's Devuan. There are pretty smart folks over there too. How many packages are there that could possibly need to be linked against systemd? -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Removing libsystemd0 from a non-systemd system
On Sun, 6 May 2018, The Wanderer wrote: On 2018-05-06 at 21:25, David Griffith wrote: What's the point of allowing libsystemd0 to exist when systemd has been purged? So that programs which interface with systemd can detect whether or not systemd is present, and fall back to alternate code paths when it's not. As I understand matters (without having actually dug into the code), that detection code literally is what libsystemd0 *is*; when systemd is present, it passes through function calls to be handled in appropriate places, and when systemd is not present, it returns an appropriate default or failure value. I was under the impression that systemd-shim provided this functionality. When I look at https://packages.debian.org/stretch/systemd-shim and https://packages.debian.org/stretch/libsystemd0, their functions appear to be identical except that the latter actually does talk to systemd if systemd is present. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
pointless systemd dependencies
Could we start the process of identifying packages that have dependencies on systemd in some way that is are not actually required? -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Removing libsystemd0 from a non-systemd system
On Sun, 6 May 2018, Patrick Bartek wrote: On Sun, 6 May 2018 02:44:16 + (UTC) David Griffith <d...@661.org> wrote: Have any advances been made in figuring out just how to remove libsystemd0 from a Debian 9 machine that's running sysvinit? The ongoing presence of libsystemd0 has caused slowly-progressing trouble with several machines of mine culminating in complete failure a couple days ago. Initially I thought this was unrelated to systemd, but now I tracked it down to systemd's remnants and the problem is progressing much faster with freshly-installed machines. First, how exactly did you convert to sysvinit, etc? And what kind of trouble? I've been running Stretch with sysvinit for almost a year -- as a personal machine, not a server -- and have had absolutely NO problems. Here's the link I used: http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_a_Debian_Stretch_installation I used the very first conversion steps, the simplest one, and none of the optional ones. No pinning. No third-party systemdless repos, etc. I still have systemd libraries including libsystemd0 for those apps that have systemd as a dependenciy. No problems. Totally removing systemd is a pain requiring third-party systemdless repos and keeping a wary eye out for problems. I did it a couple times as part of my experiments, and always had glitches. One thing did just occur to me: Are you using the GNOME desktop? I've heard stories about it and systemd. It is VERY dependent on it. I haven't used GNOME whatever version for about 7 years. I use only a window manager Openbox. I followed that same thing you did as soon as the machine was installed. I also did optional steps 2 and 3. I didn't do 1 because all the machines in question are headless. I stopped using GNOME when version 3 came out and switched to MATE for most of my desktop needs. One of the symptoms that made me think libsystemd0 had something to do with it was the output of "apt-get upgrade". It would always report "1 not upgraded" or "2 not upgraded". The trouble manifested in dependency hell and networking that would mysteriously stop for no readily apparent reason (on reboot after kernel upgrade or out of the blue). Usually networking could be regained by doing a LISH login and manually turning on the network interfaces. Then interface names started changing randomly. This was after names like "eth0" and friends were abandoned. Servers died by way of networking only working halfway, no matter what I did. I was able to ssh in and do scp and rsync transfers, but that was about it. What's the point of allowing libsystemd0 to exist when systemd has been purged? Is anyone working on a mechanism to allow for install-time selection of a desired init? I brought this up a few times since systemd came to Debian, but I've never heard anything more on this. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Removing libsystemd0 from a non-systemd system
Have any advances been made in figuring out just how to remove libsystemd0 from a Debian 9 machine that's running sysvinit? The ongoing presence of libsystemd0 has caused slowly-progressing trouble with several machines of mine culminating in complete failure a couple days ago. Initially I thought this was unrelated to systemd, but now I tracked it down to systemd's remnants and the problem is progressing much faster with freshly-installed machines. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Replace systemd
On July 5, 2017 9:11:27 AM PDT, The Wanderer <wande...@fastmail.fm> wrote: >On 2017-07-05 at 11:27, Don Armstrong wrote: > >> On Tue, 04 Jul 2017, David Griffith wrote: > >>> It would be nice to have an install-time option for selecting the >desired init. >> >> It already exists: >> >> https://lists.debian.org/debian-user/2017/04/msg00097.html >> >> « >> You can just append: >> >> preseed/late_command="in-target apt-get install -y sysvinit-core" >> >> to the installer command line. > >I suspect that what the people who ask for this are thinking of is a >step in the installer sequence at which you are prompted to choose >which >init system you want to be installed, such that the installer will >never >even attempt to install any other init system. > >This differs from the suggested methods to date not only in avoiding >"systemd-sysv was installed, then sysvinit-core replaced it later on" >(which some of the suggested methods may also do), but also in the UX; >having it presented to you as a choice, rather than having to know >about >it in advance and take separate steps on your own, makes a significant >cosmetic and psychological difference, as well as affecting >discoverability. > >If the installer doesn't present the option, then it's not really "an >install-time option" in a certain sense; it takes on more the shape of >advanced / expert hackery, rather than appearing to be something the >developers actually support. > >I think that's the mindset, anyway. > >-- > The Wanderer > >The reasonable man adapts himself to the world; the unreasonable one >persists in trying to adapt the world to himself. Therefore all >progress depends on the unreasonable man. -- George Bernard >Shaw These are exactly my motivations for an install-time prompt. -- David Griffith d...@661.org
Re: Replace systemd
On Wed, 5 Jul 2017, Don Armstrong wrote: On Tue, 04 Jul 2017, David Griffith wrote: On July 3, 2017 1:44:30 PM PDT, Martin Read <zen75...@zen.co.uk> wrote: On 03/07/17 20:42, Rory Campbell-Lange wrote: Is there a pure Debian alternative? There is an alternative init daemon, in the form of sysvinit (install the package "sysvinit-core" to use this as your init daemon), and there are several solutions for service management. It would be nice to have an install-time option for selecting the desired init. It already exists: https://lists.debian.org/debian-user/2017/04/msg00097.html « You can just append: preseed/late_command="in-target apt-get install -y sysvinit-core" to the installer command line. Or you can roll your own install media with its own syslinux.cfg which adds that or something more complicated in a preseed file. You don't need to fork the installer, or submit any patches upstream. If you want something more complicated, like not installing systemd at all, you'll have to pass --include and --exclude options to debootstrap using the base-installer/includes and base-installer/excludes preseed options; something like: base-installer/includes=sysvinit-core base-installer/excludes=systemd-sysv but that's totally untested. » I'm aware of that technique. What I was talking about is a menu option that pops up when the install is running that explicitly asks the person installing which init to use. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Re: DOSEMU DPMI unhandled exception 0e (it's back!)
On July 4, 2017 3:55:32 PM PDT, bw <apiso...@gmail.com> wrote: >>>The trouble manifested when I tried using various components of an >old release of Turbo C. >>>Everything, 16 and 32 bit, tickles this bug. > >Hey David, don't give up, i got Turbo C+ 3.0 working fine in dosbox by >setting ver to 6.00 in the dosbox.conf and using a real >MS-DOS COMMAND.COM from msdos 6. > >The only reason I ever use dosemu is for serial port, modems or old >FOSSIL stuff. dosbox is a lot easier for games and programming. > >I hope there's not some kernel issue with this, I really like my old >stuff, >especially Vern Buerg's LIST.COM combined with semware Qedit Advanced. > THE BEST two programs in history. > >Let us know how it goes, try TC on dosbox with the right command.com I'm using DOSEMU right now because I'm trying to get to the bottom of a bug in DOS Frotz. It crashes on real hardware and DOSEMU, but not DOSBOX. -- David Griffith d...@661.org
Re: Replace systemd
On July 3, 2017 1:44:30 PM PDT, Martin Read <zen75...@zen.co.uk> wrote: >On 03/07/17 20:42, Rory Campbell-Lange wrote: >> Is there a pure Debian alternative? > >There is an alternative init daemon, in the form of sysvinit (install >the package "sysvinit-core" to use this as your init daemon), and there >are several solutions for service management. > It would be nice to have an install-time option for selecting the desired init. -- David Griffith d...@661.org
Re: DOSEMU DPMI unhandled exception 0e (it's back!)
The trouble manifested when I tried using various components of an old release of Turbo C. Everything, 16 and 32 bit, tickles this bug. On July 4, 2017 7:52:36 AM PDT, bw <apiso...@gmail.com> wrote: >>When I start DOSEMU and use any DOS program, I get "DPMI: Unhandled >Exception 0e - Terminating Client" > >That is really bad news, are you sure it's all programs, and not just >programs that use DPMI ? >If the problem is only DPMI enabled programs, you can probably solve it >with some persistent effort. > >>and then I'm told that the emulator is unstable and should be >rebooted. Running any program after that causes DOSEMU to crash. > >I've used dosemu for a long time, but not on stretch, so I can't test >it right now. It is tricky to setup, as most DOS environments always >were. > >>From what I recall, some programs will require vm.mmap_min_addr set to >0 in sysctl and >you should do your own research before using this, it seems to be a >security risk on networked machines, or was at one point. >Not sure of the current state of things re: mmap_min_addr > >Some older DOS programs have a plain 16 bit ver and a 32 bit DPMI ver, >and some have a switch to turn off use of DPMI. Some also >used an environment variable to limit or control the use of DPMI. >There's also a config option in dosemu.conf to set the base address. ># DPMI base address; default: auto ># If the default value fails, try 0x1000 > ># $_dpmi_base = (auto) > >>Identical trouble was reported in https://bugs.debian.org/797378 > >That bug showed pkzip as the culprit, not all dos programs? > >If it's the same bug, maybe you should follow the links and file your >bug against the kernel instead of dosemu? >https://ugs.debian.org/cgi-bin/bugreport.cgi?bug=866965 > >Good luck, and have fun. Thanks for the heads up I will follow along >in case I run into the same issues. >bw -- David Griffith d...@661.org
DOSEMU DPMI unhandled exception 0e (it's back!)
When I start DOSEMU and use any DOS program, I get "DPMI: Unhandled Exception 0e - Terminating Client" and then I'm told that the emulator is unstable and should be rebooted. Running any program after that causes DOSEMU to crash. Identical trouble was reported in https://bugs.debian.org/797378 and attributed to a kernel bug that was fixed in 4.2.x. My Stretch machines are now running 4.9.x. What's going on here? -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Bluray Debian ISOs: Which app(s) burns bluray images?
On Mon, 19 Jun 2017, Thomas Schmitt wrote: Hi, Alan Ianson wrote: I always use a USB drive nowadays Good point: https://www.debian.org/CD/faq/#write-usb I should have mentioned the CD/DVD/BD burn item in the FAQ too: https://www.debian.org/CD/faq/#record-unix but when I did, I used K3b or wodim from the command line. I omitted wodim from my answer, because it can hardly do DVD and would do Blu-ray only by accident. One should use it only for burning CD. For completeness: There is also cdrecord, which fell into disgrace with Debian long ago. It can do BD-R and BD-RE, does not format BD-R by default, and cannot disable Defect Management on BD-RE. I've never had trouble with wodim for burning DVDs. I've never tried to burn a bluray of any kind though. I prepare my USB flash drives using the instructions found at https://www.debian.org/releases/stable/amd64/ch04s03.html.en. Using preseed.cfg files is very helpful. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
bleeding-edge MATE
I've installed MATE 1.18 into /usr/local/ and added /usr/local/share/xsessions to the sessions-director path in /etc/lightdm/lightdm.conf. At the Lightdm login screen, I can now select MATE for my desktop environment, but on logging in, MATE won't start. What's wrong? I don't see anything relevant in /var/log about this. I can start mate-session in .xinitrc and use startx, but then MATE can't find any themes... and I really would rather use Lightdm. Is anyone here tinkering with bleeding-edge MATE? How are you going about it? -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: underscore in xterm sometimes invisible
On Mon, 1 May 2017, Sven Joachim wrote: On 2017-05-01 08:58 +, David Griffith wrote: When I completely log out and log back in, the underscore character will be invisible in xterm. If I do "xrdb .Xresources", subsequent xterms created will show underscores. Investigating further, I tried starting with no .Xresources file. This gave me a much-too-small xterm window. When I do "xrdb -merge .Xresources-foobar", which is my normal .Xresources file, I get my favored xterm settings EXCEPT that underscores are invisible. If I don't use the "-merge" flag, then that will cause subsequent xterms to show underscores. What's going on here? How can I fix it? This has been reported in bug #858142[1], but I have not been able to reproduce it on my systems and I don't know what's going on. Cheers, Sven 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858142 Thanks. I've been able to add some hopefully helpful information to that bug report, to wit, I think the problem may be with xrdb(1). -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
underscore in xterm sometimes invisible
When I completely log out and log back in, the underscore character will be invisible in xterm. If I do "xrdb .Xresources", subsequent xterms created will show underscores. Investigating further, I tried starting with no .Xresources file. This gave me a much-too-small xterm window. When I do "xrdb -merge .Xresources-foobar", which is my normal .Xresources file, I get my favored xterm settings EXCEPT that underscores are invisible. If I don't use the "-merge" flag, then that will cause subsequent xterms to show underscores. What's going on here? How can I fix it? Here's my .Xresources file: xterm*faceName: DejaVu Sans Mono :antialias=true xterm*faceSize: 12 XTerm*renderFont: true XTerm*utf8: 1 xterm*vt100.initialFont: 3 xterm*loginShell: true xterm*vt100*geometry: 80x24 xterm*saveLines: 2000 xterm*charClass: 33:48,35:48,37:48,43:48,45-47:48,64:48,95:48,126:48 xterm*foreground: rgb:ee/ee/ee xterm*background: rgb:00/00/00 -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
MATE in /usr AND in /usr/local
I'm interested in tinkering with components of MATE and testing them while leaving the APT-installed versions alone. I've built and installed the components from the Github repos and installed them to /usr/local/. I can't figure out how to load applets from /usr/local. In particular, can someone tell me how to use the /usr/local version of the Workspace Switcher instead of /usr/? -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: libjasper in Stretch
On Mon, 27 Mar 2017, Sven Hartge wrote: David Griffith <d...@661.org> wrote: I also saw this https://packages.qa.debian.org/j/jasper/news/20170212T221713Z.html, which suggests that the original maintainer has stepped back up. In any case, I should perhaps convert my code from using Jasper to using OpenJPEG. But then I notice that there is no libopenjpeg5-dev in Stretch to go along with libopenjpeg5. Is this just temporary? Umm, openjpeg has also been removed from Stretch/Testing and Unstable See https://tracker.debian.org/pkg/openjpeg and https://tracker.debian.org/news/791076 It has been replaced by openjpeg2: https://tracker.debian.org/pkg/openjpeg2 Okay, now I see it. Why is the package named "openjp2-7" instead of "openjpeg2-7"? It seems to me that the latter would be easier to find. Why is/was there a "libopenjpeg5" package? -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: libjasper in Stretch
On Mon, 27 Mar 2017, Reco wrote: Hi. On Mon, Mar 27, 2017 at 12:16:25PM +, David Griffith wrote: Why is libjasper missing from Stretch? According to https://bugs.debian.org/812630 the stated reason for its removal is that libjasper has not been updated for ten years. No, actual reason for the removal was that the only package's maintainer stepped down. Quote: Due to lack of time, I'm looking for a new maintainer for this package. In this same bug report is a note that this assertion is not true and a link was provided to a Github repository. On January 25th maintainer stepped down. On October 25th (i.e. more than half-year later) someone noticed that upstream was back to life. The fact that the second assertion (i.e. 'dead upstream') was invalidated did not do anything to first (i.e. 'package unmaintained'). Nonetheless, the bug report was closed without further explanation. The explanation was provided, in fact: --- Reason --- RoQA; dead upstrem, replaced by openjpeg -- I also saw this https://packages.qa.debian.org/j/jasper/news/20170212T221713Z.html, which suggests that the original maintainer has stepped back up. In any case, I should perhaps convert my code from using Jasper to using OpenJPEG. But then I notice that there is no libopenjpeg5-dev in Stretch to go along with libopenjpeg5. Is this just temporary? -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
libjasper in Stretch
Why is libjasper missing from Stretch? According to https://bugs.debian.org/812630 the stated reason for its removal is that libjasper has not been updated for ten years. In this same bug report is a note that this assertion is not true and a link was provided to a Github repository. Nonetheless, the bug report was closed without further explanation. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
udev doesn't like systemd-shim
I switched to sysvinit by following the directions at http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_a_Debian_jessie/sid_installation This seemed to work until I tried to install sshfs whereupon I got this: E: /usr/share/initramfs-tools/hooks/udev failed with return 1 Poking around, I found that /usr/share/initramfs-tools/hooks/udev contained references to systemd. Re-adding systemd-shim didn't help. Over in #debian-n...@irc.oftc.net, I was told that I need to upgrade the packages udev and libudev1 to version 232-19, 233-4, or 233-5 because the existing package doesn't support systemd-shim. Is someone working on getting this into Stretch before the official release? -- David Griffith d...@661.org
Re: Can't make writable USB thumbdrive installer anymore
On Thu, 2 Feb 2017, Richard Owlett wrote:
On 02/01/2017 02:50 AM, David Griffith wrote:
I used to be able to make a writable USB thumbdrive installer > by
following the directions found at
https://hyper.to/blog/link/debian-installer-on-a-usb-key/,
altering the name of the release and device. Now I can't get > it to work.
[*SNIP* details]
I've snipped the details as I suspect the various readers have subconsciously
used those details to say your goals/motivations are _identical_ to theirs.
Following this thread I _read into_ your posts some {mutually contradictory}
things I've tried to do with various levels of success.
Once it's prepared, for what do you use it?
What problem did using a USB stick for the above purpose solve?
With what versions of Debian were you successful?
I worded those questions to keep out as many of my preconceptions out as
possible.
My intent is to have a USB installer flash drive to which I can add a
preseed.cfg file, non-free firmware packages, and other stuff I like to
add to a fresh machine.
It turned out that the problem was a change in syslinux's behavior that
was documented for Stretch's install instructions[1], but not for
Jessie[2]. It boiled down to the grammar of the syslinux.cfg file. For
instance, this is the old way:
default vmlinuz
append initrd=initrd.gz
This is the new way:
default vmlinuz initrd=initrd.gz
See also:
https://bugs.debian.org/803267
https://bugs.debian.org/853918
https://bugs.debian.org/853965
Footnotes:
[1] https://www.debian.org/releases/stretch/amd64/ch04s03.html.en
[2] https://www.debian.org/releases/stable/amd64/ch04s03.html.en
--
David Griffith
d...@661.org
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Re: Can't make writable USB thumbdrive installer anymore
On Thu, 2 Feb 2017, David Griffith wrote: 14) syslinux /dev/sdb1 The version of syslinux in the Wheezy repos is 4.05. The one in Jessie repos is 6.03. I built the earlier version on the Jessie machine to cover the possibility that syslinux itself is causing the problem. That hypothesis appears to be true. I'll do some poking around to see just when this breakage happened and file a report. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Can't make writable USB thumbdrive installer anymore
On Wed, 1 Feb 2017, Brian wrote: On Wed 01 Feb 2017 at 16:06:59 +, David Griffith wrote: On Wed, 1 Feb 2017, solitone wrote: [snip] As specified, this should work fine for most users. The other options are more complex, mainly for people with specialised needs. Please notice that the image must be written to the whole-disk device and not a partition, e.g. /dev/sdb and not /dev/sdb1. This is also pointed out in the liked web page. I followed those instruction and got the same results. I installed Wheezy on a spare machine. There I was able to create a writable flash drive installer that installs Jessie. You used 'cp debian.iso /dev/sdX' and it didn't work? Is that what you mean by "same results"? This is the exact procedure I used to create a one-partition thumb drive, which is writable, to install an arbitrary release of Debian as determined by which ISO was copied to the partition (sudo as necessary). When followed on a Wheezy machine, the result is a thumb drive that works as I previously described. When performed on a Jessie machine, the result is a thumb drive that fails to boot. 1) Ensure these packages are installed: syslinux dosfstools mbr 2) fdisk /dev/sdb (delete all partitons) (create one primary partition) (change partition type to 0x0b (W95 FAT32) (set bootable flag) (write changes and quit) 3) install-mbr /dev/sdb 4) mkdosfs /dev/sdb1 5) mount /dev/sdb1 /mnt 6) cd /mnt 7) wget http://http.us.debian.org/debian/dists/jessie/main/installer-amd64/current/images/hd-media/initrd.gz 8) wget http://http.us.debian.org/debian/dists/jessie/main/installer-amd64/current/images/hd-media/vmlinuz 9) cd 10) echo "default vmlinuz" > /mnt/syslinux.cfg 11) echo "append initrd=initrd.gz" >> /mnt/syslinux.cfg 12) cp ~/iso-images/debian/debian-8.7.1-amd64-CD-1.iso /mnt 13) umount /mnt 14) syslinux /dev/sdb1 15) mount /dev/sdb1 /mnt 16) ls debian-8.7.1-amd64-CD-1.iso initrd.gz ldlinux.c32 ldlinux.sys syslinux.cfg vmlinuz 17) umount /mnt At this point, I can remove the thumb drive and boot it on another machine. I can also test it on QEMU. For instance: sudo qemu-system-x86_64 -hdb /dev/sdb -display curses If the procedure was done on a Wheezy machine, the result is a bunch of text flying by and a normal install process beginning. If done on a Jessie machine, the result is one of these two kernel panic dumps: Panic 1: [0.801766] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS1.7.5-20140531_083030-gandalf 04/01/2014 [0.801930] 81514c11 817054c8 8800070b7ea0 [0.802072] 8151195e 8810 8800070b7eb0 8800070b7e50 [0.802166] 8800070b7ea0 8800070b7eb8 0012 0001 [0.802282] Call Trace: [0.802572] [] ? dump_stack+0x5d/0x78 [0.802654] [] ? panic+0xc8/0x206 [0.802734] [] ? mount_block_root+0x2a9/0x2b8 [0.802788] [] ? SyS_mknod+0x185/0x210 [0.802841] [] ? prepare_namespace+0x133/0x169 [0.802893] [] ? kernel_init_freeable+0x1d7/0x1e1 [0.802945] [] ? initcall_blacklist+0xb2/0xb2 [0.802996] [] ? rest_init+0x80/0x80 [0.803046] [] ? kernel_init+0xa/0xf0 [0.803096] [] ? ret_from_fork+0x58/0x90 [0.803146] [] ? rest_init+0x80/0x80 [0.803506] Kernel Offset: 0x0 from 0x8100 (relocation range:0x8000-0x9fff) [0.803738] ---[ end Kernel panic - not syncing: VFS: Unable to mountroot fs Panic 2: [0.836087] DR3: DR6: DR7: [0.836087] Stack: [0.836087] 8810 8800070b7eb0 8800070b7e50 8800070b7ea0 [0.836087] 8800070b7eb8 0012 0001 000a [0.836087] fffe 88088000 8001 81704fb5 [0.836087] Call Trace: [0.836087] [] ? mount_block_root+0x2a9/0x2b8 [0.836087] [] ? SyS_mknod+0x185/0x210 [0.836087] [] ? prepare_namespace+0x133/0x169 [0.836087] [] ? kernel_init_freeable+0x1d7/0x1e1 [0.836087] [] ? initcall_blacklist+0xb2/0xb2 [0.836087] [] ? rest_init+0x80/0x80 [0.836087] [] ? kernel_init+0xa/0xf0 [0.836087] [] ? ret_from_fork+0x58/0x90 [0.836087] [] ? rest_init+0x80/0x80 [0.836087] Code: c3 64 eb b1 83 3d 48 4d 55 00 00 74 05 e8 81 d0 b7 ff 48 c7 c6 c0 67 a6 81 48 c7 c7 f8 68 71 81 31 c0 e8 66 06 00 00 fb 66 66 90 <66> 66 90 45 31 e4 e8 9d ce be ff 4d 39 ec 7c 18 41 83 f6 01 44 [0.836087] RIP [] panic+0x1c2/0x206 [0.836087] RSP [0.836087] ---[ end trace b6399ee6bd96477c ]--- So, in conclusion, the procedure works when done on a Wheezy machine, but not on a Jessie machine. Why? How can the problem be fixed? -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q
Re: Can't make writable USB thumbdrive installer anymore
On Wed, 1 Feb 2017, David Griffith wrote: I followed those instruction and got the same results. I installed Wheezy on a spare machine. There I was able to create a writable flash drive installer that installs Jessie. Following up... The effect is exactly like what would happen if you delete initrd.gz from the thumb drive. [0.801766] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.7.5-20140531_083030-gandalf 04/01/2014 [0.801930] 81514c11 817054c8 8800070b7ea0 [0.802072] 8151195e 8810 8800070b7eb0 8800070b7e50 [0.802166] 8800070b7ea0 8800070b7eb8 0012 0001 [0.802282] Call Trace: [0.802572] [] ? dump_stack+0x5d/0x78 [0.802654] [] ? panic+0xc8/0x206 [0.802734] [] ? mount_block_root+0x2a9/0x2b8 [0.802788] [] ? SyS_mknod+0x185/0x210 [0.802841] [] ? prepare_namespace+0x133/0x169 [0.802893] [] ? kernel_init_freeable+0x1d7/0x1e1 [0.802945] [] ? initcall_blacklist+0xb2/0xb2 [0.802996] [] ? rest_init+0x80/0x80 [0.803046] [] ? kernel_init+0xa/0xf0 [0.803096] [] ? ret_from_fork+0x58/0x90 [0.803146] [] ? rest_init+0x80/0x80 [0.803506] Kernel Offset: 0x0 from 0x8100 (relocation range: 0x8000-0x9fff) [0.803738] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Can't make writable USB thumbdrive installer anymore
On Wed, 1 Feb 2017, solitone wrote: Why don't you follow what explained here: https://www.debian.org/releases/stable/amd64/ch04s03.html.en It's a simple two command procedure: # cp debian.iso /dev/sdX # sync I don't follow it because I want to be able to include a preseed file and assorted non-free firmware packages. I also want to include assorted other things that I like to put on a fresh machine. As specified, this should work fine for most users. The other options are more complex, mainly for people with specialised needs. Please notice that the image must be written to the whole-disk device and not a partition, e.g. /dev/sdb and not /dev/sdb1. This is also pointed out in the liked web page. I followed those instruction and got the same results. I installed Wheezy on a spare machine. There I was able to create a writable flash drive installer that installs Jessie. -- David Griffith d...@661.org A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Can't make writable USB thumbdrive installer anymore
I used to be able to make a writable USB thumbdrive installer by following the directions found at https://hyper.to/blog/link/debian-installer-on-a-usb-key/, altering the name of the release and device. Now I can't get it to work. When I boot the resulting thumb drive, I get this: List of all partitions: No filesystem could mount root, tried: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown - block (0,0) Pid: 1, comm: swapper/0 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.78-1 The system I'm using to create the thumb drive is Debian 8. I've tried to make installers for 7 and 8 without success. I used to be able to make viable writable install thumbdrives for Debian 7 and 8. What happened? -- David Griffith d...@661.org
