Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #171942 > unrolled thread

icedove: failed to connect server XXX@gmail.com

Back to article view | Back to linux.debian.user

Contents

  icedove: failed to connect server XXX@gmail.com mudongliang <mudongliangabcd@hotmail.com> - 2016-09-09 17:10 +0200
    How to get Jessie to run at boot time Alan McConnell <alan@his.com> - 2016-09-09 20:00 +0200
      Re: How to get Jessie to run at boot time Felix Miata <mrmazda@earthlink.net> - 2016-09-09 20:10 +0200
      Re: How to get Jessie to run at boot time "Andrew M.A. Cater" <amacater@galactic.demon.co.uk> - 2016-09-09 20:50 +0200
        Re: How to get Jessie to run at boot time Alan McConnell <alan@his.com> - 2016-09-10 17:50 +0200
          Re: How to get Jessie to run at boot time Brian <ad44@cityscape.co.uk> - 2016-09-10 18:40 +0200
            Re: How to get Jessie to run at boot time Alan McConnell <alan@his.com> - 2016-09-10 23:50 +0200
              Re: How to get Jessie to run at boot time "Andrew M.A. Cater" <amacater@galactic.demon.co.uk> - 2016-09-11 00:50 +0200
              Re: How to get Jessie to run at boot time Felix Miata <mrmazda@earthlink.net> - 2016-09-11 06:40 +0200
                Re: How to get Jessie to run at boot time -- Problem solved Alan McConnell <alan@his.com> - 2016-09-11 17:20 +0200
                  Re: How to get Jessie to run at boot time -- Problem solved Brian <ad44@cityscape.co.uk> - 2016-09-11 20:40 +0200
                    Re: How to get Jessie to run at boot time -- Problem solved Alan McConnell <alan@his.com> - 2016-09-11 21:20 +0200
                      Re: How to get Jessie to run at boot time -- Problem solved Brian <ad44@cityscape.co.uk> - 2016-09-11 22:00 +0200
                        Re: How to get Jessie to run at boot time -- Problem solved Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-12 13:20 +0200
    Re: icedove: failed to connect server XXX@gmail.com Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-13 09:30 +0200
    Re: icedove: failed to connect server XXX@gmail.com Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-13 10:00 +0200
      side-track of thread to the subject of mailservers was: Re: icedove: failed to connect server XXX@gmail.com Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-13 11:20 +0200
    Re: icedove: failed to connect server XXX@gmail.com Richard Owlett <rowlett@cloud85.net> - 2016-09-13 19:50 +0200

#171942 — icedove: failed to connect server XXX@gmail.com

Dear all,

         recently I suddenly failed to update my gmail account in 
icedove. When I tried to get messages from gmail account in icedove, it 
poped up one window : "Failled to connect server XXX@gmail.com". There 
is no error for my other email, for example, hotmail, outlook.

         How could I solve this problem?

-- 
My best regards to you.

      No System Is Safe!
      Dongliang Mu

[toc] | [next] | [standalone]

#171947 — How to get Jessie to run at boot time

This one should be _real_ easy!

Two days ago, my hard drive on my (now) discarded computer gave up the ghost.
After consideration, and advice from friends, I went out to Staples and bought
a Dell, with <sob> Windoze installed.  I hooked up everything and Windoze boots
OK, my sound works, etc.

This morning I installed Jessie, and this time the install went well.  I could
put in partitions for / , /usr/, /boot, /var, /tmp, and put in a big swap
partition.  When I rebooted at the end of the install, I got my Windows again, which
pleased me, since I'd left it in, giving it 50 gig of my terabyte drive.

But I don't know how to get my new Jessie to boot!  Back when I had one of my
first Linuxes and MS-DOS on my system, one got a prompt: "L or M" as soon as
one turned on the computer.  Things are now more subtle I'm sure, and they are
too subtle for me!

So can someone who also has a dual-bootable system(with Windows 10 and Jessie)
please tell me how you choose, at boot-time, which of your systems you wish to
boot?

TIA

Alan McConnell
 

[toc] | [prev] | [next] | [standalone]

#171950 — Re: How to get Jessie to run at boot time

Alan McConnell composed on 2016-09-09 13:58 (UTC-0400):

