Re: How to get Jessie to run at boot time -- Problem solved
On Wednesday 14 September 2016 16:34:31 Alan McConnell wrote:
> ----- Original Message -----
> From: "Felix Miata" <mrmazda@earthlink.net>
> To: debian-user@lists.debian.org
> Sent: Wednesday, September 14, 2016 1:44:14 AM
> Subject: Re: How to get Jessie to run at boot time -- Problem solved
>
> Alan McConnell composed on 2016-09-13 20:50 (UTC-0400):
> > when my home Debian install is, for some reason, not functional. I
> > apologize for Zimbra's inadequacies, failure to produce '>' as my home
> > mutt so nicely does.
> >
> > Just because one is unable to get whatever she is using to compose a
> > reply according to standards automatically doesn't excuse one who knows
> > better from conforming. Apologizing, particularly while continuing to not
> > conform, does not excuse. You are responsible for what you post, not your
> > posting agent.
>
> I just put in the '>'s in the four lines above by hand. I hope you
> are not going to ask me to continue to do so! Especially since I've
> already explained that Zimbra(which is set up to deal with E-mail) is such
> a cruddy mess.
It would be courteous. It makes an enormous difference.
...
>
> > But maybe someone
> > can tell me why the installer can't look at the partitions and determine
> > that there is some kind of OS already installed? Why does it have to
> > know about Windows 10 to behave sensibly? "Curious minds . . . "
>
> I have just checked and when I sent this it was indented eight
> spaces or so. As is this present paragraph. Do you(plural) see that it is
> indented? or does your(plural) mail reader simply delete the spaces? I
> ask, because I don't like to be chewed out when I'm doing my (present)
> level best to conform with expectations. Of course, it could be that
> Zimbra deletes the preliminary spaces before sending the mail out. I could
> tell you tales about how Gmail mucks with what one has written before it
> sends the mail.
>
>
> It does seem curious that the Debian installer would need knowledge of a
> particular Windows version in order to provide a boot menu selection for
> it, rather than simply having one that says "Windows", booting from
> whatever non-native/NTFS filesystem it happens to find containing anything
> resembling boot sector code.
> Yep. I have been back to my Jessie in the meantime, and run
> os-prober. I didn't attempt to copy down on a piece of paper what it wrote;
> trust me that it was unenlightening garbage.
>
> > Should you be game to try installing Jessie again, you might try a
> > network installation started via a Stretch installer.
>
> Jeez! I can't even run X11 on my present install(*) let alone get
> on line.
>
> (*) Does anyone here know how to create a .Xauthority file? That is one
> of the things the Jessie installer failed to provide me with.
Why not try re-downloading your install media and starting again? I take it
you did check the integrity of your install media? And did you edit your
BIOS before starting? Rhetorical question. I know that you don't believe in
answering questions or actually solving problems. You have an unsatisfactory
kludge and prefer to leave it so and just keep moaning. Or I would ask
EXACTLY what you have done and EXACTLY which model you have installed on.
Lots of people have got round the MS and Intel blocks and got Win10 and Jessie
dual booting. But is it a Skylake CPU? Because that would add an added
complication with the Jessie installer.
Either try to solve your problem or live with it and stop moaning.
(Wiktionary suggests that in that meaning that is acceptable on both sides of
the Atlantic).
Incidentally, I have just checked in my OED. Printed version, 3rd Edition,
published 1944, reprinted 1978. Whinge has been in use in its present
meaning since 1513 (they can cite a use in 1513), though it was only used
that long ago in the north and in Scotland. Whinger, the noun, cans only be
cited in 1540.
But:
https://www.google.co.uk/search?q=etymology+and+usage+of+whinge&oq=etymology+and+usage+of+whinge&aqs=chrome..69i57.9456j0j7&sourceid=chrome&ie=UTF-8
Note the first hit. Merriam Webster says that it has been in use since the
12th Century.
It hasn't been introduced here, it has died out there. It has been in
continuous use since the 16th Century or earlier.
But I don't suppose you listened to what people in Egham were saying in 1967
any more than you listen to us now.
Lisi
Reply to: