Re: Debian 5 -- data is plural.
Ken Heard wrote: ... Some people however do use the word medias. On the other hand does anyone use the word datas? If not, it is logical to conclude that they give word data a plural meaning. Wrong--what is logical to conclude is that they consider data what another poster called a mass noun--like the word information in English. If you say a piece for data for one piece of information, then data is a mass noun, and therefore grammatically singular. If you actually say datum for one piece of information, only then can you argue that data is plural. Daniel -- 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/5383ab84.3000...@kempt.net
installed cups-pdf package; now what?
Where are the instructions for what to do after installing the cups-pdf package, to have the virtual to-PDF printer appear (e.g. in lpstat -a output) and be able to print to PDF? The files /usr/share/doc/cups-pdf/... don't seem to have any such instructions. (I tried using the CUPS administration tool at http://localhost:631/admin, but it's unclear how to proceed (e.g., what Make and Model would I use).) Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51c7e9a2.9060...@kempt.net
Re: pcspkr
lee wrote: Dan B. d...@kempt.net writes: lee wrote: Hi, with the pcspkr module installed, shouldn't I hear the beep through the sound card that otherwise would be played by a little loudspeaker connected to the mainboard? pcspkr might be the wrong module. You might want snd-pcsp instead. With a little speaker plugged into the mainboard, I can install either pcspkr or snd-pcsp and in both cases, the beep comes from the little speaker and never from the sound card. I cannot install both modules at once, and without any of them, the speaker doesn't beep. What's the difference between these modules? Does snd-pcsp make the little speaker available to alsa like a sound card? There is a slider labled Beep in alsamixer, and it doesn't seem to do anything. I thought I read that snd-pcsp makes the little speaker available to alsa as a (very low-quality) sound card. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51c7c42e.9070...@kempt.net
Re: pcspkr
lee wrote: Hi, with the pcspkr module installed, shouldn't I hear the beep through the sound card that otherwise would be played by a little loudspeaker connected to the mainboard? pcspkr might be the wrong module. You might want snd-pcsp instead. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5085c171.7090...@kempt.net
Re: [Conclusion] Looking for an emacs replacement
lee wrote: ... ... You can still run emacs fine on the console or in a terminal as you could 15--20 years ago, and you can use the GUI frames if you like, even all at the same time --- or compile a version that doesn't have X-support at all. FYI: There's an emacs23-nox (no X11 dependency) package. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/505dd3fb.5060...@kempt.net
Re: What does charset in locale setting affect?
Roger Leigh wrote: On Sat, Sep 01, 2012 at 07:32:48PM -0400, Dan B. wrote: ... Which common programs (e.g., getty, xterm/etc., sed/grep?) do something different based on the charset portion of the local setting? All of them, in short. When you run a terminal emulator such as xterm, it will get the encoding to use inside the emulator using nl_langinfo(3).... What about the virtual consoles? Whether I choose a default system locale of UTF-8 or None (in the dialog for dpkg-reconfigure locales), and log out and log in (to make sure the shell has a chance to get fresh settings), then echo $'\xC2\xA2' displays the same thing (the cent sign). Is the virtual console supposed to follow the locale's character encoding? If so, does something else (e.g., something in /etc/init.d/) need to be run to make a difference? No, I'm not actually trying to turn off using UTF-8. I'm just trying to find out how things work (what actually is affected by the locale settings). Actually, what I really want to know is how to revert the sorting of file names from ls (and Emacs dired listings) from the order caused by having en_US in LANG=en_US.UTF-8 back to the traditional (old) Unix order (e.g., what LANG=C would yield) without messing up all the UTF-8 support that's all over Linux now. First of all, can UTF-8 be combined with the C locale as in LANG=C.UTF-8? Do I probably want something closer to LANG=en_US.UTF-8 LC_COLLATE=C (in order to reduce the amount of locale settings I'm overriding)? When you run sed/grep, the encoding will affect how it processes the text. Are you sure about sed? I tried probing how LANG= vs. LANG=en_US.UTF-8 affected whether the regular expression [a-z] matched X. Grep seems to be affected as expected, but sed never matched. (That's on Squeeze.) Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50441ffc.7040...@kempt.net
What does charset in locale setting affect?
In a locale setting such as en_US.UTF-8 (e.g., LANG=en_US.UTF-8), what exactly does the charset/character encoding part (UTF-8) affect? Which common programs (e.g., getty, xterm/etc., sed/grep?) do something different based on the charset portion of the local setting? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50429b20.7030...@kempt.net
What does stty's iutf8 actually do (effect)?
The manual page for stty says that the input setting iutf8 controls whether to assume [that] input characters are UTF-8 encoded. What does setting actually do? (I understand UTF-8 and its mapping between byte sequences and characters. What I don't know is where character decoding and encoding are done in Linux input and output components (virtual consoles, xterm/etc., tty devices).) What does that iutf8 setting actually affect? Is the terminal (tty?) driver involved in decoding the input byte stream into characters for the process attached to the tty device? Or does the driver decode bytes into characters only for its own checking for special characters (e.g., for stty intf CHAR)? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/502ed815.9000...@kempt.net
which layer to configure so Alt-x does Meta-x in bash?
What's the right layer to reconfigure so that Alt functions as Meta in bash command line editing? Right now, when I try to type Alt-f to execute bash's Meta-f line-editing function (Forward Word), bash instead inserts a non-ASCII character (the a-e ligature). That happens in bash in xterm and in ssh sessions, but not in bash on a virtual console. (What I mean by right layer above is the layer that probably would have the fewest unwanted side effects. For example, on an older system, Alt-f works as Meta-a in bash, but still inserts the a-e character when typed while running a command such as cat (that is, just echoing typed input to output), so I don't think I want a solution that completely disables the non-ASCII character generation.) Do I want to be looking in bash? in inputrc? in xterm? somewhere else? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ff4a482.4000...@kempt.net
Re: grub-install says can't identify filesystem; won't install
Andrei POPESCU wrote: On Jo, 28 iun 12, 21:41:23, Dan B. wrote: When I run grub-install /dev/sdb1, it says: /usr/sbin/grub-setup: error: unable to identify a filesystem in hd1,gpt1; safety check can't be performed. and does not install GRUB2. (It's still the same if I use the syntax (grub-install (hd1,gpt1).) Are you sure you want to install grub to a partition (and not to the MBR)? No. Right, I wanted grub-install /dev/sdb. (Actually, I did want GRUB to install _part_ of itself to that partition (it was a GPT bios_grub paritition), so that's why it seemed normal enough that GRUB referred to hd1,gpt1, but odd that it was looking for a filesystem there. Hmm. I guess an error-message enhancement-suggestion bug report is in order...) Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fef2229.5020...@kempt.net
grub-install says can't identify filesystem; won't install
When I run grub-install /dev/sdb1, it says: /usr/sbin/grub-setup: error: unable to identify a filesystem in hd1,gpt1; safety check can't be performed. and does not install GRUB2. (It's still the same if I use the syntax (grub-install (hd1,gpt1).) This is on a disk tht has a GPT partition table, and whose first partition has the bios_grub flag. Also, this is a new disk--that partition is still full of zeroes. Also, grub-install spits out about 33 instances of this message: error: superfluous RAID member (2 found). Does anybody recognize those symptoms or my error? I wouldn't think GRUB2 would insist on finding a file system on the device on which in installs its low-level boot code. That makes me wonder if I'm not using the right GRUB2 command or not quite catching what the error message is trying to tell me. I already have GRUB2 installed on (hd0,gpt1), but that was accomplished in the Debian installer (Squeeze), not via the command line. However, I tested running grub-install as above on a second disk earlier (before adding a new disk as /dev/sdb), and didn't have this problem. Unfortunately, I can't yet tell what's different now. Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fed07c3.8090...@kempt.net
Re: what did hwinfo do to my machine? - SOLVED
Curt wrote: On 2012-06-05, Dan B. d...@kempt.net wrote: What the heck did hwinfo do to my machine? Thanks to some suggestions that somehow caused me to check basic floppy access, I discovered that the problem was ... (get ready for a big letdown) ... a loose floppy cable. So you're saying when you typed hwinfo into an xterm, it shook the cable loose? No, the cable wasn't quite _that_ loose. It was plugging and unplugging a serial modem cable and an internal adapter cable that shook the floppy's cable loose (and that happened very close in time to when I installed and ran hwinfo). Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fcfb9ce.9020...@kempt.net
Re: what did hwinfo do to my machine?
Stan Hoeppner wrote: On 6/3/2012 11:05 PM, Dan B. wrote: After I ran hwinfo (to detect a modem), my machine runs very slowly at the beginning of booting. You did something else also. The hwinfo manpage says nothing about running at boot, so I assume it has nothing to do with this. Something is running at boot that wasn't before, and is slowing down the boot process. Look at your dmesg output and your grub command line to see what it may be. Did you really read my message? I didn't say that hwinfo was running at boot. I said that I ran hwinfo, and after than, the beginning booting has been slow. Also, I wrote: GRUB takes about 8 seconds between displaying the the Welcome to GRUB! text and the error: fd0 read error. text... That's before the Linux kernel is even involved, so how would dmesg be related? In fact, that's before the contents of a GRUB command line have any effect, so that's not related either. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fccc922.7000...@kempt.net
Re: what did hwinfo do to my machine?
Kent West wrote: On 06/03/2012 11:05 PM, Dan B. wrote: After I ran hwinfo (to detect a modem), my machine runs very slowly at the beginning of booting. (GRUB takes about 8 seconds between displaying the the Welcome to GRUB! text and the error: fd0 read error. text, ...) What the heck did hwinfo do to my machine? I can't speak about hwinfo. But the problem seems to be in your hardware somehow. Well, the _current_ problem is in my hardware. We don't know yet that hwinfo doesn't have a problem too (of changing persistent hardware settings in the process of probing). I know that in the early days of USB support, some computers thought non-booting USB devices (like a printer) was a boot device, and would look for a boot record there and hang for a long time. We got around that by unplugging the printer until after the POST part of booting. I'm also suspecting a floppy drive issue, that the BIOS is set to boot from it and one doesn't exist, or some such. Also, back to the USB printer, perhaps you have a memory card inserted into a memory card slot on the printer (having printed some pictures from it a few days ago, maybe), and the computer is seeing that card via the printer connection and trying to boot from it. I don't see any way that it's something like that. I've been rebooting multiple times per day (configuring a new system and rebooting to check setting), so it's not like I attached or detected some device days ago, forgot about it, and just now rebooted and ran into symptoms caused by an earlier change. I had tried configuring PPP. pppconfig hadn't detected an attached modem. On some subsequent boot, I installed hwinfo, ran it a couple of times, and it detected the modem (after not detecting it earlier, presumably because of an incompletely plugged-in cable). On a boot very soon after that (probably the next boot, but I can't say for sure), GRUB began being very slow. The only changes in device attachments were 1) connecting and disconnecting the modem from the serial port and 2) the KVM switching I've been doing for weeks. There was a USB memory stick that was attached, but that hadn't changed in weeks. Also, after the symptoms started, I removed it, but the problem remains. As I said, I wonder if some persistent setting in my hard disks (SATA disks) got changed. What tools does Linux have for looking at disk settings (Seagate Barracuda disks)? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fccd139.2000...@kempt.net
Re: what did hwinfo do to my machine?
Miles Fidelman wrote: Dan B. wrote: After I ran hwinfo (to detect a modem), my machine runs very slowly at the beginning of booting. (GRUB takes about 8 seconds between displaying the the Welcome to GRUB! text and the error: fd0 read error. text, and another 25 seconds for the screen to go blank on the way to displaying the menu. Kernel booting might be slow for the first dozen or so messages; after that, everything seems to be fine.) What the heck did hwinfo do to my machine? Perhaps a silly thought, but... did you install hwinfo just before running it, and if so, did you install any dependencies in the process? Yes, and one prerequisite that aptitude installed for hwinfo was a hal library. hwinfo requires some libraries that get pretty close to the hardware - perhaps a changed library is causing your problems Except that a changed library is not running, or even loaded, when GRUB is running (let alone when GRUB is just starting up). Just to doubly confirm things, I just purged hwinfo and purged the two prerequisite packages that aptitude installed, and tried rebooting. GRUB is still slow. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fccd6a9.7050...@kempt.net
Re: what did hwinfo do to my machine?
Camaleón wrote: On Mon, 04 Jun 2012 00:05:13 -0400, Dan B. wrote: After I ran hwinfo (to detect a modem), my machine runs very slowly at the beginning of booting. (GRUB takes about 8 seconds between displaying the the Welcome to GRUB! text and the error: fd0 read error. ^ (...) Well, that error can be relevant. How? It's not the *presence* of the message that has changed. It's the *delay* between the Welcome to GRUB! message and that error: fd0 read error. message that has changed (to 8 or 9 seconds, from something close to zero). Besides, that error message (presumably) simply means that GRUB didn't successfully read from the floppy drive, which makes perfect sense since there's no floppy in it. Try to disable the floppy disk controller (or any other FDD related stuff you find) from the BIOS and see what happens. Maybe I'll go ahead and try that out of desperation, but how would that fix the problem? Things were fine (GRUB loaded normally fast) with the FDC enabled before I ran hwinfo. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fccdf05.1050...@kempt.net
Re: what did hwinfo do to my machine?
Camaleón wrote: On Mon, 04 Jun 2012 12:15:01 -0400, Dan B. wrote: Camaleón wrote: On Mon, 04 Jun 2012 00:05:13 -0400, Dan B. wrote: After I ran hwinfo (to detect a modem), my machine runs very slowly at the beginning of booting. (GRUB takes about 8 seconds between displaying the the Welcome to GRUB! text and the error: fd0 read error. ^ (...) Well, that error can be relevant. How? It's not the *presence* of the message that has changed. My crystal ball did not mention that the above error message was present before ;-) Hey, don't blame me for your assuming (or misinterpreting my words to mean) that the error: fd0 read error. message was new. I wrote _the_ ... error text, not something like _an_ error, and, I referred to the welcome text and the error message text with exactly the same structure (the ... text): I wrote: GRUB takes about 8 seconds between displaying the the Welcome to GRUB! text and the error: fd0 read error. text ... It's the *delay* between the Welcome to GRUB! message and that error: fd0 read error. message that has changed (to 8 or 9 seconds, from something close to zero). Yes, I know that behaviour; it's the same long delay I get in one of my testing virtual machines. How long are the delays you usually see (from the welcome message to any fd0 error message, from either the later of those to the screen's blanking, and from then to the GRUB menu)? Besides, that error message (presumably) simply means that GRUB didn't successfully read from the floppy drive, which makes perfect sense since there's no floppy in it. Well, I can't tell what it means but given the nature of the message (error) I would ensure anything is all right. But what is there to check? The message seems perfectly well explained: At the level of reading from the floppy drive, there's read error because there's no floppy in the drive; that floppy read error isn't a problem at the GRUB level, because GRUB has been reporting that floppy-read error and still booting at normal speed ever since I installed, until this hwinfo incident. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fcce9b7.90...@kempt.net
Re: what did hwinfo do to my machine?
Miles Fidelman wrote: Dan B. wrote: Camaleón wrote: On Mon, 04 Jun 2012 00:05:13 -0400, Dan B. wrote: After I ran hwinfo (to detect a modem), my machine runs very slowly at the beginning of booting. (GRUB takes about 8 seconds between displaying the the Welcome to GRUB! text and the error: fd0 read error. ^ (...) Well, that error can be relevant. How? It's not the *presence* of the message that has changed. It's the *delay* between the Welcome to GRUB! message and that error: fd0 read error. message that has changed (to 8 or 9 seconds, from something close to zero). Besides, that error message (presumably) simply means that GRUB didn't successfully read from the floppy drive, which makes perfect sense since there's no floppy in it. ahh... but there may be various timeouts involved that have changed, for example: - is the BIOS set to run POST every time, or just under certain circumstances, if so, what happens if you set the fast boot option No, the fast-boot option is off (and has been off since I installed Squeeze). When I first noticed the slowness, since it was early in the boot process (only GRUB was definitely slow, and the kernel was definitely back to normal, at least after a dozen or so kernel messages at boot), I thought that maybe hwinfo has messed with some CPU-speed option in my BIOS, so re-set the BIOS to what I had set it to before, as I had set it before (loading BIOS defaults and then setting about 8 things (from a written plan (as opposed to just from memory))). - maybe turn on BIOS logging and see if it catches any funniness during the pre-GRUB boot process I haven't seen anything about BIOS logging in my BIOS's menus. Is it common? It is known by any other names? also sounds like your system was having problems finding the network card at one point, and then that changed - maybe your hardware is flakey - run some diagnostics No, it has always found the ethernet interface just fine. I was setting up PPP for a backup connection when I had the modem detection problem and tried hwinfo. re. your question about SATA diagnostics: - smart tools can give you a lot of diagnostic and configuration info about your drives, a flaky boot sector might cause a bunch of re-reads by the drive hardware Okay, thanks. Maybe I'll try that. - you might check your drive maker's web site for hardware-specific diagnostics I do have a diagnostics CD, so I can try that too. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fcced44.5000...@kempt.net
Re: what did hwinfo do to my machine? - SOLVED
I wrote: After I ran hwinfo (to detect a modem), my machine runs very slowly at the beginning of booting. (GRUB takes about 8 seconds between displaying [the] Welcome to GRUB! text and the error: fd0 read error. text, and another 25 seconds for the screen to go blank on the way to displaying the menu. ...) What the heck did hwinfo do to my machine? Thanks to some suggestions that somehow caused me to check basic floppy access, I discovered that the problem was ... (get ready for a big letdown) ... a loose floppy cable. (Apparently plugging in the modem--or, more likely, unplugging and re-plugging the motherboard-to-DB9 adapter cable to check something--jostled a incompletely seated floppy drive cable enough to disconnect some pins. Re-seating the floppy cable has restored the previous behavior--no major delays between the Welcome to GRUB! text and the error: fd0 read error. text, or from there to the GRUB menu.) Thanks for the help. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fcd4f3f.3000...@kempt.net
Re: what did hwinfo do to my machine? - SOLVED
Miles Fidelman wrote: Dan B. wrote: Thanks to some suggestions that somehow caused me to check basic floppy access, I discovered that the problem was ... (get ready for a big letdown) ... a loose floppy cable. It really is amazing how many things end up being hardware problems ;-) And I thought it was in some _high-tech_ hardware like flash (or other non-volatile) memory in my 8-trillion-bit, 3 billion-bit-per-second, giant magneto-resistance-based hard disk ... Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fcd6a54.4060...@kempt.net
what did hwinfo do to my machine?
After I ran hwinfo (to detect a modem), my machine runs very slowly at the beginning of booting. (GRUB takes about 8 seconds between displaying the the Welcome to GRUB! text and the error: fd0 read error. text, and another 25 seconds for the screen to go blank on the way to displaying the menu. Kernel booting might be slow for the first dozen or so messages; after that, everything seems to be fine.) What the heck did hwinfo do to my machine? I thought hwinfo's probing changed some BIOS setting that maybe slowed down the CPU, but I reset the BIOS to default and re-set what I had set before, but that didn't seem to make any difference. Now I wonder if hwinfo changed some persistent setting in my disks. What tools are there to look at any settings of SATA disks? (This is all in Squeeze.) Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fcc33f9.1070...@kempt.net
can't copy/paste between gpm and emacs on virtual console/consoles
In Squeeze, in virtual consoles, I can't copy and paste between gpm and emacs (emacs-nox) as I could in Sarge. Trying to select and paste with the mouse in virtual consoles seems to show that emacs now recognizes virtual console mouse events and hooks them into its usual copy/paste mechanism. (Selecting text (by left-buttom-dragging) in a VC not displaying emacs (via gpm) and then middle-clicking to try to paste into emacs in a VC pastes text previously selected in emacs instead of the text just selected via GPM). Similarly, drag-selecting text in emacs in a VC and then middle-click pasting into a VC not displaying emacs pastes text previously selected via gpm insert of the text just selected via emacs. In the good old days, middle-click pasting to emacs in a virtual console would paste the text most recently selected by dragging in any virtual console.) How can I restore the old behavior (so that I can, say, select text in emacs and then paste that text into a shell (on another VC, or in the same VC after backgrounding emacs))? Where is emacs' configuration of its handling of virtual console mouse events? What do I set/unset to disable it? Thanks. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fca4f9a.5090...@kempt.net
Where is GRUB2's pointer to LVM LV / filesystem containing /boot?
Where does GRUB2 store its pointer information about which block device holds the filesystem containing /boot/grub (specifically, when using GPT partitioning)? Can that information be displayed (e.g., to see it before and after trying to change it, to confirm the change and which devices it's pointing to, to try to avoid getting stuck in an unbootable state)? (I meant to set up my system to have /boot on a RAID1 array, while having all other filesystems on LVM logical volumes (on top of other RAID1 arrays). However, I apparently forgot to configure /boot when I installed (using the Squeeze installer), so /boot is just part of the root filesystem (on an LVM logical volume). Surprisingly (because I thought GRUB2 handled only RAID1 but not LVM), GRUB2 and my system boot fine. I can see, via command completion in GRUB2's boot-time command-line mode, that GRUB2 detects all my LVM logical volumes. So how does the lower layer of GRUB2 know in which (virtual) block device to look to find /boot (to get to the configuration in /boot/grub)? It seems that the GRUB2 installer must have stored some data with the GRUB2 code in the special GPT partition that the installer's partitioner calls the BIOS Boot partition and parted lists as being of type bios_grub. Does GRUB2 store a UUID or something else? If it's a UUID, what's it the UUID of? (a filesystem? a virtual block device (e.g., and LVM logical volume or an mdadm RAID array)?) ) I think I want to move /boot to the RAID1 array I originally intended for it (so that booting into GRUB2 depends only on the /boot RAID1 array, and not also on the integrity of my LVM volumes). After I copy/move /boot to the RAID1 array, 1. how do I tell GRUB2 to look in the new place? and 2. how do I see the setting in the bios_grub partition (or wherever) to try to confirm that I got things right before I reboot and hope GRUB2 and my system boot back up? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fc2dd81.6060...@kempt.net
Re: OT: language
Tony van der Hoff wrote: ... I think he meant what he said. There is a nasty usage developing in English (in the UK, at least) for their singular, to denote he or she. I have resisted it so far. Actually, it's not just developing (recently developed)--apparently it first appeared decades ago. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fba86a7.4030...@kempt.net
Re: How do I remove a bad file??
Jochen Spieker wrote: Dan B.: No. Losing the display order setting is probably the _worst-case_ scenario The OP showed us an obvious case of file system corruption. He is lucky if he only lost this index file and no other files. He is *very* lucky if an fsck can repair the damage and nothing else is corrupted. Or maybe he is smart and has a backup. ;-) I thought you were referring to just the effect on SeaMonkey/Thunderbird of removing the .msf file (since your comment was right after my details about .msf files). Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa3e99c.20...@kempt.net
Re: ls sorting order change
Camaleón wrote: On Wed, 02 May 2012 15:28:33 -0400, Dan B. wrote: ... I guess now I need to figure out where I might like to see things in the new order vs. where I still want to see things in LC_COLLATE=C order.) Is that that new? The above output is from my Lenny system and that was the default setup two years ago :-? No, it's not really that new--just new to me because I got far behind in upgrading/updating my Debian system. (That's why I used quotes--to show that I didn't really mean the usual sense of new.) Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa2bfb9.1060...@kempt.net
Re: How do I remove a bad file??
Arnt Karlsen wrote: On Wed, 02 May 2012 15:39:05 -0400, Dan wrote in message ... ..if Inbox.msf is your email,... That looks like a Mozilla SeaMonkey or Thunderbird mail _index_ file. If it is, it can be deleted and SeaMonkey/Thunderbird will re-create it (from the corresponding mail data file) the next time the corresponding mail folder is opened/viewed. In my experience (as a long-time Mozilla user and occasional mail file hacker--but _not_ developer or expert), the only thing the OP might lose is his or her choice of display order (by date vs. sender, etc., and whether threaded display or not). ..that sounds like the very best case scenario. No. Losing the display order setting is probably the _worst-case_ scenario--mail messages are stored in a separate file, so deleting Inbox.msf definitely will not lose the mail message data in Inbox. Most of Inbox.msf is just indexing of Inbox for quicker listing of header in the UI and quicker access to the data in Inbox, and SeaMonkey re-creates Inbox.msf and that indexing data if Inbox.msf doesn't exist when you try to accessing the Inbox folder. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa2c1f7.9020...@kempt.net
Re: ls sorting order change
Wayne Topa wrote: On 05/01/2012 03:10 PM, Dan B. wrote: What controls the order that the ls command uses for sorting names? ... ... Well man ls says List information about the FILEs (the current directory by default). Sort entries alphabetically if none of -cftuvSUX nor --sort is specified. Guess you could start there. Yes, I did look at the manual page and saw that text. However, that didn't say anything about which definition of alphabetical ls uses. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa185f8.6090...@kempt.net
Re: ls sorting order change
Sven Joachim wrote: On 2012-05-01 21:10 +0200, Dan B. wrote: What controls the order that the ls command uses for sorting names? The locale or more specifically, the LC_COLLATE setting. See locale(7). ... .. LC_COLLATE=C for many years. Thanks. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa1862b.1050...@kempt.net
Re: ls sorting order change
Camaleón wrote: On Tue, 01 May 2012 15:10:23 -0400, Dan B. wrote: ... On a fresh Squeeze installation, ls seems to ignore leading . characters (it no longer lists all hidden files adjacent to each other) and to ignore capitalization differences. (...) Can you post a sample of the command you issued and the ouput you got? It was like (using made-up names): .aaa bbb ccc DDD EEE .fff when I expected: .aaa .fff DDD EEE bbb ccc (The first order is a typical order for English (case-insensitive, and ignoring punctuation), so now it makes sense that my default locale setting (LANG=en_US.UTF-8) yielded that order. The second order is plain old ASCII(/ISO-8859-x/Unicode) character order with no special treatment (ignoring or case-mapping) of characters--and setting LC_ALL=C (or LC_COLLATE=C) does indeed yield that order. I guess now I need to figure out where I might like to see things in the new order vs. where I still want to see things in LC_COLLATE=C order.) Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa18ae1.5010...@kempt.net
Re: How do I remove a bad file??
Arnt Karlsen wrote: On Wed, 2 May 2012 07:04:55 +0200, Jochen wrote in message 20120502050455.ga25...@well-adjusted.de: Dennis Wicks: Greetings; I have a file that looks like the following in an ls list; -? ? ?? ?? Inbox.msf I can't do anything with it. Can't mv, rm, cp, or anything else I have thought of to get rid of it or write over it. Any ideas how I can get this thing out of my life?? Fsck the filesystem. ..first, umount it right _now!_ ..if Inbox.msf is your email,... That looks like a Mozilla SeaMonkey or Thunderbird mail _index_ file. If it is, it can be deleted and SeaMonkey/Thunderbird will re-create it (from the corresponding mail data file) the next time the corresponding mail folder is opened/viewed. In my experience (as a long-time Mozilla user and occasional mail file hacker--but _not_ developer or expert), the only thing the OP might lose is his or her choice of display order (by date vs. sender, etc., and whether threaded display or not). Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa18d59.9010...@kempt.net
ls sorting order change
What controls the order that the ls command uses for sorting names? On a fresh Squeeze installation, ls seems to ignore leading . characters (it no longer lists all hidden files adjacent to each other) and to ignore capitalization differences. It used to sort in standard/traditional Unix order (not ignoring any characters, and ordering by order of characters in ASCII/etc. (as opposed to by case-insensitive alphabetical order)). What controls ls's sorting order? I haven't set any locale environment variable specifically for the collation order, but I don't know what base LANG=en_US.UTF-8 setting does. Does en_US imply that new sorting order? How do I tell ls to work the way I've seen it work for decades? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa0351f.8010...@kempt.net
gdm3 cancels/ignores Control/CapsLock swap
What is it about gdm3 that undoes (or otherwise ignores) swapping of Control and Caps Lock keys configured via /etc/default/keyboard? I have XKBOPTIONS=ctrl:swapcaps in /etc/default/keyboard. That works (the Control and Caps Lock keys are swapped) for virtual consoles and for X11 displays started with startx--both without and with GNOME installed. However, when I start gdm3, then in the X11 display managed started by gdm3, the keys are _not_ swapped any more. (That's both initially (when gdm3 prompts for username and password) and later (with the GNOME environment displayed).) Some Debian documentation or discussion says that the settings in /etc/default/keyboard are supposed to work for both virtual consoles and X11 (so one doesn't have to configure consoles and X11 separately). Why doesn't gdm3 follow that? Does it sound like I have a configuration problem, or does gdm3 have a bug (with respect to the intent that /etc/default/keyboard configures both VCs and X11 displays)? Thanks. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f956ad5.5050...@kempt.net
Re: Bash script problem [OT?]
Iuri Guilherme dos Santos Martins wrote:
When dealing with paths in bash i usually employ two things:
One is declaring arrays like this:
FILES_LIST=( )
And everytime I want to append to the array I go like this:
FILES_LIST=( ${FILES_LIST[@]} ${NEW_FILE} )
Obviously I will have problems if the paths or files have spaces in
their names, ...
Does this work?
FILES_LIST=( ${FILES_LIST[@]} ${NEW_FILE} )
(Read the part of the bash manual page that describes how ...[*]
and ...[@] act when inside double-quoted strings.)
Daniel
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f95fb6b.8020...@kempt.net
Re: Bash script problem [OT?]
I wrote:
...
FILES_LIST=( ${FILES_LIST[@]} ${NEW_FILE} )
You can also write:
FILE_LIST[${#FILE_LIST[@]}]=${NEW_FILE}
Daniel
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f961197.4010...@kempt.net
kernel modesetting - set only at boot, or changeable?
When KMS (kernel modesetting) is used, can the video mode (resolution) be changed after booting, or is it set only once, at boot time (or maybe at module-load time)? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f661558.7050...@kempt.net
Re: kernel modesetting - set only at boot, or changeable?
Jörg-Volker Peetz wrote: The resolution can be changed with KMS activated, e.g., with xrandr when X is running. Further reading: http://linux.koolsolutions.com/2009/11/02/howto-enabling-kernel-mode-setting-kms-in-debian-linux-kernel/ http://en.gentoo-wiki.com/wiki/Radeon Can it be changed before/without starting X? Currently I'm trying to solve the following problem (on a system not yet set up enough to run X): If I boot with my KVM switch connecting my monitor to my Squeeze system, I get a video resolution of 1920x1080 pixels (the resolution of my monitor), giving me virtual consoles with 240 x 67 characters. If I boot with my KVM switch connecting my monitor elsewhere, then of course I get a different video resolution--1024x768 pixels (apparently what my KVM sends in that state when the real monitor isn't connected), giving virtual consoles with 128 x 48 or so characters. I want to override Linux's auto-detection and just set the video resolution to 1920x1080 so that the resolution won't depend on the KVM switch state at boot time. Although I can set the video mode in Grub's command line for the kernel, I'd really prefer to do it somewhere in the booted system (e.g., via /etc/init.d/... and /etc/defaults/... or whatever) rather than in Grub on my shared /boot partition (which could get clobbered more easily).) Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f669cae.4030...@kempt.net
Gnome Ctrl key default not respecting default - which package?
I found why Gnome seemed to behave inconsistently regarding following Control-key settings in XKBOPTIONS in /etc/default/keyboard: GDM and the rest of Gnome work differently. In GDM, my Control key _is_ swapped as intended. (Apparently, GDM starts X without overriding keyboard settings, which X evidently _does_ get from my /etc/default/keyboard.) Once I log in at GDM's prompt and get the Gnome desktop, my Control key is no longer swapped. I checked Gnome's Keyboard Preferences. In the Options dialog, the Ctrl key position setting is set to default. However, Gnome is _NOT_ respecting my system/X11 default for the control key. (The help for that dialog box does not say anything about the default setting value's being _Gnome's_ default as opposed to the _system's_ default.) So (for submitting a bug report(s)), which package(s) are Gnome's keyboard configuration and its help data in? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec7cd78.90...@kempt.net
Re: Gnome Ctrl key default not respecting default - which package?
I wrote: I found why Gnome seemed to behave inconsistently regarding following Control-key settings in XKBOPTIONS in /etc/default/keyboard: GDM and the rest of Gnome work differently. ... Agh! It's even worse than that. Even within just gdm, the behavior is inconsistent: In gdm, when the list of user names plus Other... is listed, my Control key is swapped. However, when I click on any item in that list and get to gmd's password dialog box, the Control key is _not_ swapped! What the hell is gdm doing? Is gdm reading the keyboard at two different levels or something? Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec7d200.1000...@kempt.net
'pcspkr' is already registered aborting, breaking console video mode setup
I'm getting some inconsistent behavior. When I boot one installation of Squeeze on my machine, the kernel sets a high-resolution console video mode (240x67). However, when I boot either of two other installations of Squeeze on the same machine, I get just the initial low console resolution (80x25). On those installations, dmesg shows an error: Error: 'pcspkr' is already registered, aborting and only about 3 lines mentioning drm or radeon (vs. the couple dozen lines mentioning drm or radeon for installation 1's dmesg output). My question is not (yet) what to do about the pcspkr error itself (I have found some pages addressing it), but is this: Why are installations 2 and 3 breaking while installation 1 works? (And why did installation 2 work fine for a while and then start breaking?) As far as boot-time things (e.g., kernel settings), they're pretty much identical. (I followed similar steps in the installer each time.) Because the pcspkr message has appeared in a slightly different position, I wonder if the difference between the systems could be because of timing--installation 1 is on a PATA disk, and both installations 2 and 3 are on SATA disks. Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec53e44.6010...@kempt.net
Re: capturing console resolution from auto-detection for when KVM switched away?
Brian wrote: On Mon 14 Nov 2011 at 21:48:05 -0500, Dan B. wrote: When I boot with my monitor connected (through a KVM), I end up with high-resolution virtual consoles (67 rows by 240 columns). However, when I boot with the KVM switched away, then since the kernel/etc. can't auto-detect my monitor, I get lower resolutions (48 rows by 128 columns, or 25 by 80 once). Have you got that the right way round? My experience is that with a KVM the monitor's EDID may not get passed to the computer. I think so. Note that _both_ of my cases are with a KVM: the first is when the KVM is switched to (connecting the monitor, etc., to) the computer I'm talking about, and one is when the KVM is switched away from the computer I'm talking about (switched to an otherwise unrelated computer). (I'm not talking about the case of having the monitor connected directly to the computer.) Of course, I'd like to force it to use the higher resolution regardless of which computer my KVM is switched to when this computer boots. Something like video=DVI-1:1280x1024 as a kernel parameter (when KMS is used) works for me. What tools (commands) are there in console-data or console-tools or whatever for getting (and changing) the console video settings? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec28d55.3010...@kempt.net
Re: update-flashplugin-nonfree issue
J. Bakshi wrote: Dear list, I have run update-flashplugin-nonfree --install and it downloads the latest plugin at /var/cache/flashplugin-nonfree/install_flash_player_11_linux.x86_64.tar.gz after uncompromising it I get .. Once something has been compromised by the taint of being commercial/closed source, can it ever really be uncompromised again? :-) Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec28f5f.6000...@kempt.net
What's DE-specific, what's independent? (was: Re: KDE package manager)
Sian Mountbatten wrote: Doug dmcgarr...@optonline.net writes: On 11/09/2011 03:33 AM, Andrei POPESCU wrote: On Jo, 03 nov 11, 10:59:43, Ken Heard wrote: Sian Mountbatten wrote, in part: Is there a KDE package manager available? For the various things that get installed for Gnome, KDE, etc., which are specific to the chosen desktop environment, and which work with any desktop environment (or perhaps any sufficiently capable DE (e.g., FreeDesktop-compliant))? When a DE includes a (default) audio player, file manager, CD-writing program, etc., is the only thing specific to that DE the fact that it chose that program as its default for that type of application, or is the application usually tied to that DE? More generally, what I'm try to get at is: Of the things you get with a particular desktop environment (i.e., of the packages installed by installing a Gnome, KDE, etc., virtual package), which work only with that DE, and which work with other DE's you might switch to (or also run)? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec299a1.5050...@kempt.net
Re: [OT] can't see own post to the list
Scott Ferguson wrote: On 14/11/11 11:19, Dan B. wrote: Scott Ferguson wrote: On 13/11/11 16:14, Doug wrote: ... GMail deliberately removes your own list messages so you can't see them and know that you actually were successful in posting. Well, no. Not that I have shares in Google - just a dislike for BS and trolls. The gmail default settings is to *not* provide you with a duplicate in Sent mail. Why would there be a duplicate in _Sent_ mail? Only the message you sent out should be in the Sent folder--the message back from the mailing list is a different message ... ..., it is not a duplicate. Are you serious? Yes. What the heck are you questioning? If mail is in my Sent folder it only proves that my mailer got that far in sending it out. When the MDA delivers a copy (one from a mailing list server or just one caused by my BCC to myself, then I have proof that the mail got to the server. A mailer shouldn't forcibly* treat the second message as a duplicate of the first. (*That is, without giving the user a choice.) It sounds like GMail/Google is judging whether a message was Sent by the From: header field (or whatever) rather than by the simple fact of whether it was actually sent (through GMail's mail-sending actions) or received. Gmail's reasons for the policy have been posted previously in this thread. Yes, I know. Why do you think I wrote It sound like GMail/Google is judging ...? (A similar problem can also occur with BCC copies to oneself in some mailers.) Which would beg the question why would anyone do that - if I didn't have better things to do, or a total lack of desire to understand the reasoning of the insane. :-) You really shouldn't call people insane just because their reasons are something of which you are ignorant. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec14896.7050...@kempt.net
capturing console resolution from auto-detection for when KVM switched away?
What command shows the virtual console video mode (specifically, the information needed to set it to that mode if it's in a different mode)? When I boot with my monitor connected (through a KVM), I end up with high-resolution virtual consoles (67 rows by 240 columns). However, when I boot with the KVM switched away, then since the kernel/etc. can't auto-detect my monitor, I get lower resolutions (48 rows by 128 columns, or 25 by 80 once). Of course, I'd like to force it to use the higher resolution regardless of which computer my KVM is switched to when this computer boots. Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec1d2e5.1040...@kempt.net
Re: [OT] can't see own post to the list
Scott Ferguson wrote: On 13/11/11 16:14, Doug wrote: ... GMail deliberately removes your own list messages so you can't see them and know that you actually were successful in posting. Well, no. Not that I have shares in Google - just a dislike for BS and trolls. The gmail default settings is to *not* provide you with a duplicate in Sent mail. Why would there be a duplicate in _Sent_ mail? Only the message you sent out should be in the Sent folder--the message back from the mailing list is a different message (e.g., with added mail-transfer header fields (e.g., Received), mailing list header fields (e.g., List-ID), and modifications to the body (e.g., the mailing list signature), and is not the message you sent out. Although it usually contains almost everything from the original message (though not BCC header fields), it is not a duplicate. A mailer shouldn't forcibly* treat the second message as a duplicate of the first. (*That is, without giving the user a choice.) It sounds like GMail/Google is judging whether a message was Sent by the From: header field (or whatever) rather than by the simple fact of whether it was actually sent (through GMail's mail-sending actions) or received. (A similar problem can also occur with BCC copies to oneself in some mailers.) Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec05e81.7040...@kempt.net
Re: /etc/default/keyboard XKBOPTIONS not read by X
Andrei POPESCU wrote: On Vi, 11 nov 11, 17:23:16, Dan B. wrote: Something _really_ screwy seems to be going on here. I think Gnome is overriding the keyboard settings. Did you read the part about its setting the keyboard settings in its X server differently depending on whether an unrelated X server was running? Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ebe9f4d.30...@kempt.net
Re: /etc/default/keyboard XKBOPTIONS not read by X
Raf Czlonka wrote: On Wed, Nov 09, 2011 at 12:50:57AM GMT, Bob Proulx wrote: Dan B. wrote: I tried swapping the left Control key and Caps Lock key by modifying the XKBOPTIONS value in /etc/default/keyboard, per instructions that said it would take effect for both the virtual consoles and X. I presume you've restarted restarted udev or rebooted since then? I have now (rebooted). % udevadm trigger --subsystem-match=input --action=change Can we see the content of your file (without the comments), please? XKBMODEL=pc105 XKBLAYOUT=us XKBVARIANT= XKBOPTIONS=ctrl:swapcaps Could you also point us to the instructions you've used as well, please? http://shallowsky.com/blog/2011/Mar/20/ Note: I was mistaken in thinking that _that_ page said that the /etc/default/keyboard setting would take effect for both the virtual consoles and X. However, I read (somewhere else) that in Squeeze one could fix both the virtual consoles and X with one setting. (Also, the fact that /etc/default/keyboard uses the name XKB... and uses the X configuration format suggests that the file might also be read by X startup scripts.) Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ebd8ed8.50...@kempt.net
Re: /etc/default/keyboard XKBOPTIONS not read by X
Dan B. wrote: Raf Czlonka wrote: On Wed, Nov 09, 2011 at 12:50:57AM GMT, Bob Proulx wrote: Dan B. wrote: I tried swapping the left Control key and Caps Lock key by modifying the XKBOPTIONS value in /etc/default/keyboard, per instructions that said it would take effect for both the virtual consoles and X. ... XKBMODEL=pc105 XKBLAYOUT=us XKBVARIANT= XKBOPTIONS=ctrl:swapcaps Could you also point us to the instructions you've used as well, please? http://shallowsky.com/blog/2011/Mar/20/ Note: I was mistaken in thinking that _that_ page said that the /etc/default/keyboard setting would take effect for both the virtual consoles and X. However, I read (somewhere else) that in Squeeze one could fix both the virtual consoles and X with one setting. (Also, the fact that /etc/default/keyboard uses the name XKB... and uses the X configuration format suggests that the file might also be read by X startup scripts.) Hey, I just noticed that if I use startx (startx -- :1) to start X (and Gnome, etc), the Control key gets swapped;. It's in the X session started (or use?) by GDM that the Control key doesn't get swapped. Does that help identify the problem? Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ebd93a7.4020...@kempt.net
Re: /etc/default/keyboard XKBOPTIONS not read by X
I. wrote: Dan B. wrote: Raf Czlonka wrote: On Wed, Nov 09, 2011 at 12:50:57AM GMT, Bob Proulx wrote: Dan B. wrote: I tried swapping the left Control key and Caps Lock key by modifying the XKBOPTIONS value in /etc/default/keyboard, ... ... XKBOPTIONS=ctrl:swapcaps ... Hey, I just noticed that if I use startx (startx -- :1) to start X (and Gnome, etc), the Control key gets swapped;. It's in the X session started (or use?) by GDM that the Control key ^If it's ^used doesn't get swapped. Actually, it varies in GDM, apparently depending on whether another X server is still running: I rebooted. *In the original X server started automatically by/for GDM, Control was not swapped (as I reported above). I invoked startx ... to start another X server (and default Gnome session). *In that X server, Control was swapped (as I reported above). I exited that Gnome session and X server (with Gnome's Log Out menu item). In the original GDM-starte X server and Gnome session, I logged out and logged back in. *In that X server, Control was not swapped (as for the previous GDM-started X server). Again, I started an X server with startx. *In that X server, Control was again swapped (as for the previous startx-started X server). Without exiting that startx-started server, I went to GDM-started server, logged out and back in. *In that X server, Control *was* swapped (different than in the previous two GDM-started X servers). Something _really_ screwy seems to be going on here. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ebda054.6070...@kempt.net
Re: samba weirdly taking wrong password - never mind (mostly solved)
I wrote: I'm having a really weird problem: the Samba server accepts a _wrong_ password instead of the expected password. ... Never mind. I finally figured out that Samba was checking some Samba layer of passwords instead of the regular Linux password layer. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ebaa89e.4020...@kempt.net
Re: sh scriptname malfunction after upgrade
J. Bakshi wrote: On Wed, 9 Nov 2011 12:34:57 +0100 Jochen Spieker m...@well-adjusted.de wrote: ... You need to either run bash -x script or use set -x in the script. Thanks , so is it a backward compatibility ? Shall I place set -x just after #!/bin/bash ? You can also use this: #!/bin/bash -x Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ebaad42.2040...@kempt.net
/etc/default/keyboard XKBOPTIONS not read by X
I tried swapping the left Control key and Caps Lock key by modifying the XKBOPTIONS value in /etc/default/keyboard, per instructions that said it would take effect for both the virtual consoles and X. However, it works only for the virtual consoles, and not for X (neither when started by GDM nor when started by startx (with GDM disabled)). This on a fresh Squeeze installation. (Hmm. A freshly Squeezed compu... never mind.) Is something else necessary? Or are those instructions obsolete? Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eb94f11.2060...@kempt.net
Re: How to ifdown ... on squeeze?
Bob Proulx wrote: Tom H wrote: Dan B. wrote: ... How does one take an interface down on squeeze? The expected tool on a GNOME system would be by using the NetworkManager GUI with the mouse or as Tom writes, 'nmcli' from the command line. Something like this: # nmcli conn down id 'Auto eth0' # nmcli conn up id 'Auto eth0' (with a commented-out line: #NetworkManager#iface eth0 inet dhcp For the background of that comment see the bug report here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530024#49 ... When NM controls your connections, NICs aren't defined in /etc/network/interfaces, by default; you can change that behavior by changing the managed variable of the ifupdown section of /etc/NetworkManager/networkmanager.conf. You can also use nmcli to take down and bring up your NIC. My recommendation is to edit that commented out line and remove it from NetworkManager's control and return it to ifupdown's control. ... Thanks. Yes, I'll probably take control back to normal Linux commands. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eb850d1.3000...@kempt.net
Re: How to ifdown ... on squeeze?
Tom H wrote: ... NM's only controversial because there are people who oppose change not matter why it might be. ... So are you lumping people who oppose having things break out from under them, such as, say, someone installing a new release and finding that standard Unix(?)/Linux networking commands no longer work, into your people who oppose change [no] matter why category? As Bob wrote elsewhere), a more (newbie-)user-friendly layer (e.g., GNOME components) should call the standard interface, not break it. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eb85316.40...@kempt.net
Re: Understanding versioning.
Sthu Deus wrote: Thank You for Your time and answer, Camaleón: It is provided to allow mistakes in the version numbers of older versions of a package, and also a package's previous version numbering schemes, to be left behind. What does this mean? From other posts in the thread it is still not clear to me. If You can explain, please do so. Also what is epoch in this sense? I now time is measured in UNIX systems since the first system ran - it's obvious - a new great OS generation has started and till now rolls on. But what about the package epoch they use? First, don't think of second or fifth (per http://dictionary.reference.com/browse/epoch) senses of epoch-- the _beginning_ of some period (the meaning used re Unix time). Think of the first or fourth senses--a _period_ of time. Then, think of a package version epoch as the period of time during which a coherent (i.e., ascending) sequence of version numbers is used. If such a period ends because, say because you issue a new version number that is lower than (and therefore seems older than) an older version number, a way to resolve the confusion is to declare that you have switched to using a new system of version numbers. The package version epoch number identifies in which system of version numbers a given version number reference is written. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eb85a7a.8030...@kempt.net
samba weirdly taking wrong password
Does anyone recall whether Samba had problems with truncating passwords, or possibly with mixing up user IDs and/or passwords between the serving side and the clienting side (mounting other machines' shares)? I'm having a really weird problem: the Samba server accepts a _wrong_ password instead of the expected password. The wrong password that it is accepting is both: 1) the prefix (n-1 characters out of n) of the expected password (the password of a user account on the Linux system running samba) and 2) the password of a (supposedly) unrelated Windows user account on a Windows machine that happens to mount two shares from the Linux system and serve out two shares mounted by that Linux system. I _think_ the Windows user account should be completely unrelated, because I don't use any Windows domain or Samba equivalent. However, both the Windows system and the Linux system have user accounts with the same name U, and when Windows user U is logged on, there is a Windows mount, using Linux user account U, of the samba- served share. That makes me wonder if samba is mixing up the two different user accounts because they have the same name. However, I don't see how samba in Linux would ever get the password for the Windows user account: Although Windows needs to pass the password for Linux account U (which I gave to Windows when I set up the mounting) to samba, it never needs to pass the password for _Windows_ account U, right? (The Linux machine mounts the Windows shares using a different Windows user account (with a non-duplicate name), so that mounting seems completely unrelated.) The clienting I'm doing is mounting a samba-served share using mount -t cifs -o user=... ... and entering a password at the prompt. When I enter the expected password (the n-character password of the corresponding user account), it fails with samba's -13 permission error. When I enter the supposedly wrong password, it succeeds (and the share is mounted). That failure and success is the same whether the mount command is issued on the sarge Linux machine running the samba server or is issued on brand-new squeeze Linux machine. (The sarge machine's samba version is 3.0.14a-3sarge11.) Any ideas? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eb870bb.70...@kempt.net
How to ifdown ... on squeeze?
On a new installation of squeeze, ifdown no longer works as it used to (on my old Debian system). When ifconfig lists an interface eth0, neither ifdown eth0 nor ifdown eth takes the interface down. The attempts yield: ifdown: interface eth0 not configured and ifdown: interface eth not configured. How does one take an interface down on squeeze? (My old system's /etc/network/interfaces had: ... auto eth0 iface eth0 inet dhcp On my squeeze system, it's: ... allow-hotplug eth0 (with a commented-out line: #NetworkManager#iface eth0 inet dhcp ) ) Also: The reason I was trying to take it down and back up was to trigger a fresh DHCP query and corresponding host-name configuration. What's the preferred way of doing that? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eb7376b.9080...@kempt.net
Re: Firware drivers?
Camaleón wrote: ... ... let me add that any system upgrade is capable of breaking thinks. For those who want/need a smooth upgrade I would recommend to install the new release in parallel with the old release, that is, leaving lenny at the same state and perform a new install of Squeeze in a different partition. So if something wrong happens, you can always boot the old version and work with that. Is time consuming and requires double disk space but for many environments thats should not be a problem at all. A related option is to clone the core of your system and then upgrade one copy (leaving the other copy bootable in case of problems with the udgrade). (That is, clone the root file system to a new partition, make it bootable by adjusting a few things (such as Grub/LILO and /etc/fstab), and the updgrade either the original or the clone.) Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d5ee3bc.80...@kempt.net
Re: piping find to zip -- with spaces in path
Bob Proulx wrote: Dan B. wrote: Bob Proulx wrote: So as you can see whitespace isn't safe to use in URLs. This is basically the same as for Unix filenames. They're not quite the same: Not quite the same is basically the same here. :-) Okay. They're not the same. So they're not basically the same. The question of the topic was: ... what about urls? They come from the Unix world, and are full of underscores and question marks and equal signs. Then there are emails, all of which require the @ sign. Not complaining, just asking. I think basically the same describes things adequately. Having a clear specification and having things build on it consistently (at least mostly) is not basically the same as not having any clear specification and having inconsistent support for spaces. There's a major difference between the two--in the first case you can easily, definitely know what must be supported (at least to be compliant, correct, complete, or whatever) but in the second case you can't. People with a Unix background wouldn't normally include spaces in either of file names or URLs, or other related handles to data. If you do then they are much more of a pain to manipulate in shell scripts. And so you just don't do it... No argument there. and don't think about whether it is technically possible or not. Except when you're trying to write scripts (etc.) that don't break the instant someone _else_ or some _other_ tool uses characters you didn't happen to use or think of. Remember that it's not just space characters. For example, when a kernel driver file used a comma in its name, Emacs' etags feature broke because it used commas to delimit filenames (with no encoding/escaping mechanism). ... In URIs, it's not that whitespace isn't safe to use; it's simply that whitespace is not allowed, period. ... No. Actually it was exactly that, unsafe. *Exactly* as I said. RFC 1738 The space character is unsafe because ... Literally they are documented as being unsafe. That is not the specification; that is the rationale for what was specified. The reason we avoid putting spaces in (real) URIs isn't just that spaces are unsafe (e.g., something might break). The reason we avoid putting spaces in (real) URIs is because they are not allowed by the specification. Later RFCs have clarified this somewhat. But regardless of being unsafe most software does actually allow them. (I sometimes see them inappropriately used in slug lines.) wget -O- http://www.example.com/one two three.html Fine. Wget's argument is not a URI but some other kind of string. (So does that wget argument generate the URI http://www.example.com/onetwothree.html; or the URI http://www.example.com/one%20two%20three.html;?) And even though the space hasn't been included in the possible characters RFC 3986 includes this statement: Using angle brackets around each URI is especially recommended as a delimiting style for a reference that contains embedded whitespace. Pay attention to the words reference and URI there. They don't mean the same thing: That's so that a _reference_ in text to a URI can have whitespace inserted to allow line wrapping. The thing that contains that space is NOT a URI, but some kind of reference to a URI--and the W3C says that such whitespace is removed when mapping that reference back to the URI is represents (that is, the whitespace characters are not to be encoded as %20, etc.). ... Unfortunately, on the other hand, Unix filenames have no corresponding specification, at least one that is followed consistently. The kernel and file systems allow spaces, and some utilities/commands/scripts/etc. do, but many don't. The Unix filesystem allows all characters except for the zero character. Because the zero character delimits the end of the string it cannot be used in the string. And of course the '/' is used as a directory separator. If an application doesn't allow other characters then it is arguably a bug in that application. (However the application may document its limitations and stop there.) Core utilities will of course be okay but I am sure that fringe applications have bugs in them. Right, other than that without a clear specification of what's supposed to be, it's harder to say whether an application is buggy/limited or not. Partially, I wish Unix/Linux were like VMS in how VMS defined which characters were legal or not in filenames. Because of that definition, it was clear which characters would never, ever appear in a file name and therefore could be used in, say, command line interpreter syntax without causing things to break on somebody else's chosen file names. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d30b1ac.3070...@kempt.net
Re: piping find to zip -- with spaces in path
Bob Proulx wrote: Bob Proulx wrote: ... So as you can see whitespace isn't safe to use in URLs. This is basically the same as for Unix filenames. They're not quite the same: In URIs, it's not that whitespace isn't safe to use; it's simply that whitespace is not allowed, period. (Yes, encodings of whitespace characters are allowed, but that encoding still contains no actual whitespace characters.) That's clearly defined by a specification (IETF RFC 3986 _Uniform Resource Identifier (URI): Generic Syntax_, http://tools.ietf.org/html/rfc3986). Additionally, various other syntaxes and protocols build on that consistently (e.g., since URIs can never contain space characters, HTTP uses space characters as delimiters around URI references). Unfortunately, on the other hand, Unix filenames have no corresponding specification, at least one that is followed consistently. The kernel and file systems allow spaces, and some utilities/commands/scripts/etc. do, but many don't. Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d2f8f3e.7030...@kempt.net