> Two days ago, my hard drive on my (now) discarded computer gave up the ghost.
> After consideration, and advice from friends, I went out to Staples and bought
> a Dell, with <sob> Windoze installed.  I hooked up everything and Windoze boots
> OK, my sound works, etc.

> This morning I installed Jessie, and this time the install went well.  I could
> put in partitions for / , /usr/, /boot, /var, /tmp, and put in a big swap
> partition.  When I rebooted at the end of the install, I got my Windows again, which
> pleased me, since I'd left it in, giving it 50 gig of my terabyte drive.

> But I don't know how to get my new Jessie to boot!  Back when I had one of my
> first Linuxes and MS-DOS on my system, one got a prompt: "L or M" as soon as
> one turned on the computer.  Things are now more subtle I'm sure, and they are
> too subtle for me!

> So can someone who also has a dual-bootable system(with Windows 10 and Jessie)
> please tell me how you choose, at boot-time, which of your systems you wish to
> boot?

Booting Linux from W10's own boot menu might be the simplest:
http://neosmart.net/EasyBCD/
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#171952 — Re: How to get Jessie to run at boot time

On Fri, Sep 09, 2016 at 01:58:03PM -0400, Alan McConnell wrote:
> This one should be _real_ easy!
> 
> Two days ago, my hard drive on my (now) discarded computer gave up the ghost.
> After consideration, and advice from friends, I went out to Staples and bought
> a Dell, with <sob> Windoze installed.  I hooked up everything and Windoze boots
> OK, my sound works, etc.
> 
> This morning I installed Jessie, and this time the install went well.  I could
> put in partitions for / , /usr/, /boot, /var, /tmp, and put in a big swap
> partition.  When I rebooted at the end of the install, I got my Windows again, which
> pleased me, since I'd left it in, giving it 50 gig of my terabyte drive.
> 
> But I don't know how to get my new Jessie to boot!  Back when I had one of my
> first Linuxes and MS-DOS on my system, one got a prompt: "L or M" as soon as
> one turned on the computer.  Things are now more subtle I'm sure, and they are
> too subtle for me!
> 
> So can someone who also has a dual-bootable system(with Windows 10 and Jessie)
> please tell me how you choose, at boot-time, which of your systems you wish to
> boot?
> 
> TIA
> 
> Alan McConnell
> 

Boot your install medium - enter rescue mode - reinstall grub?

HTH,

Andy C 

[toc] | [prev] | [next] | [standalone]

#171989 — Re: How to get Jessie to run at boot time

(Please excuse my cc to Mr Cater)

----- Original Message -----
From: "Andrew M.A. Cater" <amacater@galactic.demon.co.uk>
To: debian-user@lists.debian.org
Sent: Friday, September 9, 2016 2:42:28 PM
Subject: Re: How to get Jessie to run at boot time

On Fri, Sep 09, 2016 at 01:58:03PM -0400, Alan McConnell wrote:
> This one should be _real_ easy!
        .  .  .  .  .

> But I don't know how to get my new Jessie to boot!  Back when I had one of my
> first Linuxes and MS-DOS on my system, one got a prompt: "L or M" as soon as
> one turned on the computer.  Things are now more subtle I'm sure, and they are
> too subtle for me!
> 
> So can someone who also has a dual-bootable system(with Windows 10 and Jessie)
> please tell me how you choose, at boot-time, which of your systems you wish to
> boot?

> Boot your install medium - enter rescue mode - reinstall grub?
         I tried Rescue Mode.  Maybe I'm not doing it right, but I got thrown into
         "Chose language", "Choose Keyboard" . . . just as if I were doing a fresh
         install.  ? ? ?

But I don't need that.  I played with the BIOS a little, and now I boot automatically
into my new Jessie.  I am busy installing stuff and getting stuff off of backups, etc . . 
But I'd still like to be asked, right after I turn the machine on, which OS I'd like
to boot.

My present /boot/grub/ directory contains minimal stuff:
     fonts/ , grub.cfg , grubenv , i386-pc/ , locale/ , unicode.pf2

But when I run    apt-cache search grub  , it shows me a lot more stuff that I
could install.  So I ask again, this time from a position of being able to install
and configure  grub , how do I do it, and make it give me a good clean choice of
OS when I turn my machine on in the morning?

I hope that this is the place to ask; or is there an E-list full of grub experts?

TIA,

