Re: Installing/updating packages are very slow
On 23/10/2014, Bob Proulx wrote: > Igor Sverkos wrote: >> As you can see, it is always the "Unpacking" step which is taking all the >> time. > > dpkg has added fsync() calls after all file actions. This > significantly slows down file operations. Basically it disables the > file system buffer cache causing it to operate at disk drive speeds. > This is why unpacking files is quite a bit slow. > Is this why the Update Manager (on Debian 6 LTS) has stopped working? When I try to run Update Manager, I end up having to kill it. " Update Manager (as superuser) is not responding. You may choose to wait a short while for it to continue or force the application to quit entirely. " It displays "Downloading list of changes", or something like that, and then freezes, and, after five minutes or so, with no change, I have to kill it. Doing a mouseover, on the Update Manager icon in the panel, shows that "There are 32 updates are available", but, it seems unable to either find them, or do anything about it. This has only happened today, after implementing a list of updates yesterday, I think it was, that included apt stuff. Now, I can not update the system (Debian 6 LTS) -- Bret Busby Armadale West Australia .. "So once you do know what the question actually is, you'll know what the answer means." - Deep Thought, Chapter 28 of Book 1 of "The Hitchhiker's Guide to the Galaxy: A Trilogy In Four Parts", written by Douglas Adams, published by Pan Books, 1992 -- 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/CACX6j8N5jubeuRbAQMqBhTQCg9SxSRVSotriPShLPcK=jp4...@mail.gmail.com
Re: Problem with systemd-sleep in Jessie
Am 24.10.2014 um 17:23 schrieb Michael Biebl: > What do you get if your that program when your lid is closed/opened? The output of $ cat /proc/acpi/button/lid/LID/state when lid is closed / open would be helpful as well. If you don't have an external monitor, you can run sleep 30 && cat /proc/acpi/button/lid/LID/state and then quickly close your lid. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Problem with systemd-sleep in Jessie
Am 24.10.2014 um 14:46 schrieb ~Stack~:
> On 10/23/2014 11:06 PM, Michael Biebl wrote:
>> That looks all fine.
>> Can you remove the settings again from logind.conf and restart
>> systemd-logind while monitoring what evtest logs and and also what
>> systemd-logind logs.
>> For the latter, you can either run systemd-logind in the foreground (as
>> I described) or use Joey's method to filter journal entries via
>> "journalctl -u systemd-logind -f"
>
> I did as you asked. I had the F1 terminal set to start systemd-login, F2
> terminal was watching journalctl, F3 was watching evtest for input 4 (I
> also retested with the others, but similar results).
>
> The /only/ thing that journalctl prints out is "Suspending...".
> Everything else is related to when I press the button to wake it back up.
>
> As for the evtest, I get this message over and over again:
> Event: time , type 1 (EV_KEY), code 116 (KEY_POWER), value 1
So, it doesn't look like you get spurious SW_LID events.
We discussed that on #debian-systemd, and it's likely that this is
because of the change that was committed in [1]:
"logind is now a lot more aggressive when suspending the machine due to
a closed laptop lid. Instead of acting only on the lid close action, it
will continuously watch the lid status and act on it."
We suspect, that either your laptop reports an incorrect lid state or
the heuristic to determine the lid state is not correct.
I extracted the lid state switch into a small test program.
Can you compile the attach test program (make switch). I hard-coded the
lid switch button to /dev/input/input1. You'll need to change that if
that's different on your system (check with evtest). You need to run
that binary as root.
What do you get if your that program when your lid is closed/opened?
It should return 0 if the lid is open and 1 if closed.
[1]
http://cgit.freedesktop.org/systemd/systemd/commit/?id=ed4ba7e4f652150310d062ffbdfefb4521ce1054
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
#include
#include
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char **argv) {
int fd;
int lid_closed;
uint8_t switches[SW_MAX/8+1] = {};
fd = open("/dev/input/event1", O_RDONLY);
if (fd < 0)
return -EINVAL;
if (ioctl(fd, EVIOCGSW(sizeof(switches)), switches) < 0)
return -errno;
lid_closed = (switches[SW_LID/8] >> (SW_LID % 8)) & 1;
printf("State: %i\n", lid_closed);
return(0);
}
signature.asc
Description: OpenPGP digital signature
Re: installing systemd on Debian 7
Ric Moore: You have to make a concerted effort to enable systemd to Wheezy. I > mean, you really have to try hard. :) It isn't that hard. But one does have to regularly type in a barefaced lie. -- 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/544a5c20.7020...@ntlworld.com
Re: containers/chroot to allow ABI breakage is the wrong approach
On Fri, 24 Oct 2014, Thomas Goirand wrote: > > OpenBSD’s libc.so major number is 50 or something like that right now, > > because they – correctly – increment it on every incompatible change. > > The correct thing to do is to not do incompatible change. No, in the interest of software hygiene it is often useful and sometimes even required. I can think of cases where glibc’s binary compatibility is *still* biting users’ arses. lewellyn and I had an enlightening discussion on IRC yesterday, which touches this issue. I won’t bore you with the why and the details, but imagine a musl/Linux distribution with the Unix concept of “universes”, which offers a GNU/glibc universe, specifically for running proprietary/binary-only GNU/Linux binaries. The irony! > > This is not a problem because, you know, we have Open Source, so we > > can always just recompile everything against the new libraries. > > Wouldn't it be better to "just" upgrade to the new lib? Recompiling is a > major pain and a loss of time/resources which could be avoided. Sometimes, yes. Often, though, the pain is manageable, and if you do it often enough you have incentive to keep the resources and especially manual work required small. > I explained extensively why in my post. Re-read it, and let me know > which part you didn't understand... :) You wrote a whole lot of things I fully agree with, but you postulate that library major bumps must not happen, without explanation or reasoning, which I disagree with based on my current understanding of things. bye, //mirabilos -- Sometimes they [people] care too much: pretty printers [and syntax highligh- ting, d.A.] mechanically produce pretty output that accentuates irrelevant detail in the program, which is as sensible as putting all the prepositions in English text in bold font. -- Rob Pike in "Notes on Programming in C" -- 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/alpine.deb.2.11.1410241510100.25...@tglase.lan.tarent.de
Re: Problem with systemd-sleep in Jessie
On 10/23/2014 09:36 PM, ~Stack~ wrote: > On 10/23/2014 08:29 PM, Don Armstrong wrote: >> You can also change /etc/systemd/logind.conf, and change the >> HandlePowerKey=, HandleSuspendKey=, HandleHibernateKey=, >> HandleLidSwitch= all to ignore temporarily. > > Done. That seems to work! The laptop isn't sleeping incessantly. :-) Just because I was curious, I decided to test out which one of these is actually the culprit. Thus, I edited logind.conf and commented out the ignore line on all but one at a time. Then 'systemctl stop systemd-logind.service' and then 'systemctl start systemd-logind.service' (yeah, I could have probably done a restart, but I wanted to ensure a full stop). Every time the laptop would instantly go to sleep on start. Except for HandleLidSwitch. That is the one causing problems. Leaving that one set to ignore stops the constant sleep cycle. Maybe the smarter people have already figured that out, but for me it was nice to know the exact one being a pain. :-) Thanks! signature.asc Description: OpenPGP digital signature
Re: Problem with systemd-sleep in Jessie
On 10/23/2014 11:06 PM, Michael Biebl wrote: > That looks all fine. > Can you remove the settings again from logind.conf and restart > systemd-logind while monitoring what evtest logs and and also what > systemd-logind logs. > For the latter, you can either run systemd-logind in the foreground (as > I described) or use Joey's method to filter journal entries via > "journalctl -u systemd-logind -f" I did as you asked. I had the F1 terminal set to start systemd-login, F2 terminal was watching journalctl, F3 was watching evtest for input 4 (I also retested with the others, but similar results). The /only/ thing that journalctl prints out is "Suspending...". Everything else is related to when I press the button to wake it back up. As for the evtest, I get this message over and over again: Event: time , type 1 (EV_KEY), code 116 (KEY_POWER), value 1 Thanks for helping me on this! signature.asc Description: OpenPGP digital signature
Re: Problem with systemd-sleep in Jessie
On 10/23/2014 11:19 PM, Ric Moore wrote: > > To the OP: Stack. THANK YOU for starting an intelligent systemd Q&A. I have voiced my systemd concerns before. At this time, I am simply tying to figure out what is wrong with my laptop. Should systemd be the default/only init system when Jessie releases, I would rather have all these weird quirks fixed /before/ the release. Thus, I am trying to learn about systemd and understand what is going on vs starting yet another flamewar (there is enough of those at the moment...I really don't want to add another). > One feature I read about is that systemd will shut down under various > conditions that would also prevent exhausting the battery on a > laptop. A good thought. The battery on this 8yr old laptop is long dead. I only keep it in the laptop because it balances the weight (and there is an awkward gap in the back without it). A new battery for this laptop is 90$. Not worth it for this laptop. In any case, I removed the battery and I still have the issue. > I don't suppose there is anyway to install fresh to get rid of old > cruft?? I am sure I could, but it isn't easy as this laptop doesn't support USB boot and the CD-ROM is long dead too. I have to PXE boot the network image for the Debian install... Besides, I would rather see if I can find what is wrong vs just blowing it away and potentially losing whatever caused the problem. If I lose that, then we can't file a bug report to have it fixed which in turn means others might have this same issue in the future. If at all possible, I would like to find a proper fix. > I'm of no help as I am just starting to learn it, but I am learning > from your experience, so that you again. Ric I'm learning too. :-) Thanks for the input. signature.asc Description: OpenPGP digital signature
Re: Problem with systemd-sleep in Jessie
On 10/23/2014 10:25 PM, Michael Biebl wrote: > Am 24.10.2014 um 04:58 schrieb Michael Biebl: >> Am 24.10.2014 um 04:19 schrieb Michael Biebl: >> >>> For some reason, you seem to be getting acpi events which trigger the >>> suspend request in logind. This might be a buggy ACPI implementation >>> like in [1]. >> >> To further debug this, you might install the "evtest" package and run >> the evtest binary as root. > > Another thing you can try is the following (run as root): > $ systemctl stop systemd-logind.service > $ /lib/systemd/systemd-logind > > This will show you, which input devices logind will monitor and which > events it receives. # /lib/systemd/systemd-logind New seat seat0 Watching system buttons on /dev/input/event5 (Power Button) Watching system buttons on /dev/input/event1 (Video Bus) Watching system buttons on /dev/input/event4 (Power Button) Watching system buttons on /dev/input/event2 (Lid Switch) Watching system buttons on /dev/input/event3 (Sleep Button) New session c1 of user lightdm New session 1 of user root. Suspending... Power key pressed. Operation finished. As soon as I ran the command, that is what happened. The Power key pressing was me waking it back up. Thanks! signature.asc Description: OpenPGP digital signature
Re: How To Prove Systemd Can|Cannot Be Jessie Default
On 23/10/14 22:10, David L. Craig wrote: On 14Oct23:2035+0300, Dimitrios Chr. Ioannidis wrote: That's not the point. From the technical point of view, IMO, you are correct but that's not the only view that exists in Debian Project, me thinks. [snip] My choices reg. my use of technology isn't based only on technical grounds, you know. There are legal considerations pertaining to global software redistribution, of course. There are financial considerations beyond Debian's licensing and support fees, to be sure, but those and other categories of non-technical considerations are entirely outside of the Debian organization as I see it--they are user considerations. And there should be ethical considerations, e. g. to not expose the users by default to software that due to its complexity and technical characteristics might facilitate intrusion and spying. -- 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/m2dgie$sib$1...@ger.gmane.org
Re: Good news on claws-mail
Le 23.10.2014 20:40, lee a écrit : berenger.mo...@neutralite.org writes: The only problem is bash, here: it is unable to handle multi-instances, so the histories are lost more or less randomly when I close/spawn terminals and sessions. # append history rather than overwriting it shopt -s histappend Interesting. I'll try this ASAP. Do you use tmux? No, I do not really see the interest of using it, I must admit it. -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable. -- 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/3682d558c5ae72aa35d1b8e85f018...@neutralite.org
Re: Have never seen this previously...........
On Fri, 24 Oct 2014 10:44:25 +0100 Darac Marjal sent: > I'm not quite sure what your setup here is so: > * If you're booting in BIOS mode with an MBR disk, then raise a bug > against grub > * If you're booting in BIOS mode with a GPT disk, then create the BIOS > Boot Partition that grub is asking for. > * If you're booting in UEFI mode with a GPT disk, then you're using > the wrong version of grub; i386-pc is for BIOS booting and you should > install grub-efi instead > * If you're booting in UEFI mode with an MBR disk, then switch to > grub-efi, and see if the same error is raised. If so, raise a bug > against grub. I did nothing special, just what I do normally when I get a computer or hard disk. Wipe it with gparted and set up my partitions: /root, /home, /usr, /var etc., etc.. Allow grub to install. Then put in the netinstall disk, install a basic system with that. Reboot and start using it adding whatever packages I need as I require them. That's it. Not difficult I don't think, and I update and upgrade about once a week, and have never had that error message previously. No worries. Obviously something changed in the last upgrade. Not something that I did, because I didn't do anything. [laughing] Anyway, it was just a curiosity, not a bug as far as I can see because it boots and everything works. Be well, Charlie -- Registered Linux User:- 329524 *** 'Come to the edge', he said. They said..'We are afraid'. 'Come to the edge', he said. They came, he pushed them And they flew. ___Guillaume Apollinaire *** Debian GNU/Linux - just the best way to create magic - -- 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/20141024230714.4b1bedc4@taogypsy
Re: containers/chroot to allow ABI breakage is the wrong approach
On 24/10/14 10:12, Thomas Goirand wrote: On 10/21/2014 05:12 PM, Thorsten Glaser wrote: OpenBSD’s libc.so major number is 50 or something like that right now, because they – correctly – increment it on every incompatible change. The correct thing to do is to not do incompatible change. A wonderful aphorism. Now, what do you do when the only sane way to resolve a critical security vulnerability, or implement a feature demanded-with-good-reason by 95% of your users, is to make an incompatible change? -- 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/544a3dc8.5080...@zen.co.uk
Re: Searching uninstalled packages by directory name
Am 24.10.2014 um 13:08 schrieb Darac Marjal: > Actually, apt-file will search the whole path (try 'apt-file search > bin'). If you like, try the -x option to apt-file to specify a > perl-compatible regex. You're right! Thanks for pointing that out. I was mislead by the man page auf apt-file 2.5.1 (in wheezy) which says search Search in which package a file is included. A list of all pack‐ ages containing the pattern pattern is returned. apt-file will only search for filenames, not directory names. This is due to the format of the Contents files it searches. A misinterpretation on my behalf or a bug in the documentation? -- 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/m2de24$hri$1...@ger.gmane.org
Dutch myspell/hunspell .aff file giving errors when loaded in PostgreSQL
On the Debian bug reporting page it said that I should ask here if I wasn't sure where to report a bug. The problem is that the file /usr/share/hunspell/nl.aff (part of the myspell-nl package) gives errors if you construct a ispell Dictionary with it in PostgreSQL as follow: CREATE TEXT SEARCH DICTIONARY dutch_ispell ( template = ispell, DictFile = nl, AffFile = nl, StopWords = dutch ); The error reads: ERROR: wrong affix file format for flag CONTEXT: line 827 of configuration file "/usr/share/postgresql/9.3/tsearch_data/nl.affix": "SFX CA Y 2" In the nl.affix file it says: # accept an optional - when compounding, first part # the second line allows for the optional hyphen SFX CA Y 2 SFX CA 0 /CaCp SFX CA 0 -/CaCp In the PostgreSQL documentation it reads (http://www.postgresql.org/docs/8.3/static/textsearch-dictionaries.html#TEXT SEARCH-ISPELL-DICTIONARY): Note: MySpell does not support compound words. Hunspell has sophisticated support for compound words. At present, PostgreSQL implements only the basic compound word operations of Hunspell. So the problems are: - The package Myspell-nl appears to deliver a Hunspell dictionary (there is not even a simlink in the /usr/share/myspell/dits/ directory, there are simlinks there for the Hunspell files installed through the Hunspell-en and Hunspell-de packages) - PostgreSQL does not support COMPOUND words in Hunspell files (or atleast not the way it is done in the Dutch affix file) - Since I only know this error to appear in PostgreSQL when using the Dutch myspell files I don't know where to report this, the myspell-nl package or the PostgreSQL-common package (the PostgreSQL-common package comes with the "pg_updatedicts" this copies supported installed files to /var/cache/postgresql/dicts/ and creates links to them in /usr/share/postgresql/9.3/tsearch_data Hope someone can point me in the right direction, Greetings W -- 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/006901cfef7a$da0fa260$8e2ee720$@nodiscipline.net
Re: If Not Systemd, then What?
On 10/24/2014 4:49 AM, Jonathan de Boyne Pollard wrote: > Tanstaafl: >> And why was OPenRC not a contender? > Your question takes a falsehood as its premise. It actually was, > contrary to what M. Popescu dismissively stated. Several members of the > technical committee took it and tried to use it themselves, just as they > did the other systems; and it was included on the formal ballots and in > the votes. I actually do remember reading a fleeting mention of it somewhere in the vast sea of stuff I read when trying to catch up on this issue... > Contrastingly, the people who were propounding OpenRC at the > time provided a good example of how NOT to go about doing so. Their > several mistakes are worth learning from. Not sure I understand what you are saying here... Are you saying that some of the people who suggested OpenRC actually provided BAD examples - meaning, examples that were destined to result in problems - of how to use it in Debian? If so, maybe that was on purpose, to decrease the chances of OpenRC being a real contender? The fact is, OpenRC has been the default init system on gentoo since I don't know when, and I have *never* had an init problem on any of my gentoo systems - although I admittedly never use unstable/testing for system-critical packages either... -- 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/544a32ef.3090...@libertytrek.org
Re: If Not Systemd, then What?
On 10/23/2014 4:10 PM, koanhead wrote: > I propose OpenRC, having recently tried it. So far I'm liking how it > works, and it solves most of the problems I had with sysvinit. It's not > a replacement for PID1, and is supposed to be compatible with arbitrary > PID1 programs (sysvinit, sytemd, runit, etc.) I expect to test it with > other PID1 programs at some point, but for now I'm still learning it. > There's also runit, which I haven't tried yet but about which I've heard > good things; and daemontools, which has already been talked up on this > list. All these are already in Debian's repositories. Seconded... OpenRC has also been the default init system for gentoo for as long as I can remember knowing what init system I was running on my gentoo server (I had help setting up the first one ten years ago, so I don't know if it was the default then)... -- 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/544a2f86.2070...@libertytrek.org
Re: Searching uninstalled packages by directory name
On Fri, Oct 24, 2014 at 12:36:01PM +0200, Malte Forkel wrote: > Hi, > > how can I find all packages that will install files in a specific directory? > > dpkg-query (dpkg -S) only searches installed packages. apt-file will > only search filenames, not directory names. Actually, apt-file will search the whole path (try 'apt-file search bin'). If you like, try the -x option to apt-file to specify a perl-compatible regex. > > Thanks > Malte > > > -- > 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/m2da2e$fsb$1...@ger.gmane.org > signature.asc Description: Digital signature
Searching uninstalled packages by directory name
Hi, how can I find all packages that will install files in a specific directory? dpkg-query (dpkg -S) only searches installed packages. apt-file will only search filenames, not directory names. Thanks Malte -- 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/m2da2e$fsb$1...@ger.gmane.org
Re: Legacy PTY`s in Debian 7.7
Hi, the default Debian 7.7 kernel seems to lack LEGACY_PTY support: > grep LEGACY_PTY /boot/config-$(uname -r) > # CONFIG_LEGACY_PTYS is not set -- Regards, Igor -- 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/caayqc41ewr0wpdufssscobtpes40fjxbh-caccpoju0ceof...@mail.gmail.com
Re: Have never seen this previously...........
On Fri, Oct 24, 2014 at 08:15:03PM +1100, Charlie wrote: > On Thu, 23 Oct 2014 14:20:33 +0100 Darac Marjal sent: > > > > On a GPT disk using BIOS, though, GRUB will still install Stage 1 into > > the first sector, but then there's no suitable place for it to put > > Stage 1.5. So you're expected to create the Bios Boot Partition, into > > which Grub will install Stage 1.5. No file system should be created > > on this partition. > > > > I googled GPT disk and this was certainly a UEFI disk or partition or > whatever. But formatted the whole disk and then created the > partitions I wanted with GParted and then installed Jessie. Are you trying to boot in BIOS or UEFI mode? BIOS/MBR and UEFI/GPT are the most common supported modes. BIOS/GPT is unusual, but appears to be what you're attempting. I'm not quite sure what your setup here is so: * If you're booting in BIOS mode with an MBR disk, then raise a bug against grub * If you're booting in BIOS mode with a GPT disk, then create the BIOS Boot Partition that grub is asking for. * If you're booting in UEFI mode with a GPT disk, then you're using the wrong version of grub; i386-pc is for BIOS booting and you should install grub-efi instead * If you're booting in UEFI mode with an MBR disk, then switch to grub-efi, and see if the same error is raised. If so, raise a bug against grub. > > So maybe the disk has reverted or something? But it has only done this > in the last update. prior to that there was no problem. > > The system boots all right anyway, so I'll see what happens in the > future. I might have to reformat the whole disk again and reinstall > Jessie. > > I'll see what happens. > > Thanks for the explanation which I didn't really understand. > > Charlie > -- > Registered Linux User:- 329524 > *** > > Zen practise is thus not a set of operations designed to > achieve an external goal. In Zen, the effort and the result are > not two different things, the means and the goal are not to be > separated, the finding occurs in the very seeking itself. > _Bernard Phillips > > *** > > Debian GNU/Linux - just the best way to create magic > > - > > > -- > 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/20141024201503.04dbf681@taogypsy > signature.asc Description: Digital signature
Re: Have never seen this previously...........
On Thu, 23 Oct 2014 14:20:33 +0100 Darac Marjal sent: > On a GPT disk using BIOS, though, GRUB will still install Stage 1 into > the first sector, but then there's no suitable place for it to put > Stage 1.5. So you're expected to create the Bios Boot Partition, into > which Grub will install Stage 1.5. No file system should be created > on this partition. I googled GPT disk and this was certainly a UEFI disk or partition or whatever. But formatted the whole disk and then created the partitions I wanted with GParted and then installed Jessie. So maybe the disk has reverted or something? But it has only done this in the last update. prior to that there was no problem. The system boots all right anyway, so I'll see what happens in the future. I might have to reformat the whole disk again and reinstall Jessie. I'll see what happens. Thanks for the explanation which I didn't really understand. Charlie -- Registered Linux User:- 329524 *** Zen practise is thus not a set of operations designed to achieve an external goal. In Zen, the effort and the result are not two different things, the means and the goal are not to be separated, the finding occurs in the very seeking itself. _Bernard Phillips *** Debian GNU/Linux - just the best way to create magic - -- 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/20141024201503.04dbf681@taogypsy
Re: containers/chroot to allow ABI breakage is the wrong approach
On 10/21/2014 05:12 PM, Thorsten Glaser wrote: > On Tue, 21 Oct 2014, Thomas Goirand wrote: > >> So, dear fellow DDs, I'm asking you: each time you see that an upstream >> author is breaking an ABI on a package you maintain, write an email to >> him/her, and explain how much this is bad and shouldn't happen. If the >> Unix community starts to realize how much we're loosing by breaking >> ABIs, I'm sure the situation will improve. > > Why? I explained extensively why in my post. Re-read it, and let me know which part you didn't understand... :) > OpenBSD’s libc.so major number is 50 or something like that right now, > because they – correctly – increment it on every incompatible change. The correct thing to do is to not do incompatible change. > This is not a problem because, you know, we have Open Source, so we > can always just recompile everything against the new libraries. Wouldn't it be better to "just" upgrade to the new lib? Recompiling is a major pain and a loss of time/resources which could be avoided. Thomas -- 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/544a17ee.5040...@debian.org
Re: Re: If Not Systemd, then What?
Andrei Popescu: Upstart was the only real contender to systemd at the time of the > evaluation by the Technical Committee, but it has or is being > replaced by systemd everywhere. Tanstaafl: And why was OPenRC not a contender? Your question takes a falsehood as its premise. It actually was, contrary to what M. Popescu dismissively stated. Several members of the technical committee took it and tried to use it themselves, just as they did the other systems; and it was included on the formal ballots and in the votes. Contrastingly, the people who were propounding OpenRC at the time provided a good example of how NOT to go about doing so. Their several mistakes are worth learning from. -- 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/544a12aa.10...@ntlworld.com
Legacy PTY`s in Debian 7.7
Hello, I am new to this list and I am looking for help with Debian 7.7, I have this test setup on my laptop using the xfce desktop. With my applications I run on Ubuntu 10.04.4, I create some pty links for running software on the same linux box. Usually I just need to add the statement pty.legacy_count=32 to the grub.cfg file but this no longer appears to work in Debian ? cat /proc/cmdline shows it is present but Debian ignores it and does not create the pty devices in /dev BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae root=UUID=9a27be8f-4417-4ee4-9348-6d108623a9b5 ro pty.legacy_count=32 quiet Any suggestions ? Thank you. Regards . Peter ZL2BAU -- 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/544a078f.9060...@gmail.com
Re: X Server not available after Sid update on 21 Oct.
Am Donnerstag, den 23.10.2014, 14:06 -0700 schrieb Don Armstrong: > On Thu, 23 Oct 2014, Jürgen Kleber wrote: > > I did not mention yet that I tried lightdm/xfce4 - and it failed, too. > > You should assign the bug additionally to lightdm. > > What was output to syslog when you did this? > > What versions of these packages did you have installed? > > What is output to ~/.xsession-errors for your user? > > Do you have anything in ~/.config/autostart/? If so, try deleting it > first. > > -- > Don Armstrong http://www.donarmstrong.com > > Maybe I did steal your heart > and I am such a perfect criminal > that you never noticed > -- a softer world #481 > http://www.asofterworld.com/index.php?id=481 > > Yesterday I updated a third Sid system and everything is ok. I'll check out what might have gone wrong on 21th. Thank you for your assistance. Jürgen signature.asc Description: This is a digitally signed message part
Re: lightdm's "Default Xsession"?
On 24/10/14 at 10:17am, Andrei POPESCU wrote: > On Jo, 23 oct 14, 19:38:15, John Conover wrote: > > > > I use two WM, (xfce and fvwm.) Lightdm's "Default Xsession" is fvwm2. > > > > How do I change lightdm's "Default Xsession" to xfce? > > I prefer to do this at system level (i.e. will work for any DM): > > update-alternatives --config x-session-manager That's smarter but doesn't always work. As an example I always use awesome and sometimes i3 but the command above returns only xfce4-session ie no alternatives. /r -- « Nunc est bibendum, nunc pede libero pulsanda tellus » -- 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/20141024073358.gb1...@gmail.com
Re: lightdm's "Default Xsession"?
On Jo, 23 oct 14, 19:38:15, John Conover wrote: > > I use two WM, (xfce and fvwm.) Lightdm's "Default Xsession" is fvwm2. > > How do I change lightdm's "Default Xsession" to xfce? I prefer to do this at system level (i.e. will work for any DM): update-alternatives --config x-session-manager Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: quilt & debian-jenkis-glue
On Jo, 23 oct 14, 15:37:04, George Shuklin wrote: > Hello. > > I can't get normal workflow with quilt & debian-jenkins-glue. You might have more success on -mentors. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
