Re: I need guidance about how to configure a newly installed Jessie
On Sat, 18 Apr 2015 20:18:17 -0600 Paul E Condon wrote: > On 20150418_1905-0500, David Wright wrote: > > Quoting Paul E Condon (pecon...@mesanetworks.net): > > > > > I was running as pec or as root. I forget. Since doing that, I > > > realized that for many years I have been running with my own > > > version of /etc/ssh/ssh.config. Confronted with the evidence, I > > > recall that this was a place I found, through exhaustive search, > > > to turn off the hashing of known_host. I like to be able to > > > identify lines in known_host, because I think each line is a > > > possible access path for a hacker and the sysadmin, namely me, > > > should be able to trace the provenance of all such lines. In > > > short hashing them opens a backdoor more serious than the one it > > > closes, IMHO. I now know that I can put my edits in two > > > places, /home/pec/.ssh/ssh_config and /root/.ssh/ssh_config, and > > > have the same effect. > > > > If you're happy with not hashing, you need only put that in > > /etc/ssh/ssh_config (underscore, not dot) if you remove all other > > .ssh/ssh_config files. > > > > > I can envision a different way, but I cannot envision one that > > > does not impact of how Debian wants to configure Jessie. So be it. > > > > When upgrade runs, you'll need to keep your configuration and then > > run diff against the maintainer's version (suffixed .dpkg-new > > or .ucf-dist or some such) to fold in any changes they've made > > (likely to be few to none). > > > > > I have not yet discovered a way to append new known host keys > > > from newly configured hosts into the .ssh/known_hosts files on > > > older computers. > > > > known_hosts and authorized_keys are both text files. Each line is > > independent. You can cat x >> y to append contents of x to y or > > insert with an editor. An editor's Insert File is safe, but make > > sure to reconstruct the lines if cut and paste does any line > > wrapping, ie > > > > ssh-rsa > > jhdgkhkkdjkjnskjn > > foo@bar > > > > needs to be made back into > > > > ssh-rsa jhdgkhkkdjkjnskjn foo@bar > > > > IIRC any line from one hosts's or user's known_hosts file will work > > for another user and/or host, and the same with authorized_keys > > (though don't mix them up!). > > > > > I think the removed file was the one associated with either pec, > > > or root, which ever was appropriate for a test. Since doing the > > > tests, I have done a complete re-install. With that removing the > > > appropriate known_hosts file gives me the old familiar option of > > > accepting the risk of man-in-the-middle. > > > > There's never a problem with wiping out known_hosts and letting it > > gradually be rebuilt, particularly if you know the fingerprints > > thusly: > > > > > > $ ssh-keygen -l -v -f /etc/ssh/ssh_host_ecdsa_key.pub > > > > > .../ssh-fingerprint > > > > > As said before, I am working now with a new re-install on my main > > > computer. It is the one on which I am composing this email. > > > This is its /etc/hosts file: > > > > > 127.0.0.1 localhost > > > 127.0.1.1 big.lan.gnu big > > > > > > 192.168.1.1 rtr.lan.gnu rtr # LAN side of router > > > 192.168.1.10 cmn.lan.gnu cmn > > > 192.168.1.11 big.lan.gnu big > > > 192.168.1.12 gq.lan.gnu gq > > [...] > > > > > The top two lines were provided during the running of netinst CD > > > RC2. The rest were provided by me, after I took the CD out of the > > > computer and rebooted. > > > > Well I have tried to keep things as simple as possible and I > > recently decided to call exim's bluff... > > I don't think I have a problem with exim. I use msmtp to get emails > out onto the web. I tried doing it with exim4 about 2yrs ago. It kept > breaking so I found alternative for a previous stand-alone smtp agent > that was being discontinued due to lack of upstream support at about > the same time that Debian was moving from plain exim to exim4. I > could try again, but after I get ssh working both directions, I hope. > > > > > Starting MTA:hostname --fqdn did not return a fully qualified > > name, dc_minimaldns will not work. Please fix your /etc/hosts setup. > > exim4 ok > > > > ...and configure a null domain (ie no dots in /etc/hosts outside of > > the IP numbers). Everything still works. > > > > > With this, I can ssh into 'gq' from 'big', which is my main > > > computer with the big flat screen display. I can open and edit > > > files on 'gq' and the edits will be saved. No problem. But, if I > > > sit down the keyboard and screen connected to 'gq', I cannot do > > > the reverse. On 'gq', the /etc/hosts file contains all the lines > > > as on 'big', except for the first two. > > > > It should contain the first two lines exactly the same except > > substitute big→gq. > > > > > Working on 'gq', I cannot ping ['big']. Can you > > > tell be why, and what I can do to make the ping possible. It > > > would be very educational for me, and maybe all other problems > > > will fall
Re: [solved] Re: Change partition numbering
David Wright writes: > Quoting Joe (j...@jretrading.com): >> >> Everything else is likely to refer to the mount points in >> fstab, and if mounting is by UUID, presumably nothing needs to be done >> even there. > > Indeed, and also if using LABELs. That's why I wondered about the > reason for making the change if it was at all risky (which it turned > out not to be). The OP didn't say. I said, that I had to ptoperly edit fstab and, also, reisntall grub boot loader to mbr, with Debian Installer rescue mode. The system wouldn't boot any more. Rodolfo -- 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/87y4loskdw@gmail.com
Re: bugs found
Quoting Richard Jasmin (frazzledj...@gmail.com): > I have a bug in liberoffice writer that puts text on a new line instead > of using the spacebar to do so. > I cant report the bug as the packages is not listed for liberoffice. ...because there's no such package. OTOH there is one called libreoffice. BTW you might consider choosing a more informative Subject: line for your posting if you want anyone to find/read it. If/when you report the bug, you will be specifically asked to do this. Cheers, David. -- 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/20150419050431.GC20569@alum
Re: [solved] Re: Change partition numbering
Quoting Joe (j...@jretrading.com): > > What happens next depends on exactly what's on the partitions, and > where the references to /dev/sda1, etc. are. I think there is only > likely to be trouble where grub is involved, as it stores actual disc > locations. I think you're confusing grub with LILO. Grub can read partition tables, UUIDs, LABELs and filesystems. > Everything else is likely to refer to the mount points in > fstab, and if mounting is by UUID, presumably nothing needs to be done > even there. Indeed, and also if using LABELs. That's why I wondered about the reason for making the change if it was at all risky (which it turned out not to be). The OP didn't say. Cheers, David. -- 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/20150419045542.GB20569@alum
Re: apt-offline usage
From: franc...@avalenn.eu Date: Thu, 9 Apr 2015 16:55:01 +0200 > isolated$ apt-offline set --update ... > networked$ apt-offline get ... > isolated$ apt-offline install > isolated$ apt-offline set --upgrade ... > networked$ apt-offline get ... > isolated$ apt-offline install ... > isolated$ apt-get upgrade Appears OK until apt-get upgrade. For example; root@joule:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@joule:/# dpkg -l openssl Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii openssl1.0.1e-2+deb i386 Secure Socket Layer (SSL) binary Whereas a newer deb file certainly is available locally. root@joule:/# ls /var/cache/apt/archives/open* /var/cache/apt/archives/openssl_1.0.1k-3_i386.deb I've found no mention of sources in any apt-offline documentation. For "apt-offline set ..." and "apt-offline get ..." sources.list should refer to a networked source. For "apt-offline install ..." sources.list should refer to the local files in isolated:/var/cache/apt/archives/. No mention of this in the manual. Regards, ... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 12 Tel +13606390202 http://easthope.ca/peter.html Bcc: peter at easthope. ca -- 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/E1YjgR2-Np-DN@armada
Re: Debian 7 and external monitors and graphics adaptors
Quoting John Hasler (jhas...@newsguy.com): > Celejar writes: > > I run my main browser instance with all JavaScript disabled… > > So do I. Lots of sites put up banners warning me that some "features" > may not operate properly without JS but generally those are exactly the > "features" that I specifically don't want. A few other sites really > won't work usefully without JS. I've not done this (yet). Would I be right in assuming it's as simple as setting javascript.enabled to false in about:config (iceweasel)? What sorts of "features" might not work? With JS enabled (as it has been for me) and Flash available (at the moment I have to "Allow Now" on each page) there are odd sites that still will not work, eg https://www.capitalone.com/ where, if I try to login, it just says "The connection to the server was reset while the page was loading." in the place where the username/password would be typed. Any ideas on what I might have misconfigured or have missing? (I can only login with chromium; that's the only site I have visited with it.) > In that case I either go elsewhere or > temporarily enable JS for that site only. But just how bad do you consider JS to be? Does it deserve the expletive epithet; is it malware? (I don't know a lot about it. I'm barely past the stage of confusing it with its nominative cousin, java.) Cheers, David. -- 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/20150419044436.GA20569@alum
Re: Encrypting an External HDD
On Fri, 17 Apr 2015 14:25:36 -0700
David Christensen wrote:
> On 04/17/2015 12:41 PM, Reco wrote:
...
> > [Perl's Math::Random::ISAAC::XS] doesn't seem to use kernel-based entropy
> > at all. Thank
> > you for pointing me out at it, now I know it so I avoid it.
>
> ISAAC is very useful when I want a repeatable stream of random numbers,
> such as for testing.
>
>
> ISAAC can generate cryptographically secure random number streams by
> feeding it a "good" random seed:
>
> 2015-04-17 14:22:23 dpchrist@t2250 ~
> $ time dd if=/dev/random bs=16 count=1 2>/dev/null | perl
> -MMath::Random::ISAAC::XS -e
> '$r=Math::Random::ISAAC::XS->new(@ARGV);while(print $r->irand){}' | dd
> iflag=fullblock of=/dev/null bs=1M count=100 2>/dev/null
>
> real 0m18.350s
> user 0m18.305s
> sys 0m0.256s
Yes, this is what Math::Random::Secure does - it seeds
Math::Random::ISAAC from /dev/urandom:
http://search.cpan.org/~mkanat/Math-Random-Secure-0.06/lib/Math/Random/Secure.pm#IMPLEMENTATION_DETAILS
Celejar
--
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/20150418223356.c8fa4a705dac88e82dbda...@gmail.com
Re: I need guidance about how to configure a newly installed Jessie
On 20150418_1905-0500, David Wright wrote: > Quoting Paul E Condon (pecon...@mesanetworks.net): > > > I was running as pec or as root. I forget. Since doing that, I > > realized that for many years I have been running with my own version > > of /etc/ssh/ssh.config. Confronted with the evidence, I recall that > > this was a place I found, through exhaustive search, to turn off the > > hashing of known_host. I like to be able to identify lines in > > known_host, because I think each line is a possible access path for a > > hacker and the sysadmin, namely me, should be able to trace the > > provenance of all such lines. In short hashing them opens a backdoor > > more serious than the one it closes, IMHO. I now know that I can put > > my edits in two places, /home/pec/.ssh/ssh_config and > > /root/.ssh/ssh_config, and have the same effect. > > If you're happy with not hashing, you need only put that in > /etc/ssh/ssh_config (underscore, not dot) if you remove all other > .ssh/ssh_config files. > > > I can envision a different way, but I cannot envision one that does > > not impact of how Debian wants to configure Jessie. So be it. > > When upgrade runs, you'll need to keep your configuration and then run > diff against the maintainer's version (suffixed .dpkg-new or .ucf-dist > or some such) to fold in any changes they've made (likely to be few to > none). > > > I have not yet discovered a way to append new known host keys from newly > > configured hosts into the .ssh/known_hosts files on older computers. > > known_hosts and authorized_keys are both text files. Each line is > independent. You can cat x >> y to append contents of x to y or > insert with an editor. An editor's Insert File is safe, but make sure > to reconstruct the lines if cut and paste does any line wrapping, ie > > ssh-rsa > jhdgkhkkdjkjnskjn > foo@bar > > needs to be made back into > > ssh-rsa jhdgkhkkdjkjnskjn foo@bar > > IIRC any line from one hosts's or user's known_hosts file will work > for another user and/or host, and the same with authorized_keys > (though don't mix them up!). > > > I think the removed file was the one associated with either pec, or root, > > which ever was appropriate for a test. Since doing the tests, I have done > > a complete re-install. With that removing the appropriate known_hosts file > > gives me the old familiar option of accepting the risk of man-in-the-middle. > > There's never a problem with wiping out known_hosts and letting it > gradually be rebuilt, particularly if you know the fingerprints thusly: > > > > $ ssh-keygen -l -v -f /etc/ssh/ssh_host_ecdsa_key.pub > > > > .../ssh-fingerprint > > > As said before, I am working now with a new re-install on my main computer. > > It is the one on which I am composing this email. > > This is its /etc/hosts file: > > > 127.0.0.1 localhost > > 127.0.1.1 big.lan.gnu big > > > > 192.168.1.1 rtr.lan.gnu rtr # LAN side of router > > 192.168.1.10 cmn.lan.gnu cmn > > 192.168.1.11 big.lan.gnu big > > 192.168.1.12 gq.lan.gnu gq > [...] > > > The top two lines were provided during the running of netinst CD RC2. > > The rest were provided by me, after I took the CD out of the computer > > and rebooted. > > Well I have tried to keep things as simple as possible and I recently > decided to call exim's bluff... I don't think I have a problem with exim. I use msmtp to get emails out onto the web. I tried doing it with exim4 about 2yrs ago. It kept breaking so I found alternative for a previous stand-alone smtp agent that was being discontinued due to lack of upstream support at about the same time that Debian was moving from plain exim to exim4. I could try again, but after I get ssh working both directions, I hope. > > Starting MTA:hostname --fqdn did not return a fully qualified name, > dc_minimaldns will not work. > Please fix your /etc/hosts setup. > exim4 ok > > ...and configure a null domain (ie no dots in /etc/hosts outside of > the IP numbers). Everything still works. > > > With this, I can ssh into 'gq' from 'big', which is my main computer with > > the big > > flat screen display. I can open and edit files on 'gq' and the edits will be > > saved. No problem. But, if I sit down the keyboard and screen connected to > > 'gq', > > I cannot do the reverse. On 'gq', the /etc/hosts file contains all the > > lines as > > on 'big', except for the first two. > > It should contain the first two lines exactly the same except > substitute big→gq. > > > Working on 'gq', I cannot ping ['big']. Can you > > tell be why, and what I can do to make the ping possible. It would be very > > educational for me, and maybe all other problems will fall away in my > > basement. > > >From what you have posted, I would imagine that big has come up as > 192.168.1.X where X is not 11. /sbin/ifconfig will tell you the IP > number of the machine it's run on. /usr/sbin/arp -n -a run on gq > (during or soon after you have talked to
Re: Debian 7 and external monitors and graphics adaptors
Celejar writes: > I run my main browser instance with all JavaScript disabled… So do I. Lots of sites put up banners warning me that some "features" may not operate properly without JS but generally those are exactly the "features" that I specifically don't want. A few other sites really won't work usefully without JS. In that case I either go elsewhere or temporarily enable JS for that site only. -- John Hasler jhas...@newsguy.com Elmwood, WI USA -- 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/874mocvq9t@thumper.dhh.gt.org
Re: Debian 7 and external monitors and graphics adaptors
On Fri, 17 Apr 2015 08:38:43 + (UTC) Liam O'Toole wrote: ... > So do you normally run browsers on squeeze with javascript /dis/abled? I'm > surprised that any modern web sites work at all. I run my main browser instance with all JavaScript disabled, and many / most of the sites I use run perfectly well (e.g., Google, The New Republic, The Washington Post, The Atlantic, The New Yorker, Ars Technica, to name a few of the more prominent ones I currently have open). Celejar -- 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/20150418212914.288aabff0a13eddbb04c9...@gmail.com
Re: I need guidance about how to configure a newly installed Jessie
Quoting Paul E Condon (pecon...@mesanetworks.net): > I was running as pec or as root. I forget. Since doing that, I > realized that for many years I have been running with my own version > of /etc/ssh/ssh.config. Confronted with the evidence, I recall that > this was a place I found, through exhaustive search, to turn off the > hashing of known_host. I like to be able to identify lines in > known_host, because I think each line is a possible access path for a > hacker and the sysadmin, namely me, should be able to trace the > provenance of all such lines. In short hashing them opens a backdoor > more serious than the one it closes, IMHO. I now know that I can put > my edits in two places, /home/pec/.ssh/ssh_config and > /root/.ssh/ssh_config, and have the same effect. If you're happy with not hashing, you need only put that in /etc/ssh/ssh_config (underscore, not dot) if you remove all other .ssh/ssh_config files. > I can envision a different way, but I cannot envision one that does > not impact of how Debian wants to configure Jessie. So be it. When upgrade runs, you'll need to keep your configuration and then run diff against the maintainer's version (suffixed .dpkg-new or .ucf-dist or some such) to fold in any changes they've made (likely to be few to none). > I have not yet discovered a way to append new known host keys from newly > configured hosts into the .ssh/known_hosts files on older computers. known_hosts and authorized_keys are both text files. Each line is independent. You can cat x >> y to append contents of x to y or insert with an editor. An editor's Insert File is safe, but make sure to reconstruct the lines if cut and paste does any line wrapping, ie ssh-rsa jhdgkhkkdjkjnskjn foo@bar needs to be made back into ssh-rsa jhdgkhkkdjkjnskjn foo@bar IIRC any line from one hosts's or user's known_hosts file will work for another user and/or host, and the same with authorized_keys (though don't mix them up!). > I think the removed file was the one associated with either pec, or root, > which ever was appropriate for a test. Since doing the tests, I have done > a complete re-install. With that removing the appropriate known_hosts file > gives me the old familiar option of accepting the risk of man-in-the-middle. There's never a problem with wiping out known_hosts and letting it gradually be rebuilt, particularly if you know the fingerprints thusly: > > $ ssh-keygen -l -v -f /etc/ssh/ssh_host_ecdsa_key.pub > .../ssh-fingerprint > As said before, I am working now with a new re-install on my main computer. > It is the one on which I am composing this email. > This is its /etc/hosts file: > 127.0.0.1 localhost > 127.0.1.1 big.lan.gnu big > > 192.168.1.1 rtr.lan.gnu rtr # LAN side of router > 192.168.1.10 cmn.lan.gnu cmn > 192.168.1.11 big.lan.gnu big > 192.168.1.12 gq.lan.gnu gq [...] > The top two lines were provided during the running of netinst CD RC2. > The rest were provided by me, after I took the CD out of the computer > and rebooted. Well I have tried to keep things as simple as possible and I recently decided to call exim's bluff... Starting MTA:hostname --fqdn did not return a fully qualified name, dc_minimaldns will not work. Please fix your /etc/hosts setup. exim4 ok ...and configure a null domain (ie no dots in /etc/hosts outside of the IP numbers). Everything still works. > With this, I can ssh into 'gq' from 'big', which is my main computer with the > big > flat screen display. I can open and edit files on 'gq' and the edits will be > saved. No problem. But, if I sit down the keyboard and screen connected to > 'gq', > I cannot do the reverse. On 'gq', the /etc/hosts file contains all the lines > as > on 'big', except for the first two. It should contain the first two lines exactly the same except substitute big→gq. > Working on 'gq', I cannot ping ['big']. Can you > tell be why, and what I can do to make the ping possible. It would be very > educational for me, and maybe all other problems will fall away in my > basement. >From what you have posted, I would imagine that big has come up as 192.168.1.X where X is not 11. /sbin/ifconfig will tell you the IP number of the machine it's run on. /usr/sbin/arp -n -a run on gq (during or soon after you have talked to gq on big) will tell you how gq sees big (recognised by its MAC address). > Notice the difference in IP address for localhost and big.lan.gnu . This is > real, > not a typing mistake in transcription. Is it important? Debian's philosophy is outlined at https://lists.debian.org/debian-boot/2005/06/msg00639.html though I mentally delete ".localdomain" as I read it. So much un*x and Internet documentation is written by and for people whose machines have an Internet address, as that's how it used to be. Not so much has been written for people running a network at home, and it tends to be inconsistent precisely because it's only applicable locally. How are you m
Re: [solved] Re: Change partition numbering
Rodolfo Medina writes: > Rodolfo Medina writes: > >> After resizing a partition on my hard disk, partition numbering changed and >> now number 7 comes before and number 6 comes after: >> >> Model: ATA SAMSUNG MP0402H (scsi) >> Disk /dev/sda: 40.1GB >> Sector size (logical/physical): 512B/512B >> Partition Table: msdos >> Disk Flags: >> >> Number Start End SizeType File system Flags >> 1 32.3kB 8390MB 8390MB primary fat32 boot >> 2 8390MB 40.1GB 31.7GB extended lba >> 5 8390MB 9434MB 1045MB logical linux-swap(v1) >> 7 9434MB 26.2GB 16.8GB logical ext3 >> 6 26.2GB 40.1GB 13.8GB logical ext3 >> >> Is it possible, and how?, to correct that and change back 7 with 6? >> Googling around found no solution. > > I found this article: > > > http://unix.stackexchange.com/questions/18752/change-the-number-of-the-partition-from-sda1-to-sda2/18759#18759 > > According to it, I did: > > # sfdisk -d /dev/sda > myfile > > and edited sda.bkp my way. Sorry, I mean `edited myfile'. > Then, > > # sfdisk --no-reread -f /dev/sda < myfile > > . Then I edited /etc/fstab properly and rebooted. But then I had to rescue > the system: from a Debian installation disk, in rescue mode, from the boot > partition, I did: > > # grub-install /dev/sda > > , then rebooted and now it seems ok. Maybe I had to give the last command > before rebooting the first time. > > Rodolfo -- 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/87zj65cb0i@gmail.com
Re: I need guidance about how to configure a newly installed Jessie
On 20150418_1222-0600, Paul E Condon wrote: > On 20150417_1408-0500, David Wright wrote: > > Quoting Paul E Condon (pecon...@mesanetworks.net): > > > > > I have four desktop machines running Jessie. I try to keep them a;; > > > upgraded on whenever new package versions are released. I thought it > > > would be fast and simple. I was very wrong. This install behaves very > > > differently in the following way: When I attempt to ssh into one of > > > the computers that was not re-installed, I get a complaint that: > > > > > > @@@ > > > @ WARNING: POSSIBLE DNS SPOOFING DETECTED! @ > > > @@@ > > > The RSA host key for gq has changed, > > > and the key for the corresponding IP address 192.168.1.12 > > > is unknown. This could either mean that > > > DNS SPOOFING is happening or the IP address for the host > > > and its host key have changed at the same time. > > > > This I do not receive, perhaps because my router knows my MAC and > > gives me my static IP number. > > > > > @@@ > > > @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ > > > @@@ > > > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! > > > Someone could be eavesdropping on you right now (man-in-the-middle > > > attack)! > > > It is also possible that a host key has just been changed. > > > The fingerprint for the RSA key sent by the remote host is > > > 51:cf:52:87:6f:13:43:50:73:29:2c:b4:34:11:cd:5c. > > > Please contact your system administrator. > > > Add correct host key in /home/pec/.ssh/known_hosts to get rid of this > > > message. > > > Offending RSA key in /etc/ssh/ssh_known_hosts:3 > > > remove with: ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R gq > > > RSA host key for gq has changed and you have requested strict checking. > > > Host key verification failed. > > > > This one is very familiar, and is something I wanted to avoid when > > installing via ssh and network-console. > > > > You're presumably running ssh as pec. What I'm not sure about is why > > you're using /etc/ssh/ssh_known_hosts rather than > > /home/pec/.ssh/known_hosts , because you need root to maintain the > > former. > > I was running as pec or as root. I forget. Since doing that, I > realized that for many years I have been running with my own version > of /etc/ssh/ssh.config. Confronted with the evidence, I recall that > this was a place I found, through exhaustive search, to turn off the > hashing of known_host. I like to be able to identify lines in > known_host, because I think each line is a possible access path for a > hacker and the sysadmin, namely me, should be able to trace the > provenance of all such lines. In short hashing them opens a backdoor > more serious than the one it closes, IMHO. I now know that I can put > my edits in two places, /home/pec/.ssh/ssh_config and > /root/.ssh/ssh_config, and have the same effect. > > I can envision a different way, but I cannot envision one that does > not impact of how Debian wants to configure Jessie. So be it. > > I have not yet discovered a way to append new known host keys from newly > configured hosts into the .ssh/known_hosts files on older computers. > > I envision that, before I die, all traffic on the web will be > monitored by at least one spy organization of another. Maybe it is > already so. The job of personal sysadmin will be to allow monitoring > by agencies one knows and trusts, and disallows monitoring by > others. Frankly I trust the CIA more that the FBI, but both are more > trustworthy than Facebook ;-\ > > Debian has a much bigger problem than I have. > > But all this comment is just policy without effective implementation. > > > > > > I get this same complaint even after I remove the known_hosts file > > > entirely. How can the software retain the information that the offending > > > line is the third line? It must be doing more than the documentation > > > that I have says its doing, > > > > There are potentially two files. "the known_hosts file" implies you've > > deleted one of them. > > I think the removed file was the one associated with either pec, or root, > which ever was appropriate for a test. Since doing the tests, I have done > a complete re-install. With that removing the appropriate known_hosts file > gives me the old familiar option of accepting the risk of man-in-the-middle. > > > > > > This is a home lan. I use a hosts file to > > > inform the several computers of the IP addresses of all the computers in > > > the LAN. The file is identical on all computers and hasn't changed sine > > > etch. > > > > Same here. The router doesn't have a resolver, so I type hostnames and > > hosts gives me the static IP numbers. > > > > > In the past, I was given the option of typing the login password of the > > > computer
USB3 problem
My external USB3 hard drive worked for a while but it gave an error and dropped the drive and now it won't mount. I'm hoping rebooting will fix it but that is a bit drastic. [12171.656060] xhci_hcd :02:00.0: ERROR no room on ep ring [12171.656067] xhci_hcd :02:00.0: ERR: No room for command on command ring [12171.656074] hub 4-0:1.0: couldn't allocate port 1 usb_device I tried a USB2 port and it worked. [12478.736201] usb 5-1: new high-speed USB device number 3 using ehci_hcd That is not a good solution either because I have more USB3 ports. I'm using Jessie. Linux cheetah 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u2 x86_64 GNU/Linux -- 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/5532abdf.6050...@lockie.ca
Re: I need guidance about how to configure a newly installed Jessie
On 20150417_1408-0500, David Wright wrote: > Quoting Paul E Condon (pecon...@mesanetworks.net): > > > I have four desktop machines running Jessie. I try to keep them a;; > > upgraded on whenever new package versions are released. I thought it > > would be fast and simple. I was very wrong. This install behaves very > > differently in the following way: When I attempt to ssh into one of > > the computers that was not re-installed, I get a complaint that: > > > > @@@ > > @ WARNING: POSSIBLE DNS SPOOFING DETECTED! @ > > @@@ > > The RSA host key for gq has changed, > > and the key for the corresponding IP address 192.168.1.12 > > is unknown. This could either mean that > > DNS SPOOFING is happening or the IP address for the host > > and its host key have changed at the same time. > > This I do not receive, perhaps because my router knows my MAC and > gives me my static IP number. > > > @@@ > > @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ > > @@@ > > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! > > Someone could be eavesdropping on you right now (man-in-the-middle attack)! > > It is also possible that a host key has just been changed. > > The fingerprint for the RSA key sent by the remote host is > > 51:cf:52:87:6f:13:43:50:73:29:2c:b4:34:11:cd:5c. > > Please contact your system administrator. > > Add correct host key in /home/pec/.ssh/known_hosts to get rid of this > > message. > > Offending RSA key in /etc/ssh/ssh_known_hosts:3 > > remove with: ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R gq > > RSA host key for gq has changed and you have requested strict checking. > > Host key verification failed. > > This one is very familiar, and is something I wanted to avoid when > installing via ssh and network-console. > > You're presumably running ssh as pec. What I'm not sure about is why > you're using /etc/ssh/ssh_known_hosts rather than > /home/pec/.ssh/known_hosts , because you need root to maintain the > former. I was running as pec or as root. I forget. Since doing that, I realized that for many years I have been running with my own version of /etc/ssh/ssh.config. Confronted with the evidence, I recall that this was a place I found, through exhaustive search, to turn off the hashing of known_host. I like to be able to identify lines in known_host, because I think each line is a possible access path for a hacker and the sysadmin, namely me, should be able to trace the provenance of all such lines. In short hashing them opens a backdoor more serious than the one it closes, IMHO. I now know that I can put my edits in two places, /home/pec/.ssh/ssh_config and /root/.ssh/ssh_config, and have the same effect. I can envision a different way, but I cannot envision one that does not impact of how Debian wants to configure Jessie. So be it. I have not yet discovered a way to append new known host keys from newly configured hosts into the .ssh/known_hosts files on older computers. I envision that, before I die, all traffic on the web will be monitored by at least one spy organization of another. Maybe it is already so. The job of personal sysadmin will be to allow monitoring by agencies one knows and trusts, and disallows monitoring by others. Frankly I trust the CIA more that the FBI, but both are more trustworthy than Facebook ;-\ Debian has a much bigger problem than I have. But all this comment is just policy without effective implementation. > > > I get this same complaint even after I remove the known_hosts file > > entirely. How can the software retain the information that the offending > > line is the third line? It must be doing more than the documentation > > that I have says its doing, > > There are potentially two files. "the known_hosts file" implies you've > deleted one of them. I think the removed file was the one associated with either pec, or root, which ever was appropriate for a test. Since doing the tests, I have done a complete re-install. With that removing the appropriate known_hosts file gives me the old familiar option of accepting the risk of man-in-the-middle. > > > This is a home lan. I use a hosts file to > > inform the several computers of the IP addresses of all the computers in > > the LAN. The file is identical on all computers and hasn't changed sine > > etch. > > Same here. The router doesn't have a resolver, so I type hostnames and > hosts gives me the static IP numbers. > > > In the past, I was given the option of typing the login password of the > > computer that I want to log into, but not now. > > I'm not sure why you call it an "option". The default is to require > typing a password (of the user, not the computer), and we avoid that > by giving the remote host a "question" (our public key, placed it
Re: Change partition numbering
Kruppt writes: > On 2015-04-18, Rodolfo Medina wrote: >> >> After resizing a partition on my hard disk, >> partition numbering changed and now >> number 7 comes before and number 6 comes after: >> >> Model: ATA SAMSUNG MP0402H (scsi) >> Disk /dev/sda: 40.1GB >> Sector size (logical/physical): 512B/512B >> Partition Table: msdos >> Disk Flags: >> >> Number Start End SizeType File system Flags >> 1 32.3kB 8390MB 8390MB primary fat32 boot >> 2 8390MB 40.1GB 31.7GB extended lba >> 5 8390MB 9434MB 1045MB logical linux-swap(v1) >> 7 9434MB 26.2GB 16.8GB logical ext3 >> 6 26.2GB 40.1GB 13.8GB logical ext3 >> >> Is it possible, and how?, to correct that and change back 7 with 6? >> Googling around found no solution. >> >> Thanks for any help, >> >> Rodolfo >> >> > > Yes it is possible with GNU Linux fdisk in expert mode. > > Boot systemrescuecd (CD/USB) or GNU/Linux LiveCD > that has a recent version of GNU linux fdisk binary available. > run fdisk -l from root term or console > to determine proper drive dev location. > Then run for instance, if the drive shows to be > /dev/sda as determined via the output of fdisk -l. > Run fdisk as below: > fdisk /dev/sda > Then at the fdisk prompt type: > x > now you should be in expert mode and at the expert mode prompt. > type: > f > at the expert mode prompt. If all went right it will realign > partition order. When you are really sure you have done this > all properly, you would then type: > w > at the fdisk prompt and changes will be written to disk. I solved it the other way I described in early posts of the present thread, but the one you suggest sounds even better. Thanks, Rodolfo -- 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/87r3rhxqzr@gmail.com
Re: [solved] Re: Change partition numbering
Rodolfo Medina writes: > Rodolfo Medina writes: > >> After resizing a partition on my hard disk, partition numbering changed and >> now number 7 comes before and number 6 comes after: >> >> Model: ATA SAMSUNG MP0402H (scsi) >> Disk /dev/sda: 40.1GB >> Sector size (logical/physical): 512B/512B >> Partition Table: msdos >> Disk Flags: >> >> Number Start End SizeType File system Flags >> 1 32.3kB 8390MB 8390MB primary fat32 boot >> 2 8390MB 40.1GB 31.7GB extended lba >> 5 8390MB 9434MB 1045MB logical linux-swap(v1) >> 7 9434MB 26.2GB 16.8GB logical ext3 >> 6 26.2GB 40.1GB 13.8GB logical ext3 >> >> Is it possible, and how?, to correct that and change back 7 with 6? >> Googling around found no solution. > > I found this article: > > > http://unix.stackexchange.com/questions/18752/change-the-number-of-the-partition-from-sda1-to-sda2/18759#18759 > > According to it, I did: > > # sfdisk -d /dev/sda > myfile > > and edited sda.bkp my way. Then, > > # sfdisk --no-reread -f /dev/sda < myfile > > . Then I edited /etc/fstab properly and rebooted. But then I had to rescue > the system: from a Debian installation disk, in rescue mode, from the boot > partition, I did: > > # grub-install /dev/sda > > , then rebooted and now it seems ok. Maybe I had to give the last command > before rebooting the first time. ...and, finally, # update-grub Rodolfo -- 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/87egnhz674@gmail.com
Re: Change partition numbering
On 2015-04-18, Rodolfo Medina wrote: > Hi all. > > After resizing a partition on my hard disk, > partition numbering changed and now > number 7 comes before and number 6 comes after: > > Model: ATA SAMSUNG MP0402H (scsi) > Disk /dev/sda: 40.1GB > Sector size (logical/physical): 512B/512B > Partition Table: msdos > Disk Flags: > > Number Start End SizeType File system Flags > 1 32.3kB 8390MB 8390MB primary fat32 boot > 2 8390MB 40.1GB 31.7GB extended lba > 5 8390MB 9434MB 1045MB logical linux-swap(v1) > 7 9434MB 26.2GB 16.8GB logical ext3 > 6 26.2GB 40.1GB 13.8GB logical ext3 > > Is it possible, and how?, to correct that and change back 7 with 6? Googling > around found no solution. > > Thanks for any help, > > Rodolfo > > Yes it is possible with GNU Linux fdisk in expert mode. Boot systemrescuecd (CD/USB) or GNU/Linux LiveCD that has a recent version of GNU linux fdisk binary available. run fdisk -l from root term or console to determine proper drive dev location. Then run for instance, if the drive shows to be /dev/sda as determined via the output of fdisk -l. Run fdisk as below: fdisk /dev/sda Then at the fdisk prompt type: x now you should be in expert mode and at the expert mode prompt. type: f at the expert mode prompt. If all went right it will realign partition order. When you are really sure you have done this all properly, you would then type: w at the fdisk prompt and changes will be written to disk. -- 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/cpfhjef7dc...@mid.individual.net
Re: [solved] Re: Change partition numbering
On Sat, 18 Apr 2015 17:07:10 + Rodolfo Medina wrote: > Rodolfo Medina writes: > > > Hi all. > > > > After resizing a partition on my hard disk, partition numbering > > changed and now number 7 comes before and number 6 comes after: > > > > Model: ATA SAMSUNG MP0402H (scsi) > > Disk /dev/sda: 40.1GB > > Sector size (logical/physical): 512B/512B > > Partition Table: msdos > > Disk Flags: > > > > Number Start End SizeType File system Flags > > 1 32.3kB 8390MB 8390MB primary fat32 boot > > 2 8390MB 40.1GB 31.7GB extended lba > > 5 8390MB 9434MB 1045MB logical linux-swap(v1) > > 7 9434MB 26.2GB 16.8GB logical ext3 > > 6 26.2GB 40.1GB 13.8GB logical ext3 > > > > Is it possible, and how?, to correct that and change back 7 with > > 6? Googling around found no solution. > > I found this article: > > > http://unix.stackexchange.com/questions/18752/change-the-number-of-the-partition-from-sda1-to-sda2/18759#18759 > > According to it, I did: > > # sfdisk -d /dev/sda > myfile > > and edited sda.bkp my way. Then, > > # sfdisk --no-reread -f /dev/sda < myfile > > . Then I edited /etc/fstab properly and rebooted. But then I had to > rescue the system: from a Debian installation disk, in rescue mode, > from the boot partition, I did: > > # grub-install /dev/sda > > , then rebooted and now it seems ok. Maybe I had to give the last > command before rebooting the first time. > I've done this in the past with fdisk, carefully noting the partition start and end cylinders, then deleting the offending items from the partition table and adding them back in the right order. Write the table, edit /etc/fstab if necessary and reboot... What happens next depends on exactly what's on the partitions, and where the references to /dev/sda1, etc. are. I think there is only likely to be trouble where grub is involved, as it stores actual disc locations. Everything else is likely to refer to the mount points in fstab, and if mounting is by UUID, presumably nothing needs to be done even there. -- Joe -- 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/20150418182103.2dc6d...@jresid.jretrading.com
[solved] Re: Change partition numbering
Rodolfo Medina writes: > Hi all. > > After resizing a partition on my hard disk, partition numbering changed and > now number 7 comes before and number 6 comes after: > > Model: ATA SAMSUNG MP0402H (scsi) > Disk /dev/sda: 40.1GB > Sector size (logical/physical): 512B/512B > Partition Table: msdos > Disk Flags: > > Number Start End SizeType File system Flags > 1 32.3kB 8390MB 8390MB primary fat32 boot > 2 8390MB 40.1GB 31.7GB extended lba > 5 8390MB 9434MB 1045MB logical linux-swap(v1) > 7 9434MB 26.2GB 16.8GB logical ext3 > 6 26.2GB 40.1GB 13.8GB logical ext3 > > Is it possible, and how?, to correct that and change back 7 with 6? Googling > around found no solution. I found this article: http://unix.stackexchange.com/questions/18752/change-the-number-of-the-partition-from-sda1-to-sda2/18759#18759 According to it, I did: # sfdisk -d /dev/sda > myfile and edited sda.bkp my way. Then, # sfdisk --no-reread -f /dev/sda < myfile . Then I edited /etc/fstab properly and rebooted. But then I had to rescue the system: from a Debian installation disk, in rescue mode, from the boot partition, I did: # grub-install /dev/sda , then rebooted and now it seems ok. Maybe I had to give the last command before rebooting the first time. Rodolfo -- 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/874mod1i2p@gmail.com
Re: wheezy drive recognition?
On 2015-04-17, Gene Heskett wrote: > > Thats good to read Petter, thanks. I got burned a bit early on, running > dd-wrt on an x86 boxen from nothing but flash, It worked great, till the > flashes died, about 3 of the std sized 512 meggers in a month. I suppose much of what holds for minimizing disk read/writes for flash is more or less what holds for an SSD? (Is it just me or are these Arch wikies the best wikies in town?) https://wiki.archlinux.org/index.php/SSD#Tips_for_minimizing_disk_reads.2Fwrites > Cheers, Gene Heskett -- -- 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/slrnmj4v6u.3uj.cu...@einstein.electron.org
Change partition numbering
Hi all. After resizing a partition on my hard disk, partition numbering changed and now number 7 comes before and number 6 comes after: Model: ATA SAMSUNG MP0402H (scsi) Disk /dev/sda: 40.1GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End SizeType File system Flags 1 32.3kB 8390MB 8390MB primary fat32 boot 2 8390MB 40.1GB 31.7GB extended lba 5 8390MB 9434MB 1045MB logical linux-swap(v1) 7 9434MB 26.2GB 16.8GB logical ext3 6 26.2GB 40.1GB 13.8GB logical ext3 Is it possible, and how?, to correct that and change back 7 with 6? Googling around found no solution. Thanks for any help, Rodolfo -- 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/87h9sd1lkt@gmail.com
upnp no more working
hi everybody, I'm fighting since several days with a problem which appeared on my Jessie desktop about 2 weeks ago. Here are the facts - until end of March, no problem: PC files were seen on all my upnp clients I was using as upnp clients an Android app on my tablet and an ADSL box (french freebox) and mediatomb as server (but it used to work also with minidlna) - since 2 weeks, my PC is not seen on the clients. (nothing useful in the log file) I tried to use minidlna instead of mediatomb: same thing. - I installed minidlna on 2 Debian laptops, and they were seen immediatly, without any configuration change. - I have also a Windows 7 laptop, and it is also seen. I'm unable to find what kind of change on my PC can explain this sudden failure. I hoped to get some imformation with upnp-inspector, running on the desktop and on one laptop. It actually detected the local minidlna server (not the network ones!) but I could not find any useful information As there is no port redirection for the laptops, I don't see why it should be necessary for the desktop. Anyway, I tried some port redirections, without success. Has anybody an idea ? best regards, -- Pierre Frenkiel -- 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.1504181646100.24...@pfr2.frenkiel-hure.net
Re: I need guidance about how to configure a newly installed Jessie
On 20150417_1408-0500, David Wright wrote: > Quoting Paul E Condon (pecon...@mesanetworks.net): > > > I have four desktop machines running Jessie. I try to keep them a;; > > upgraded on whenever new package versions are released. I thought it > > would be fast and simple. I was very wrong. This install behaves very > > differently in the following way: When I attempt to ssh into one of > > the computers that was not re-installed, I get a complaint that: > > > > @@@ > > @ WARNING: POSSIBLE DNS SPOOFING DETECTED! @ > > @@@ > > The RSA host key for gq has changed, > > and the key for the corresponding IP address 192.168.1.12 > > is unknown. This could either mean that > > DNS SPOOFING is happening or the IP address for the host > > and its host key have changed at the same time. > > This I do not receive, perhaps because my router knows my MAC and > gives me my static IP number. > > > @@@ > > @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ > > @@@ > > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! > > Someone could be eavesdropping on you right now (man-in-the-middle attack)! > > It is also possible that a host key has just been changed. > > The fingerprint for the RSA key sent by the remote host is > > 51:cf:52:87:6f:13:43:50:73:29:2c:b4:34:11:cd:5c. > > Please contact your system administrator. > > Add correct host key in /home/pec/.ssh/known_hosts to get rid of this > > message. > > Offending RSA key in /etc/ssh/ssh_known_hosts:3 > > remove with: ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R gq > > RSA host key for gq has changed and you have requested strict checking. > > Host key verification failed. > > This one is very familiar, and is something I wanted to avoid when > installing via ssh and network-console. > > You're presumably running ssh as pec. What I'm not sure about is why > you're using /etc/ssh/ssh_known_hosts rather than > /home/pec/.ssh/known_hosts , because you need root to maintain the > former. > > > I get this same complaint even after I remove the known_hosts file > > entirely. How can the software retain the information that the offending > > line is the third line? It must be doing more than the documentation > > that I have says its doing, > > There are potentially two files. "the known_hosts file" implies you've > deleted one of them. > > > This is a home lan. I use a hosts file to > > inform the several computers of the IP addresses of all the computers in > > the LAN. The file is identical on all computers and hasn't changed sine > > etch. > > Same here. The router doesn't have a resolver, so I type hostnames and > hosts gives me the static IP numbers. > > > In the past, I was given the option of typing the login password of the > > computer that I want to log into, but not now. > > I'm not sure why you call it an "option". The default is to require > typing a password (of the user, not the computer), and we avoid that > by giving the remote host a "question" (our public key, placed it its > authorized_keys file) to which only we know the "answer" (our private > key, in our id_rsa file). > > > I don't understand what I should do with the RSA 'fingerprint' doesn't > > look at all like a legitimate line in a known_host file. How is it used? > > On the odd occasion that I keep the newly-installed host keys (usually > when I notice a new type of key in /etc/ssh/) I type, for example, > $ ssh-keygen -l -v -f /etc/ssh/ssh_host_ecdsa_key.pub > .../ssh-fingerprint > where ... is the place you keep your configuration records. > That's the remote hosts's fingerprint you check when you get the > warning. (I don't know how to get a host to send the randomart.) > > > Where is the source of this occult knowledge? > > man ssh-keygen is your friend. > > > Why does the author of the WARNING presume that there is a different > > person, other than the person reading the message who is the actual > > 'your system administration'? Has someone in NSA or CIA been assigned > > to monitor me, and this message breaches global security because I > > should not be allowed to know that I am being watch? > > Because if you were logging in to your unix account at work, say, > you'd pick up the phone and ask the operators what in h*ll's name are > they up to! In other words, ssh assumes the remote host really is > remote. You (local) get the warning, but the host that might have been > compromised (if it's not man-in-the-middle) is the remote one. > > Cheers, > David. Thanks, David I'm replying here to your post that was earlier than one that I have already replied to. It is 4:30am for me, and I woke up way before I usually do and couldn't go back to sleep. Now after about an hour of wakefulness, I'm beginning to need more sleep. I hav
Re: Wicd - no wireless networks found
On 2015-04-16 21:40, German wrote: Ok, I installed realtek firmware, running modrpobe rtl8723be returns no output, so I think my card is operational. But Wicd doesn't show any wireless networks. Where to go from here? Thank you In wicd-client, have you switched on WiFi and set Preferences->General Settings -> Wireless Interface to "wlan0"? -- August -- 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/mgt9h0$vkj$1...@speranza.aioe.org
Re: bugs found
On 2015-04-18 00:00, Richard Jasmin wrote: I have a bug in liberoffice writer that puts text on a new line instead of using the spacebar to do so. I don't understand what you mean. Do you want the spacebar to work like the return key? -- August -- 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/mgt97g$ura$1...@speranza.aioe.org
Re: Hibernate option in Gnome menu? (Jessie)
On 2015-04-17 20:23, deloptes wrote: > I had to downgrade upower package (look for a posting in this forum "No > suspend in XFCE without systemd") to get it work again. > It looks like upower dropped the freedesktop actions exposed to dbus and now > the system dows not know of such possibility - however old upower works > fine Is this really related? My relative does run systemd, and what is missing in the menu is hibernate (to disk), not suspend (to RAM). hibernate works fine after configuring the power button to this function, as suggested by Michael Biebl. Thanks anyway. -- 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/20150418091959.GA25508@fama
Re: Debian 7 and external monitors and graphics adaptors
On Sat, 18 Apr 2015 15:01:55 +0800 Bret Busby wrote: > On 18/04/2015, Liam O'Toole wrote: > > On 2015-04-17, David Wright wrote: > >> Quoting Bret Busby (bret.bu...@gmail.com): > >>> The computers upon which I run Debian 6, have only 16 GB of RAM, > >>> and, > >> > >> Lucky you. 2GB here. > >> > >>> expecially with Debian 6 not having adequate memory management (as > >>> previously mentioned, memory swapping does not work effectively), > >>> so, > >> > >> Eh? Squeeze ran quite happily for me with a Klamath Pentium II on > >> an Atlanta mobo with 384MB of RAM. What on earth *are* you running? > > > > I suspect the OP is confused about used vs free memory[1]. > > > > No. > > It has been made quite clear, in previous posts - it is to do with the > RAM being used up without memory swapping, occurring, when memory > usage shows at 90-95%, with no memory swapping. > > But, this thread has now descended into flaming, and so I simply give > up on it, and, on trying to get Debian 7 to work, via the mailing > list. Well, before you give up, have you tried the advice you have been given? There should be plenty there to get you started, and several resources for reading. It is hard to help when you do not respond about what you have tried and not, and what has/hasn't worked. I'm not interested in arguing with you, but have actually tried to help. If you are not interested in help, there is very little we can do for you. Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgpRmxZwPGsEk.pgp Description: OpenPGP digital signature
Re: Debian 7 and external monitors and graphics adaptors
On 18/04/2015, Liam O'Toole wrote: > On 2015-04-17, David Wright wrote: >> Quoting Bret Busby (bret.bu...@gmail.com): >>> The computers upon which I run Debian 6, have only 16 GB of RAM, and, >> >> Lucky you. 2GB here. >> >>> expecially with Debian 6 not having adequate memory management (as >>> previously mentioned, memory swapping does not work effectively), so, >> >> Eh? Squeeze ran quite happily for me with a Klamath Pentium II on an >> Atlanta mobo with 384MB of RAM. What on earth *are* you running? > > I suspect the OP is confused about used vs free memory[1]. > No. It has been made quite clear, in previous posts - it is to do with the RAM being used up without memory swapping, occurring, when memory usage shows at 90-95%, with no memory swapping. But, this thread has now descended into flaming, and so I simply give up on it, and, on trying to get Debian 7 to work, via the mailing list. -- 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/CACX6j8Nrbj=eSbqOTec66RROszcsm5TRVynx=o3-sv+577r...@mail.gmail.com