Alan McConnell

[toc] | [prev] | [next] | [standalone]

#171992 — Re: How to get Jessie to run at boot time

On Sat 10 Sep 2016 at 11:40:28 -0400, Alan McConnell wrote:

> > Boot your install medium - enter rescue mode - reinstall grub?
>          I tried Rescue Mode.  Maybe I'm not doing it right, but I got thrown into
>          "Chose language", "Choose Keyboard" . . . just as if I were doing a fresh
>          install.  ? ? ?

You noticed what was in the top left-hand corner of the screen?

> But I don't need that.  I played with the BIOS a little, and now I boot automatically

Yes, you need it - definitely. Persevere. Keep going and eventually
you'll get to a page where you can reinstall GRUB.

> into my new Jessie.  I am busy installing stuff and getting stuff off of backups, etc . . 
> But I'd still like to be asked, right after I turn the machine on, which OS I'd like
> to boot.
> 
> My present /boot/grub/ directory contains minimal stuff:
>      fonts/ , grub.cfg , grubenv , i386-pc/ , locale/ , unicode.pf2
> 
> But when I run    apt-cache search grub  , it shows me a lot more stuff that I
> could install.  So I ask again, this time from a position of being able to install
> and configure  grub , how do I do it, and make it give me a good clean choice of
> OS when I turn my machine on in the morning?
> 
> I hope that this is the place to ask; or is there an E-list full of grub experts?

They'll tell you to reinstall GRUB and run the command 'update-grub'
from rescue mode. You can ask about this if you are stuck when you get
rescue mode going.

[toc] | [prev] | [next] | [standalone]

#172016 — Re: How to get Jessie to run at boot time

----- Original Message -----
From: "Brian" <ad44@cityscape.co.uk>
To: debian-user@lists.debian.org
Sent: Saturday, September 10, 2016 12:38:11 PM
Subject: Re: How to get Jessie to run at boot time
     .   .   .   .

> could install.  So I ask again, this time from a position of being able to install
> and configure  grub , how do I do it, and make it give me a good clean choice of
> OS when I turn my machine on in the morning?
> 
> I hope that this is the place to ask; or is there an E-list full of grub experts?

> They'll tell you to reinstall GRUB and run the command 'update-grub'
> from rescue mode. You can ask about this if you are stuck when you get
> rescue mode going.
       Good grief.  I just wrote that I am now logged in to a working jessie.
       So I can run any kind of apt-get, aptitude, etc.  

       So I repeat:  apt-cache search grub gives me lots of grub files to install.
       Do I want to install a different grub?  I remember that previously I had lots
       of files in /boot/grub/ .  Now I have just a few, which I gave to you and the
       List in my previous post.

       Again:  are there people with a working dual boot system?  I'd like a response
       from one of them(if they exist here) letting me know how it works, and also:
       what is the content of their /boot/grub/ directory.

Again: TIA.

Alan McConnell

[toc] | [prev] | [next] | [standalone]

#172019 — Re: How to get Jessie to run at boot time

On Sat, Sep 10, 2016 at 05:45:51PM -0400, Alan McConnell wrote:
> 
> 
> ----- Original Message -----
> From: "Brian" <ad44@cityscape.co.uk>
> To: debian-user@lists.debian.org
> Sent: Saturday, September 10, 2016 12:38:11 PM
> Subject: Re: How to get Jessie to run at boot time
>      .   .   .   .
> 
> > could install.  So I ask again, this time from a position of being able to install
> > and configure  grub , how do I do it, and make it give me a good clean choice of
> > OS when I turn my machine on in the morning?
> > 
> > I hope that this is the place to ask; or is there an E-list full of grub experts?
> 
> > They'll tell you to reinstall GRUB and run the command 'update-grub'
> > from rescue mode. You can ask about this if you are stuck when you get
> > rescue mode going.
>        Good grief.  I just wrote that I am now logged in to a working jessie.
>        So I can run any kind of apt-get, aptitude, etc.  
> 
>        So I repeat:  apt-cache search grub gives me lots of grub files to install.
>        Do I want to install a different grub?  I remember that previously I had lots
>        of files in /boot/grub/ .  Now I have just a few, which I gave to you and the
>        List in my previous post.
> 
>        Again:  are there people with a working dual boot system?  I'd like a response
>        from one of them(if they exist here) letting me know how it works, and also:
>        what is the content of their /boot/grub/ directory.
> 
> Again: TIA.
> 
> Alan McConnell

If you install Debian, then install Windows - you normally overwrite the GRUB entries and MBR.

If you isntall the other way round, you normally find that Debian will find the Windows partition and install GRUB correctly.

In case of only having Windows come up: boot from media, run rescue - which looks like an insstall but isn't quite - work through
to the end and you have an option to reinstall GRUB.

If you're already _in_ a working Jessie - run os-prober and update-grub as root

This is by way of becoming an FAQ - and is in the installation instructions / release notes as Chapter 8, I think.

apt-get install debian-handbook and read up on this?

All the very best,

Andy C

[toc] | [prev] | [next] | [standalone]

#172028 — Re: How to get Jessie to run at boot time

Alan McConnell composed on 2016-09-10 17:45 (UTC-0400):

> Good grief.  I just wrote that I am now logged in to a working jessie.
> So I can run any kind of apt-get, aptitude, etc.

> So I repeat:  apt-cache search grub gives me lots of grub files to install.
> Do I want to install a different grub?

Possibly, though not likely. What does 'dpkg -l | grep grub' show now?

> I remember that previously I had lots
> of files in /boot/grub/ .  Now I have just a few, which I gave to you and the
> List in my previous post.

You had more files when you were using Grub. Now you surely have Grub2, which 
scatters files across more locations instead of keeping most in /boot/grub.

> Again:  are there people with a working dual boot system?

I have no "dual boot" systems, but I do have *dozens* of multiboot systems 
representing hundreds of installations of various distros that include 
Wheezy, Jessie and Stretch. Grub is installed to the MBR of none of them, 
regardless whether or not Windows or DOS are among their installations.

> I'd like a response
> from one of them(if they exist here) letting me know how it works,

Several different ways work here. This machine:
1-Generic code is installed to MBRs
2-/dev/sda1 and /dev/sdb1 are marked active/bootable in MBR table
3-Grub actually used for booting is installed to /dev/sda1 and /dev/sdb1
4-After installation or kernel update, I copy kernel and initrd to /dev/sd#1
5-Grub loads kernel/initrd from /dev/sd#1
6-/dev/sd#1/boot/grub are maintained entirely by myself
7-/ partitions are on /dev/md1, /dev/md2, /dev/md3 & /dev/md4 (md4 running)

The method is fundamentally equivalent to how DOS, OS/2 and Windows boot: 
standard MBR code finds the active/bootable partition, then loads and 
transfers control to the boot code found there.

A very different, and simpler, example can be found on:
http://fm.no-ip.com/PC/install-doz-after.html

> and also:
> what is the content of their /boot/grub/ directory.

 From the one from which I write this (but note it's not the location from 
which machine normally "boots", only the one the distro installation installs 
and maintains):
# ll /boot/grub
total 532
drwxr-xr-x 2 root root   4096 Aug  2 02:58 .
drwxr-xr-x 4 root root   4096 Aug  2 02:57 ..
-rw------- 1 root root     10 Oct  3  2011 default
-rw------- 1 root root    108 Jan 31  2015 device.map
-rw------- 1 root root     30 Oct  3  2011 device.map-ab
-rw------- 1 root root    108 Jan 31  2015 device.map-both
-rw------- 1 root root     29 Oct  3  2011 device.map.old
-rw-r--r-- 1 root root  13280 Sep 11  2015 e2fs_stage1_5
-rw-r--r-- 1 root root  11213 Sep 11  2015 fat_stage1_5
-rw-r--r-- 1 root root   9920 Sep 11  2015 ffs_stage1_5
-rw-r--r-- 1 root root   9984 Sep 11  2015 iso9660_stage1_5
-rw-r--r-- 1 root root  11968 Sep 11  2015 jfs_stage1_5
-rw------- 1 root root    681 Feb  7  2016 menu.lst
-rw------- 1 root root    681 Feb  7  2016 menu.lst.0
-rw------- 1 root root   1360 Feb  7  2016 menu.lst.02
-rw------- 1 root root   1614 Feb  7  2016 menu.lst.03
-rw------- 1 root root   1620 May 30 21:39 menu.lst.04
-rw------- 1 root root   1620 Jul  2 01:51 menu.lst.05
-rw------- 1 root root   1620 Aug  2 02:54 menu.lst.06
-rw------- 1 root root   1363 Aug  2 02:54 menu.lst.old
-rw-r--r-- 1 root root  10048 Sep 11  2015 minix_stage1_5
-rw-r--r-- 1 root root  13696 Sep 11  2015 reiserfs_stage1_5
-rw-r--r-- 1 root root    512 Sep 11  2015 stage1
-rw-r--r-- 1 root root 137520 Dec 26  2015 stage2
-rw-r--r-- 1 root root  10324 Sep 11  2015 ufs2_stage1_5
-rw-r--r-- 1 root root   9472 Sep 11  2015 vstafs_stage1_5
-rw-r--r-- 1 root root  13446 Sep 11  2015 xfs_stage1_5
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#172049 — Re: How to get Jessie to run at boot time -- Problem solved

----- Original Message -----
From: "Felix Miata" <mrmazda@earthlink.net>
To: debian-user@lists.debian.org
Sent: Saturday, September 10, 2016 11:33:46 PM
Subject: Re: How to get Jessie to run at boot time

Alan McConnell composed on 2016-09-10 17:45 (UTC-0400):

> Good grief.  I just wrote that I am now logged in to a working jessie.
> So I can run any kind of apt-get, aptitude, etc.

> So I repeat:  apt-cache search grub gives me lots of grub files to install.
> Do I want to install a different grub?

> Possibly, though not likely. What does 'dpkg -l | grep grub' show now?
        I have grub 2.0.2

        What works for me now is the following:  If I do nothing, I boot directly
        into Jessie.  However, if I wish to boot into Windoze, which is what I'll do
        a lot for now, since I haven't even got an X11 system running on my Jessie,
        I press and hold F12, to get into the choose boot method pre-OS screen.
        There I choose Windows boot manager(recall that this is a new machine, a
        generic Dell, so OF COURSE it had Windows installed.  And after choosing
        this, of course what I get is a nice boot into Windoze.

Before leaving this topic, I have a remark:  I have been telling interested and
non-interested people for years that one doesn't have to completely abandon one's
long-held Windoze habit, one can install Linux as a second OS and play with both
until Linux has "sold itself".  I shudder to think of someone taking my advice,
following all the instructions, and winding up with a system where only Linux
is available.  Imagine being taken out of one's English-speaking world and dumped
into a village in Uzbekistan!

Fortunately I live in a facility where there is a "computer lab" to which I have
access.  And I was able to go there, use their Chrome browser to get to my his.com
E-mail facility, whine to you folks, and blunder my way through to a solution.
Other people won't have that good fortune.

Addendum:  during my Jessie install, the install program commented at one point:
"There doesn't seem to be any other OS on your system".  Jeez!!  I hope some
maintainer reads this complaint and Debian  works hard to make sure that the
operation of installing a second OS(Linux) on a Windoze box is as easy and
error-proof as it is possible to make it.

Best wishes, and thanks to all the kind responders who helped me.

Alan McConnell

[toc] | [prev] | [next] | [standalone]

#172058 — Re: How to get Jessie to run at boot time -- Problem solved

On Sun 11 Sep 2016 at 11:13:45 -0400, Alan McConnell wrote:

> Addendum:  during my Jessie install, the install program commented at one point:
> "There doesn't seem to be any other OS on your system".  Jeez!!  I hope some
> maintainer reads this complaint and Debian  works hard to make sure that the

What is the exact name and version of this OS which is not found?

> operation of installing a second OS(Linux) on a Windoze box is as easy and
> error-proof as it is possible to make it.

1. As a user do

     dpkg -l | grep grub

   Please post the output of this command.

2. Suppose there are four packages listed. As root do

     apt-get --reinstall install <package_name>

   for each package

   <package_name> is in the second column of the 'dpkg -l' output.

   So, for example

     apt-get --reinstall install grub-common
     apt-get --reinstall install grub-pc
     apt-get --reinstall install grub-pc-bin
     apt-get --reinstall install grub2-common

   is what I would do on my machine. For the grub-pc reinstall please post
   the lines which begin "Found ....." in the output.

3. As root run the command

     os-prober

   and post its output.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#172060 — Re: How to get Jessie to run at boot time -- Problem solved

----- Original Message -----
From: "Brian" <ad44@cityscape.co.uk>
To: debian-user@lists.debian.org
Sent: Sunday, September 11, 2016 1:32:54 PM
Subject: Re: How to get Jessie to run at boot time -- Problem solved

On Sun 11 Sep 2016 at 11:13:45 -0400, Alan McConnell wrote:

> Addendum:  during my Jessie install, the install program commented at one point:
> "There doesn't seem to be any other OS on your system".  Jeez!!  I hope some
> maintainer reads this complaint and Debian  works hard to make sure that the

What is the exact name and version of this OS which is not found?
       <LOL>  Windows 10.  If there is a more exact name, I don't know it.

> operation of installing a second OS(Linux) on a Windoze box is as easy and
> error-proof as it is possible to make it.

1. As a user do

     dpkg -l | grep grub

   Please post the output of this command.

2. Suppose there are four packages listed. As root do

     apt-get --reinstall install <package_name>

   for each package

   <package_name> is in the second column of the 'dpkg -l' output.

   So, for example

     apt-get --reinstall install grub-common
     apt-get --reinstall install grub-pc
     apt-get --reinstall install grub-pc-bin
     apt-get --reinstall install grub2-common

   is what I would do on my machine. For the grub-pc reinstall please post
   the lines which begin "Found ....." in the output.

3. As root run the command

     os-prober

   and post its output.

         Why?  why all this?  What good will it do? to anyone?  To do this I'd have
         to get out of this URL(mail.his.com), shut down my Windoze, reboot to Jessie,
         copy the output you are requesting to a piece of paper, and then get back here.(*)

         May I ask: are you the Debian installation maintainer?  if you are, I'd be
         happy to work with you.

(*)  Many years ago, when I ran a dual boot machine of Linux and MS-DOS, I used to be
able to mount the MS-DOS partition from my Linux system, and copy file to and from it.
I'm going to try that, when next I (re)boot into Jessie.

Best wishes,

Alan

[toc] | [prev] | [next] | [standalone]

#172061 — Re: How to get Jessie to run at boot time -- Problem solved

On Sun 11 Sep 2016 at 15:17:00 -0400, Alan McConnell wrote:

> On Sun 11 Sep 2016 at 11:13:45 -0400, Alan McConnell wrote:
> 
> > Addendum:  during my Jessie install, the install program commented at one point:
> > "There doesn't seem to be any other OS on your system".  Jeez!!  I hope some
> > maintainer reads this complaint and Debian  works hard to make sure that the
> 
> What is the exact name and version of this OS which is not found?
>        <LOL>  Windows 10.  If there is a more exact name, I don't know it.

Deconstruction of this statement follows:

 I do not know. I am unable to extract information from any OS. But I am
 really good at moaning about them. You will get no help from me, don't
 bother me.

> > operation of installing a second OS(Linux) on a Windoze box is as easy and
> > error-proof as it is possible to make it.
> 
> 1. As a user do
> 
>      dpkg -l | grep grub
> 
>    Please post the output of this command.
> 
> 2. Suppose there are four packages listed. As root do
> 
>      apt-get --reinstall install <package_name>
> 
>    for each package
> 
>    <package_name> is in the second column of the 'dpkg -l' output.
> 
>    So, for example
> 
>      apt-get --reinstall install grub-common
>      apt-get --reinstall install grub-pc
>      apt-get --reinstall install grub-pc-bin
>      apt-get --reinstall install grub2-common
> 
>    is what I would do on my machine. For the grub-pc reinstall please post
>    the lines which begin "Found ....." in the output.
> 
> 3. As root run the command
> 
>      os-prober
> 
>    and post its output.
> 
>          Why?  why all this?  What good will it do? to anyone?  To do this I'd have
>          to get out of this URL(mail.his.com), shut down my Windoze, reboot to Jessie,
>          copy the output you are requesting to a piece of paper, and then get back here.(*)

Deconstruction of this statement follows:

  You are asking questions. Questions are awkward - you have to give
  answers; I do not want to participate in giving answers. Just take
  some notice of me and give me what I want without all this palaver.

>          May I ask: are you the Debian installation maintainer?  if you are, I'd be
>          happy to work with you.

Having chosen to post to debian-user you cannot even work with the
process here. What chance would there be of a working relationship if
you thought you were talking to the Debian Leader.

> (*)  Many years ago, when I ran a dual boot machine of Linux and MS-DOS, I used to be
> able to mount the MS-DOS partition from my Linux system, and copy file to and from it.
> I'm going to try that, when next I (re)boot into Jessie.

Deconstruction of this statement follows:

  Redirection. I've managed to avoid answering anything but I can still
  go down fighting and introduce something irrelevant. Do I have to stew
  in my own juice?

[toc] | [prev] | [next] | [standalone]

#172082 — Re: How to get Jessie to run at boot time -- Problem solved

On Sunday 11 September 2016 20:51:50 Brian wrote:
> On Sun 11 Sep 2016 at 15:17:00 -0400, Alan McConnell wrote:
> > On Sun 11 Sep 2016 at 11:13:45 -0400, Alan McConnell wrote:
> > > Addendum:  during my Jessie install, the install program commented at
> > > one point: "There doesn't seem to be any other OS on your system". 
> > > Jeez!!  I hope some maintainer reads this complaint and Debian  works
> > > hard to make sure that the
> >
> > What is the exact name and version of this OS which is not found?
> >        <LOL>  Windows 10.  If there is a more exact name, I don't know
> > it.
>
> Deconstruction of this statement follows:
>
>  I do not know. I am unable to extract information from any OS. But I am
>  really good at moaning about them. You will get no help from me, don't
>  bother me.
>
> > > operation of installing a second OS(Linux) on a Windoze box is as easy
> > > and error-proof as it is possible to make it.
> >
> > 1. As a user do
> >
> >      dpkg -l | grep grub
> >
> >    Please post the output of this command.
> >
> > 2. Suppose there are four packages listed. As root do
> >
> >      apt-get --reinstall install <package_name>
> >
> >    for each package
> >
> >    <package_name> is in the second column of the 'dpkg -l' output.
> >
> >    So, for example
> >
> >      apt-get --reinstall install grub-common
> >      apt-get --reinstall install grub-pc
> >      apt-get --reinstall install grub-pc-bin
> >      apt-get --reinstall install grub2-common
> >
> >    is what I would do on my machine. For the grub-pc reinstall please
> > post the lines which begin "Found ....." in the output.
> >
> > 3. As root run the command
> >
> >      os-prober
> >
> >    and post its output.
> >
> >          Why?  why all this?  What good will it do? to anyone?  To do
> > this I'd have to get out of this URL(mail.his.com), shut down my Windoze,
> > reboot to Jessie, copy the output you are requesting to a piece of paper,
> > and then get back here.(*)
>
> Deconstruction of this statement follows:
>
>   You are asking questions. Questions are awkward - you have to give
>   answers; I do not want to participate in giving answers. Just take
>   some notice of me and give me what I want without all this palaver.
>
> >          May I ask: are you the Debian installation maintainer?  if you
> > are, I'd be happy to work with you.
>
> Having chosen to post to debian-user you cannot even work with the
> process here. What chance would there be of a working relationship if
> you thought you were talking to the Debian Leader.
>
> > (*)  Many years ago, when I ran a dual boot machine of Linux and MS-DOS,
> > I used to be able to mount the MS-DOS partition from my Linux system, and
> > copy file to and from it. I'm going to try that, when next I (re)boot
> > into Jessie.
>
> Deconstruction of this statement follows:
>
>   Redirection. I've managed to avoid answering anything but I can still
>   go down fighting and introduce something irrelevant. Do I have to stew
>   in my own juice?

And to achieve all this rudeness he hijacked mudongliang's thread and as a 
result mudongliang has still had no answers.  :-(  But I'm forgetting.  
Nothing and no-one else matters compared with Alan. :-(

I'm off to try and answer mudongliang, but I fear that I can't because I don't 
think I know the answer.  But at least it should revive his thread.

Lisi

[toc] | [prev] | [next] | [standalone]

#172108

On Friday 09 September 2016 16:02:42 mudongliang wrote:
> Dear all,
>
>          recently I suddenly failed to update my gmail account in
> icedove. When I tried to get messages from gmail account in icedove, it
> poped up one window : "Failled to connect server XXX@gmail.com". There
> is no error for my other email, for example, hotmail, outlook.
>
>          How could I solve this problem?

Have you seen this reply?
https://lists.debian.org/msgid-search/20160912190300.2f74664d@playground

Lisi

[toc] | [prev] | [next] | [standalone]

#172109

I am still trying to figure out why my original reply got so thoroughly 
blocked by, I think, Debian's spam filters.  So here is the original reply, 
with the acronyms replaced by wikipedia links.  (For coherent reading, 
replace the wikipedia links with teh relevant acronyms)

On Friday 09 September 2016 16:02:42 mudongliang wrote:
> Dear all,
>
>          recently I suddenly failed to update my gmail account in
> icedove. When I tried to get messages from gmail account in icedove, it
> poped up one window : "Failled to connect server XXX@gmail.com". There
> is no error for my other email, for example, hotmail, outlook.
>
>          How could I solve this problem?

Look at the 
https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol
 or 
https://en.wikipedia.org/wiki/Internet_Message_Access_Protocol
 server settings.  It looks as though something has 
gone wrong with the gmail settings.  It would help if you were to say which 
gmail server you are having problems with, and what settings you are using.

Lisi

[toc] | [prev] | [next] | [standalone]

#172111 — side-track of thread to the subject of mailservers was: Re: icedove: failed to connect server XXX@gmail.com

On Tuesday 13 September 2016 08:56:47 Lisi Reisz wrote:
> I am still trying to figure out why my original reply got so thoroughly
> blocked by, I think, Debian's spam filters.  So here is the original reply,
> with the acronyms replaced by wikipedia links.  (For coherent reading,
> replace the wikipedia links with teh relevant acronyms)
>
> On Friday 09 September 2016 16:02:42 mudongliang wrote:
> > Dear all,
> >
> >          recently I suddenly failed to update my gmail account in
> > icedove. When I tried to get messages from gmail account in icedove, it
> > poped up one window : "Failled to connect server XXX@gmail.com". There
> > is no error for my other email, for example, hotmail, outlook.
> >
> >          How could I solve this problem?
>
> Look at the
> https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol
>  or
> https://en.wikipedia.org/wiki/Internet_Message_Access_Protocol
>  server settings.  It looks as though something has
> gone wrong with the gmail settings.  It would help if you were to say which
> gmail server you are having problems with, and what settings you are using.
>
> Lisi

So Debian's spamcheckers were failing, consistently, over a period of time, 
the acronyms for two types of mail "sending" servers.  That strikes me as 
seriously weird.  (I daren't name the servers!!)

Lisi

[toc] | [prev] | [next] | [standalone]

#172133

On 9/9/2016 10:02 AM, mudongliang wrote:
> Dear all,
>
>          recently I suddenly failed to update my gmail account in
> icedove. When I tried to get messages from gmail account in
> icedove, it poped up one window : "Failled to connect server
> XXX@gmail.com". There is no error for my other email, for
> example, hotmail, outlook.
>
>          How could I solve this problem?
>

Reposting Neal's reply to remedy broken thread.

On 9/12/2016 6:03 PM, Neal P. Murphy wrote:
> On Mon, 12 Sep 2016 23:38:56 +0100
> Lisi Reisz <lisi.reisz@gmail.com> wrote:
>
>> PS I have been trying to help mudongliang, unsuccessfully. But thereby hangs
>> another thread. Please someone else, his question has still not been
>> answered. Are all attempts to answer it being spam-checked out of
>> existence??
>>
>
> [I trust this will appear in the desired thread; I changed the subject back....]
>
> A few things I can think of (which generally reflect your suggestions):
> - username changed in settings or at gmail
> - password changed in settings or at gmail
> - port changed in settings or at gmail (between encrypted and non-encrypted, for example)
> - DNS problems
> - SSL versus startTLS
> - change between IMAP and POP3
> - firewall blockage (but not *too* likely, since other servers can be accessed)
> - encryption schemes that are no longer valid (like SSL2 or SSL3 but, again, not *too* likely*)
>
> N
>
>
> P.S. Related to another thread (about email programs), another shortcoming of Claws Mail is that there's no way to see/edit *all* a reply's headers; otherwise, I would've adjusted this message's Message-id header to match that of the O.P.'s message and make this reply appear in the right place in the thread. I don't have the original message to reply to.
>
>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web