Re: lynx - not all sites readable
Am Mittwoch, 14. September 2016, 20:06:40 CEST schrieb Karen Lewellen: Hi Karen, thanks for your hint! This is working. Deactivating sending the agent, let me read the site. However, still there is the problem, that I cannot step to submenus on the site. If one wants to see, what I mean: go to www.nvidia.com, then try to go to the "Drivers" link. The colour here is purple of the link, and cannot be reached. Hans > Hi, > Forgive this not being in context. > If you are using the most current development edition of Lynx from April > 25 of this year and you are reaching sites that present a message like > the following, > 403 forbidden, > I suggest you try the following. > open the options menu and arrow down to the item that says >"send user agent," with an exclamation mark because the change cannot > be saved permanently. > unchecked this option do the temporary save options and you will get > confirmation that the value has been accepted. > if you are still on the site in question, things may improve right > away. if not try the site again, with positive results..or such is > my experience almost all of the time when I reach the forbidden message. > I hope this is helpful, > Karen >
google-chrome-stable vs. chromium
I haven't posted a question from the far left end of the bell-shaped curve in some time, so please bear with me! In respect of my Subject: line, above, I have the first of those two packages installed. How does it differ from the second, which I do not have installed? Thank youse, -- IMPORTANT: This email is intended for the use of the individual addressee(s) named above and may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational metaphysical beliefs.
Re: Debian Jessie : regular console instead of a hi-res one!
On Wed 14 Sep 2016 at 11:09:47 (-0400), Ric Moore wrote: > On 09/13/2016 02:36 PM, David Wright wrote: > > >When I want to change resolution, which keys should I press to do that? > > Back in the day, when xorg.conf roamed free, you could have multiple > screen resolutions noted within it and a ctrl-alt-+ would switch > resolutions on the fly. That worked on CRT monitors, not sure how > that would work on LEDs. Ric I remember it well. I also remember that you hoped the CRT had remembered the X/Y height/width/position settings for each resolution's mode, or you'd have to do a lot of fiddling with each change. Also the "clunk" presumably from the Line Output Transformer as it coped with the sudden change in demand. But none of this applied to the linux console of course. Cheers, David.
Re: Debian Jessie : regular console instead of a hi-res one!
On Wed 14 Sep 2016 at 05:43:24 (-0400), Felix Miata wrote: > David Wright composed on 2016-09-13 13:36 (UTC-0500): > > Rather curious to see a regular participant here with a .co.uk > mailing address apparently in a university environment in a UTC-0500 > time zone. Curiosity makes it for me a recurring distraction, > wondering just what part of the world this might be, somewhere north > of Wisconsin, Minnesota or North Dakota? :-p Three states south of ND...Kansas. > >On Thu 08 Sep 2016 at 12:53:49 (-0400), Felix Miata wrote: > >>David Wright composed on 2016-09-08 09:08 (UTC-0500): > > >>>You can play with framebuffers and kernel drivers all you like. > >>>What you cannot do is alter the layout of pixels on the screen. > > >>Absolutely true. > > >>>If you don't use a resolution that matches those pixels exactly, > >>>nothing you do can compensate. > > >>False. The difference from one resolution to the next is easily lost > >>if the screen resolution is beyond the resolving power of the eyes. > > >>>You are deluding yourself if you think you can. > > >>Been doing it for years. One factor is called natural optical > >>deterioration. There's a limit to resolving power that typically > >>gets worse with age. It's a primary reason why complaints are ever > >>made about tiny fonts accompanying increased pixel density. > > >The main reason people complain about tiny fonts > > I'd like to see a cite for the assertion of this "main" reason. > > >? is because they're > >often difficult to change, or changing them leads to undesirable > >effects, like web pages that don't re-wrap lines to take account > >of the change. > > I rather think the *main* reason is difficulty reading them, closely > followed by, or in conjunction with, their pervasiveness, which is > almost as commonly coupled with gray color instead of best contrast > black. I can't see the point of arguing about this; we're just looking down opposite ends of a telescope. From my end... The person to complain to about not being able to *read* small fonts is your optician. Small fonts exist, are useful in the right context when designed (or modified, see Knuth's metafont writings) with care, and aren't going to go away by being complained about. :) The people to complain to about inappropriate use of small screen fonts are the web designers who serve them up. However, is this practical? How many people are you going to complain to? How will you reach them? Where do they work now? So you're better off aiming for the single point of "failure": ones inability to change (enlarge) them. The main thrust of *my* posts has been aimed at the VC user, in which case the people to complain to are those serving up the small fonts: the computer manufacturer (if you can't read the CMOS screens) or the Debian installation team, not web designers. > Probably for most people, most of computing any more is within the > confines of a browser window. Now that ≤IE6 support is history, more > and more websites have taken to defining all sizes in px, with text > sizes most commonly those suited for the lowest pixel density > screens, rather rarely as large as 16px, which on a larger than > average size but also higher than average density 2560x1440 screen > is only 9.8pt, while a much more common 13px is <8pt and a not > uncommon 10px is 6.1pt. > > Others with poorer than it used to be eyesight, like myself, or at > least poorer than average, and/or higher density screens, surely get > rather tired as do I of the need to either zoom on entry to every > previously unvisited domain, or suffer the ill effects of either > configuring use of a minimum text size or disabling site styles > altogether. > > >But with an armoury of font sizes, six in my case from tiny to vast, > >there's no difficulty changing at all, as long as one is prepared > >to visit the bash prompt (or use a shell-escape). > > Easy for you to say. Do you have a realistic idea how hard it is to > do anything when the defaults start difficult to manage in the first > place, the proverbial chicken and egg problem? It's a whole lot > easier to make too big text smaller than it is to make too small > text bigger. Maybe size 6 isn't so vast when density is double the > reference standard and the acuity is below average. Good point. Perhaps it would be worth submitting a feature request to the d-i bug list to add an optional installer step that requests a larger default font size after the the keyboard language/layout etc. This could write lines in locations like /etc/default/console-setup and /boot/grub/grub.cfg. My smallest font gives me 213x66 characters on this laptop, and would be very uncomfortable to read for any length of time. But I can't claim that it's too difficult for me to be able to type in commands to investigate and change it. Some others probably would. > >It's easy to be misled by just considering the means to resolve two > >dots of lines from each other as the only function of d
Odd issues with Stretch installation
Hi! Not sure how best to report this, as I have no idea what Debian package (if any?) handles the installer. In trying to test an Xfce patch, I spun up a virtual machine (using VirtualBox under my main Debian Stretch installation, though I doubt that makes any difference). The virtual hard disk I assigned it is 8GB total in size, and I gave it 4GB of RAM. Two problems: 1) The default settings gave 4GB to the root partition and 4GB to the swapper. Probably a poor choice, but not overly serious except for... 2) ... the installer running out of disk space is not, apparently, an error. I had no idea whatsoever that there had been any installation difficulties. The first sign of failure was that, after installation, the GUI didn't load properly - just a black screen with a mouse cursor. In trying to track down the failure, I found the disk to be full, so I didn't bother analyzing it any further. Unfortunately, I'm still having trouble after reallocating it (6GB root, rest to swap) - so it's some other problem. How should I go about tracking it down? Chris Angelico
To "Brian"
Brian, Please contact me off list with an email address to which a reply will work. Randy Kramer
Re: How to get Jessie to run at boot time -- Problem solved
- Original Message - From: "Brian" To: debian-user@lists.debian.org Sent: Wednesday, September 14, 2016 5:09:12 PM Subject: Re: How to get Jessie to run at boot time -- Problem solved > What is "unenlightening" to you may not be unenlightening to others; > trust me on that. "garbage" is *your* value judgement; > No, I'm going to insist on my "garbage" denotation. Since I have a > very > acceptable way of going from one OS to another, your input on what > os-prober > returned to me is of little interest to me, and much less to the > other members > of this E-list, I'm sure. You can insist on what you want. It is easy when only you know what the the output is. I've seen error messages before. > an expert programmer, which I used to be but am not any more, could > put those > few simple steps into a "first of all" window. Maybe a simple grub > file? That's fine; it does what you want and will serve you well. Stick with it. but forget about involving GRUB. But a flow chart to do it would be easy: Read input if input=L then do nothing else if input=W, then change boot method to Windows Boot Manager else return to read input fi Something like that could be easily implemented, methinks. But I'm not going to do it. > Yes. If I could move stuff from my Windows OS to my Jessie, and vice > versa, that would be a big help. Any suggestions from anyone about > that? > Linux used to be able to go into MS-DOS and put files there and get > files > out of there. Has anyone any information on that? I rather think there is an answer in the response you quoted. I didn't see it. Remind me. >xorg(or maybe it was x11), and my 'startx', from my old > wheezy(fortunately >saved) worked, after I'd done a few tweeks to my .xinitrc. I tried my >old beloved sawfish(now wmctl) but that didn't work as well as > metacity. Good. (Your technique is extraordinary but comments on it are outside the scope of this thread). Thank you! I would rather start off with a X-less tty1 and then enter X with my own choice of what to run, how the background looks, etc. startx, with a good .xinit, does all I want. Simplicity, dear my lord, makes computing yare. > a username and password which got me, and keeps me, online . . . but only for > the > Windoze side. I gotta do some exploring to see if I can make this work with > Jessie. I'm confident you are resourceful and will manage. I trust that your confidence in me is not misplaced. Alan
Re: lynx - not all sites readable
Hi, Forgive this not being in context. If you are using the most current development edition of Lynx from April 25 of this year and you are reaching sites that present a message like the following, 403 forbidden, I suggest you try the following. open the options menu and arrow down to the item that says "send user agent," with an exclamation mark because the change cannot be saved permanently. unchecked this option do the temporary save options and you will get confirmation that the value has been accepted. if you are still on the site in question, things may improve right away. if not try the site again, with positive results..or such is my experience almost all of the time when I reach the forbidden message. I hope this is helpful, Karen On Thu, 15 Sep 2016, Brian wrote: On Wed 14 Sep 2016 at 22:26:08 +0200, Hans wrote: Correction: However, I could open www.nvidia.com, but could not jump to the submenu alled "Treiber". Then I tried to go to www.nvidia.de, but lynx told me, "This site is forbidden". Must be: www.nvidia.de could be opened www.nvidia.com was forbidden. Sorry for that. What do you get with lynx -useragent "Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.8.0" www.nvidia.com ?
Re: lynx - not all sites readable
On Wed 14 Sep 2016 at 17:46:31 (-0400), Henning Follmann wrote: > On Wed, Sep 14, 2016 at 05:06:29PM -0400, Jude DaShiell wrote: > > One of these days, I'd like to put a website up and permit only text > > browsers like links and lynx and edbrowse full access and either > > block all of the graphical browsers or simply cause all of them to > > crash. > > > That is stupid, petty and pretty much a waste of time. Is there any reason to try to make replies to your post get CC'd to the OP with Mail-Followup-To: Jude ..., Hans ..., debian-user@lists.debian.org ? Cheers, David.
Re: internet connectivity from Comcast (was: How to get Jessie to run...)
Alan McConnell composed on 2016-09-14 17:11 (UTC-0400): My final problem is: how to get my Jessie to get on line. I don't think this is anything anyone here can help me with, since I live in a retirement community which has a huge contract with Comcast. Is it a cable account, or is it a DSL account? Appropriate help from here, should you choose to accept any, depends on your answer. I called a tech person here, and he gave me a username and password which got me, and keeps me, online . . . but only for the Windoze side. I gotta do some exploring to see if I can make this work with Jessie. Luckily[1], I'm not a Comcast subscriber, so I cannot speak to this from experience. Maybe something following can spur you into finding a path to a solution. ISTR that some cablecos provide both a router (aka firewall and possibly a switch) and a modem in the same box, like DSL providers typically do. DSL providers normally require a login process with username and password. OTOH, cable providers typically do not require login, depending instead on the unique MAC address of the cable modem. It sounds to me like you either do not have an internet router between your PC and the modem, or have a combination modem/router/firewall, and so needs Jessie to somehow login similarly to how the tech enabled you to connect in Windows. Had you a separate internet router that you own, then the router could perform login duty, and internet connectivity would not depend on which OS you booted. [1] http://arstechnica.com/business/2015/06/comcast-customer-satisfaction-rating-plummets-again/ http://www.cheatsheet.com/business/the-top-5-worst-corporate-citizens-in-the-u-s.html/?a=viewall -- "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/
Re: How to get Jessie to run at boot time -- Problem solved
On Thu 15 Sep 2016 at 00:33:09 +0100, Lisi Reisz wrote: > On Wednesday 14 September 2016 23:09:12 Brian wrote: > > > Ah. That's good. Your E-mail reader seems to respect my > > > indentations. Others don't, alas. Do you perchance use mutt? > > Indentations count as formatting. Plain text is supposed not to preserve > formatting. I think you can be excused from thinking I wrote that but I didn't. Nothing for anyone to get bothered about as far as I am concerned. -- Brian.
Re: lynx - not all sites readable
personally i prefer links just seems to work better. especially if you install gpm also. make a great combo for terminal only browsing. henning -> because it would be fun. i've had to browse forums before using a text only browser trying to fix my X. it will make you a happy camper to have a graphic browser if you ever have to spend a couple of hours trying to find something on the web with a text browser. em
Re: How to get Jessie to run at boot time -- Problem solved
On Wednesday 14 September 2016 23:09:12 Brian wrote: > > Ah. That's good. Your E-mail reader seems to respect my > > indentations. Others don't, alas. Do you perchance use mutt? Indentations count as formatting. Plain text is supposed not to preserve formatting. Lisi
Re: lynx - not all sites readable
On Wed 14 Sep 2016 at 22:26:08 +0200, Hans wrote: > Correction: > > However, I could open www.nvidia.com, but could not jump to the submenu > > alled "Treiber". Then I tried to go to www.nvidia.de, but lynx told me, > > "This site is forbidden". > > > Must be: > www.nvidia.de could be opened > www.nvidia.com was forbidden. > > Sorry for that. What do you get with lynx -useragent "Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.8.0" www.nvidia.com ?
Re: How to get Jessie to run at boot time -- Problem solved
On Wed 14 Sep 2016 at 17:11:26 -0400, Alan McConnell wrote: Alan McConnell's responses are indented and begin with >. > From: "Brian" Brian's resonses are not indented. > > > 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. >Ah. That's good. Your E-mail reader seems to respect my indentations. > Others >don't, alas. Do you perchance use mutt? Perchance. > What is "unenlightening" to you may not be unenlightening to others; > trust me on that. "garbage" is *your* value judgement; > No, I'm going to insist on my "garbage" denotation. Since I have a > very > acceptable way of going from one OS to another, your input on what > os-prober > returned to me is of little interest to me, and much less to the > other members > of this E-list, I'm sure. You can insist on what you want. It is easy when only you know what the the output is. > > But I'd like to defend what Lisi calls a "kludge". Here is what I > do: when I > boot, or reboot my machine, if I do nothing I get my Jessie, which > is what I > want. If I want to go to Windoze, I gotta hold the F12, as Felix > Mieta taught > me several moons ago, and then I get put into a nice menu: Choose > the boot > manager. I use my Arrow keys to get to Windows boot manager, and > voila! in a > few seconds I'm in Windoze. Not so difficult after all. And I > would think that > an expert programmer, which I used to be but am not any more, could > put those > few simple steps into a "first of all" window. Maybe a simple grub > file? That's fine; it does what you want and will serve you well. Stick with it. but forget about involving GRUB. > We Debian users yearn for the day when copy 'n paste and USB sticks are > invented. It will make things so much easier to move information (which > is severely lacking from you in this thread) about. > Yes. If I could move stuff from my Windows OS to my Jessie, and vice > versa, that would be a big help. Any suggestions from anyone about > that? > Linux used to be able to go into MS-DOS and put files there and get > files > out of there. Has anyone any information on that? I rather think there is an answer in the response you quoted. > > > 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. >That situation has changed as of just an hour ago. I did a reinstall > of >xorg(or maybe it was x11), and my 'startx', from my old > wheezy(fortunately >saved) worked, after I'd done a few tweeks to my .xinitrc. I tried my >old beloved sawfish(now wmctl) but that didn't work as well as > metacity. Good. (Your technique is extraordinary but comments on it are outside the scope of this thread). > > (*) Does anyone here know how to create a .Xauthority file? That is one > > of the > > things the Jessie installer failed to provide me with. > > You've asked this five months ago: > I did indeed. That was before my old machine gave up the ghost. I > am > impressed, Brian, that you keep such careful track of me. I have a reasonably good memory. It was GNOME not installing libreoffice which triggered the connections. So unusual. You never responded to that either at the time it was pointed out. > My final problem is: how to get my Jessie to get on line. I don't think this > is > anything anyone here can help me with, since I live in a retirement community > which has a huge contract with Comcast. I called a tech person here, and he > gave me > a username and password which got me, and keeps me, online . . . but only for > the > Windoze side. I gotta do some exploring to see if I can make this work with > Jessie. I'm confident you are resourceful and will manage. -- Brian.
Re: lynx - not all sites readable
On Wed, Sep 14, 2016 at 05:06:29PM -0400, Jude DaShiell wrote: > One of these days, I'd like to put a website up and permit only text > browsers like links and lynx and edbrowse full access and either > block all of the graphical browsers or simply cause all of them to > crash. > That is stupid, petty and pretty much a waste of time. -H -- Henning Follmann | hfollm...@itcfollmann.com
Re: exim4 some config error causing error how to pinpoint
Liam O'Toole writes: > dpkg-reconfigure exim4-config Thanks, that was pretty painless. And thanks for the url to the documentation section. I've now progressed on to where I was aiming for. I wanted to have one debian box as main mail client. Yet be able to send mail from a couple of others. I've managed to get that working by aiming the secondary hosts at the main mail host as smarthost. That main host is inturn aimed at an internet smarthost. So far all working except one glitch. Here is the cast of characters: HOST1 Main mail host HOST2 secondary host User1 HOST1 User2 HOST1 user HOST2 I can send a mail from HOST2 to a user on HOST1 using the correct address. user1@HOST1 That main host has only two users. I can send mail from HOST2 to only one of those users. That is. if, from HOST2, I send mail to a HOST1 user like: user1@HOST1 It arrives in user1 slot at /var/spool/mail/user1 on HOST1. However If I try sending to user2@HOST1 it never gets there. Even though the smtp output on sending HOST2 appears to be saying it was sent and received successfully. --- --- ---=--- --- --- orignating on HOST2 tmail user2@HOST1 sending like this: mailx -v -s "TEST 160914_163910" user1@HOST1 < ~/txtmsg.txt LOG: MAIN <= u...@host2.local.lan U=user1 P=local S=422 smtp output: delivering 1bkGxi-0002L3-U4 R: smarthost for user2@HOST1 T: remote_smtp_smarthost for user1@HOST1 Connecting to HOST1.local.lan [192.168.1.5]:25 ... connected SMTP<< 220 dv ESMTP Exim 4.86 Wed, 14 Sep 2016 16:47:36 -0400 SMTP>> EHLO HOST2.local.lan SMTP<< 250-dv Hello HOST2.local.lan [192.168.1.17] 250-SIZE 52428800 250-8BITMIME 250-PIPELINING 250 HELP SMTP>> MAIL FROM: SIZE=1464 SMTP>> RCPT TO: SMTP>> DATA SMTP<< 250 OK SMTP<< 250 Accepted SMTP<< 354 Enter message, ending with "." on a line by itself SMTP>> writing message and terminating "." SMTP<< 250 OK id=1bkH5k-0008FT-UQ SMTP>> QUIT LOG: MAIN => user2@HOST1 R=smarthost T=remote_smtp_smarthost H=HOST1.local.lan [192.168.1.5] C="250 OK id=1bkH5k-0008FT-UQ" LOG: MAIN Completed Mail never appears at HOST1 /var/spool/mail/user2
Re: How to get Jessie to run at boot time -- Problem solved
- Original Message - From: "Brian" To: debian-user@lists.debian.org Sent: Wednesday, September 14, 2016 1:51:50 PM Subject: Re: How to get Jessie to run at boot time -- Problem solved On Wed 14 Sep 2016 at 11:34:31 -0400, Alan McConnell wrote: > From: "Felix Miata" > > 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. This following quotes beginning with > are from Alan McConnell. > 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. Ah. That's good. Your E-mail reader seems to respect my indentations. Others don't, alas. Do you perchance use mutt? What is "unenlightening" to you may not be unenlightening to others; trust me on that. "garbage" is *your* value judgement; No, I'm going to insist on my "garbage" denotation. Since I have a very acceptable way of going from one OS to another, your input on what os-prober returned to me is of little interest to me, and much less to the other members of this E-list, I'm sure. But I'd like to defend what Lisi calls a "kludge". Here is what I do: when I boot, or reboot my machine, if I do nothing I get my Jessie, which is what I want. If I want to go to Windoze, I gotta hold the F12, as Felix Mieta taught me several moons ago, and then I get put into a nice menu: Choose the boot manager. I use my Arrow keys to get to Windows boot manager, and voila! in a few seconds I'm in Windoze. Not so difficult after all. And I would think that an expert programmer, which I used to be but am not any more, could put those few simple steps into a "first of all" window. Maybe a simple grub file? We Debian users yearn for the day when copy 'n paste and USB sticks are invented. It will make things so much easier to move information (which is severely lacking from you in this thread) about. Yes. If I could move stuff from my Windows OS to my Jessie, and vice versa, that would be a big help. Any suggestions from anyone about that? Linux used to be able to go into MS-DOS and put files there and get files out of there. Has anyone any information on that? > > 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. That situation has changed as of just an hour ago. I did a reinstall of xorg(or maybe it was x11), and my 'startx', from my old wheezy(fortunately saved) worked, after I'd done a few tweeks to my .xinitrc. I tried my old beloved sawfish(now wmctl) but that didn't work as well as metacity. > (*) Does anyone here know how to create a .Xauthority file? That is one of > the > things the Jessie installer failed to provide me with. You've asked this five months ago: I did indeed. That was before my old machine gave up the ghost. I am impressed, Brian, that you keep such careful track of me. My final problem is: how to get my Jessie to get on line. I don't think this is anything anyone here can help me with, since I live in a retirement community which has a huge contract with Comcast. I called a tech person here, and he gave me a username and password which got me, and keeps me, online . . . but only for the Windoze side. I gotta do some exploring to see if I can make this work with Jessie. > You are probably asking the wrong question. Best wishes to all, even to Lisi! Alan
Re: lynx - not all sites readable
One of these days, I'd like to put a website up and permit only text browsers like links and lynx and edbrowse full access and either block all of the graphical browsers or simply cause all of them to crash. On Wed, 14 Sep 2016, Jude DaShiell wrote: Date: Wed, 14 Sep 2016 17:03:22 From: Jude DaShiell To: Hans , debian-user@lists.debian.org Subject: Re: lynx - not all sites readable Resent-Date: Wed, 14 Sep 2016 21:03:51 + (UTC) Resent-From: debian-user@lists.debian.org lynx isn't suppressing or forbidding anything! The sites you visit are doing all of that blocking and forbidding. On Wed, 14 Sep 2016, Hans wrote: Date: Wed, 14 Sep 2016 16:18:59 From: Hans To: debian-user@lists.debian.org Subject: lynx - not all sites readable Resent-Date: Wed, 14 Sep 2016 20:19:31 + (UTC) Resent-From: debian-user@lists.debian.org Hi list, can someone explain, why lynx sometimes forbid websites or supresses websites? I needed a driver from Nvidia. As I had no X available, I tried download using lynx. However, I could open www.nvidia.com, but could not jump to the submenu alled "Treiber". Then I tried to go to www.nvidia.de, but lynx told me, "This site is forbidden". I found no logic for these issues. Tried http 1.0 and http 1.1, but there was no change. Does someone know more? IMO lynx is very usefull, when there is no X available! Best regards Hans --
Re: lynx - not all sites readable
lynx isn't suppressing or forbidding anything! The sites you visit are doing all of that blocking and forbidding. On Wed, 14 Sep 2016, Hans wrote: Date: Wed, 14 Sep 2016 16:18:59 From: Hans To: debian-user@lists.debian.org Subject: lynx - not all sites readable Resent-Date: Wed, 14 Sep 2016 20:19:31 + (UTC) Resent-From: debian-user@lists.debian.org Hi list, can someone explain, why lynx sometimes forbid websites or supresses websites? I needed a driver from Nvidia. As I had no X available, I tried download using lynx. However, I could open www.nvidia.com, but could not jump to the submenu alled "Treiber". Then I tried to go to www.nvidia.de, but lynx told me, "This site is forbidden". I found no logic for these issues. Tried http 1.0 and http 1.1, but there was no change. Does someone know more? IMO lynx is very usefull, when there is no X available! Best regards Hans --
Re: How to get Jessie to run at boot time -- Problem solved
- Original Message - From: "Lisi Reisz" To: debian-user@lists.debian.org Sent: Wednesday, September 14, 2016 2:05:47 PM Subject: Re: How to get Jessie to run at boot time -- Problem solved On Wednesday 14 September 2016 19:51:50 Brian wrote: > You are probably asking the wrong question. Oh, no, Brian. He is asking the right question by definition. Alan is asking it, it is therefore right. Lisi, is this kind of post helpful? Is that a question that you even ask yourself? For some reason you've taken a dislike to me, at a distance of 5000 miles. That's OK, no skin off my nose. But you are starting to irritate other members of this E-list. So please: make sure from now on that your posts contain information, and not just name-calling. We'd all appreciate it. TIA, Alan
Re: lynx - not all sites readable
Correction: > However, I could open www.nvidia.com, but could not jump to the submenu > alled "Treiber". Then I tried to go to www.nvidia.de, but lynx told me, > "This site is forbidden". > Must be: www.nvidia.de could be opened www.nvidia.com was forbidden. Sorry for that. Hans
lynx - not all sites readable
Hi list, can someone explain, why lynx sometimes forbid websites or supresses websites? I needed a driver from Nvidia. As I had no X available, I tried download using lynx. However, I could open www.nvidia.com, but could not jump to the submenu alled "Treiber". Then I tried to go to www.nvidia.de, but lynx told me, "This site is forbidden". I found no logic for these issues. Tried http 1.0 and http 1.1, but there was no change. Does someone know more? IMO lynx is very usefull, when there is no X available! Best regards Hans
Re: Testing/Unstable Synaptic broken again.
On 09/01/2016 08:51 AM, Jimmy Johnson wrote: The latest upgrades have broken Synaptic, unable to use Menus or right click and Search is affected too. Thank you upstream developing and packaging team for replacing the effected packages. Yay! These packages have now been upgraded in Sid, 'gir1.2-gtk-3.0, libgtk-3-0. libgtk-3-bin. libgtk-3-common' if you have been using testing and where effected you can temp add Sid repos and upgrade the effected packages, it will pull in a few more packages, but it is fixed. -- Jimmy Johnson Debian Stretch - Plasma 5.7.4 - AMD 64 - EXT4 at sda11 Registered Linux User #380263
Re: How to get Jessie to run at boot time -- Problem solved
On Wednesday 14 September 2016 19:51:50 Brian wrote: > You are probably asking the wrong question. Oh, no, Brian. He is asking the right question by definition. Alan is asking it, it is therefore right. We are providing the wrong answers. And to make matters worse we are doing so in Old English words that poor Alan does not know, so we must have invented them. My Tutor came from Bedford College (previous job). She would have got on well with Alan. Lisi
Re: How to get Jessie to run at boot time -- Problem solved
On Wed 14 Sep 2016 at 11:34:31 -0400, Alan McConnell wrote: > From: "Felix Miata" > > 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. This following quotes beginning with > are from Alan McConnell. > 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. What is "unenlightening" to you may not be unenlightening to others; trust me on that. "garbage" is *your* value judgement; nobody can dispute it (except in the abstract) but it unlikely to be in that category. But you did get an output; you have no idea how interesting that is. We Debian users yearn for the day when copy 'n paste and USB sticks are invented. It will make things so much easier to move information (which is severely lacking from you in this thread) about. > > 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. You claimed to be unable to install libreoffice when installing GNOME: https://lists.debian.org/debian-user/2016/04/msg00247.html I decided to bite the bullet/go with the flow, and install GNOME, the whole thing. Which I did, and it took just short of an hour. For some reason, Libreoffice was not installed. This is completely impossible using 'apt-get install gnome', of course. Not unless the Debian packaging system has a gaping hole in it. But it happened to you (and nobody else). A mishapprension on your part? Now it is X; X works fine for everyone; a mishapprension on your part? At another time it was cups; a mishapprension on your part? Where to next? How many more mishapprensions devoid of usable data are there going to be?. > (*) Does anyone here know how to create a .Xauthority file? That is one of > the > things the Jessie installer failed to provide me with. You've asked this five months ago: https://lists.debian.org/debian-user/2016/04/msg00278.html Does anyone know how to create an .Xauthority with xauth? I find the man page of xauth pretty impenetrable. You are probably asking the wrong question. -- Brian.
Vásároljon őszi divatos sportruházatot! Pierre Cardin, Lonsdale, Gelert stb. márkák széles választéka!
Trops webáruház Telefon: +36 (1) 327 7057, Email: sp...@trops.hu Vásároljon őszi divatos sportruházatot! Pierre Cardin, Lonsdale, Gelert stb. márkák széles választéka! Pierre Cardin férfi kardigán Pierre Cardin férfi gombos kardigán Anyaga 100% akril Mosógépben mosható 3 féle színben 11 990 Ft helyett most 4 090 Ft http://trops.hu/component/virtuemart/search/559226.html Lonsdale FZ férfi pulóver Férfi pulóver Lonsdale nyomtatott logó Anyaga: 65% poliészter, 35% pamut Gépben mosható 4 féle színben 15 990 Ft helyett most 8 990 Ft http://trops.hu/component/virtuemart/search/554020.html Gelert férfi dzseki Gelert férfi dzseki Víz-és szélálló 5000 mm-ig 3 féle színben 11 990 Ft helyett most 6 990 Ft http://trops.hu/component/virtuemart/search/442147.html Leíratkozom a levelezési listáról: Leiratkozás ( http://trops.hu/newsletter/index.php?option=com_acajoom&Itemid=999&act=remove&subscriber=43&cle=2a54fdef923fe4eeeb5c9db05c74d1cb&listid=24 ) NYPD Invest Kft. - 6722 Szeged, Püspök utca 11/a. 2. em. 8. Adószám: 24168821-2-06, Cégjegyzékszám: 06 09 019564
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" > 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
Re: How to get Jessie to run at boot time -- Problem solved
- Original Message - From: "Felix Miata" 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. ... > 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. Best wishes, Alan
Re: Debian Jessie : regular console instead of a hi-res one!
On 09/13/2016 02:36 PM, David Wright wrote: When I want to change resolution, which keys should I press to do that? Back in the day, when xorg.conf roamed free, you could have multiple screen resolutions noted within it and a ctrl-alt-+ would switch resolutions on the fly. That worked on CRT monitors, not sure how that would work on LEDs. Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html
Re: Gnome 3.21: how to define compose key?
On Tue 13 Sep 2016 at 19:46:03 (-0400), Doug wrote: > On 09/13/2016 04:40 PM, David Wright wrote: > >On Tue 13 Sep 2016 at 15:12:17 (-0400), Doug wrote: > >>On 09/13/2016 01:07 AM, david...@freevolt.org wrote: > >>>On Mon, 12 Sep 2016, Doug wrote: > >>> > On 09/11/2016 11:47 PM, david...@freevolt.org wrote: > >On Mon, 12 Sep 2016, david...@freevolt.org wrote: > > > >>And if I wanted that behavior all the time, I would edit the file > >>/etc/default/keyboard, adding compose:rwin to the comma-separated list > >>of pairs in XKBOPTIONS. > >Of course, editing that file will change the default system-wide, for > >everybody. Even, erm, Mark! (...if running Ubuntu.) > > > >Maybe that is not what you want. > > > > > It looks like your code sets up the right Win key to be Compose, > I don't know why it would bother anyone using the machine. It > wouldn't stay that way > if you rebooted into Windows, and the key does nothing at all > (that I know of) in Linux. > >>>I see your point. That particular change is not going to surprise > >>>anyone. It won't turn an expected character key into an unexpected > >>>dead key, and then keep some other user from entering their password, > >>>quotation marks, etc. > >>> > >>>In other words, no fun at all. > >>> > As it happens, I have an old IBM model M keyboard with no > Windows keys, so I use the right alt key. Also, PCLOS has an > option in the keyboard setup to choose a Compose key. Are you > sure that Debian doesn't > have that capability built in, somewhere? > >>>No, I am certainly not certain about that. And I imagine there are > >>>desktop-environment-specific ways of configuring keyboard default > >>>preferences like this, and doing so per-user. It will be interesting > >>>to see if someone who uses the OP's DE suggests one. > >>> > >>>In the meantime there is also this: > >>> > >>># dpkg-reconfigure keyboard-configuation > >>> > >>>It asks many questions. One of the questions it eventually asks is > >>>about your compose key--whether you want one, which key you want it to > >>>be, etc. > >>> > >>>It edits /etc/default/keyboard to conform to your answers. So the same > >>>caveat about "system-wide changes, hope everyone will be equally > >>>thrilled" applies. A backup of the file you started with, before you > >>>made changes, could be convenient to have. > >>> > (I happen to be a big fan of Compose, because even if you don't > write a European language, > >>>Aha, a Brexit joke. Good one. > >>> > it does other useful things—like that m-dash I just wrote. > >>>Mastery of sarcasm: Check. > >>> > And ½, ⅓, ⅜, ©, 75°, µF, 17¢, and others.) > >>>I see recognisable glyphs for five out of seven of those. My > >>>environment does not support the other two. > >>> > >>>So I know what they are not, but I don't know what they are. Very > >>>mysterious. Could be IPA symbols. Could be a happy face next to a > >>>clover/club symbol. I may never know. > >>Don't know what you are not seeing. Here's what I wrote—and what I do see— > >> > >>one-half, one-third, three-eighths, copyright symbol, degree sign > >>after 75, Greek letter mu meaning micro before F (for Farads), cent > >>sign after17. > >Oh good, someone who uses these! Can you help me with how you use the > >last of these characters: > > > >⅓ ⅔ ⅕ ⅖ ⅗ ⅘ ⅙ ⅚ ⅛ ⅜ ⅝ ⅞ ⅟ > > > >It doesn't say it's a combining character and I can't find any > >denominators anyway to go with it. > > > >(For those people using fonts having qualities other than a wide > >repertoire, they're the thirds, fifths, sixths and eighths followed > >by a solitary 1/ numerator.) Thank you to Siard; I grepped "denom" and not "subscript". > Dav[id], I'm not sure, but I don't think you can write a number greater than 8 > in this system. I just tried to create one-ninth, but was unsuccessful. > Perhaps someone smarter than me has an answer. Not smarter; there's a list somewhere. Extracted: 2150VULGAR FRACTION ONE SEVENTH # 0031 2044 0037 2151VULGAR FRACTION ONE NINTH # 0031 2044 0039 2152VULGAR FRACTION ONE TENTH # 0031 2044 0031 0030 2153VULGAR FRACTION ONE THIRD # 0031 2044 0033 then as quoted above, and, knocking around: 2189VULGAR FRACTION ZERO THIRDS * used in baseball scoring, from ARIB STD B24 # 0030 2044 0033 Cheers, David.
Re: odd load patterns - SOLVED
On 9/14/2016 10:14 AM, Miles Fidelman wrote: > Well, I found out where all that load was coming from. > > Looks like a recent Thunderbird update reset its config to "keep all > messages for this account on this computer" - for all accounts The first time this fiasco happened - the update happened that enabled GLODA for all accounts and reset all individual offline folder settings for all accounts - was sometime around the TB 3 - 3.1 update. This was the one time I seriously looked for an alternative to TB, it made me so furious, as I have many (15+) IMAP accounts, most with a LOT of email AND a lot of folders, and with very specific OFFLINE settings for certain folders. If the devs cause this to happen again, I will be even more furious than I was then, even if it is an accident. So, hopefully you are wrong, or it is some obscure bug (maybe triggered by a misbehaved Addon) that will not hit me (or most users). > Given that I'm the admin for some servers, and a bunch of email lists, I > keep filtered spam and viruses for analysis, and I keep email going back > about 30 years that kind of causes a lot of synchronization traffic > - to the point of really bogging down our imap daemon. > > Consider this a friendly warning for those of you who use Thunderbird & > IMAP!
Re: odd load patterns - SOLVED
Well, I found out where all that load was coming from. Looks like a recent Thunderbird update reset its config to "keep all messages for this account on this computer" - for all accounts Given that I'm the admin for some servers, and a bunch of email lists, I keep filtered spam and viruses for analysis, and I keep email going back about 30 years that kind of causes a lot of synchronization traffic - to the point of really bogging down our imap daemon. Consider this a friendly warning for those of you who use Thunderbird & IMAP! Cheers, Miles Fidelman Hi, I wonder if anybody might have some thoughts on this: Lately, our server has been showing high loading, but top shows that the CPU is mostly in wait mode, and iotop shows low disk i/o traffic. Usually, the system shows high load when either a. Someone is indexing our web server (which shows up as CPU load on apache). b. Our list manager is processing a bunch of traffic (most of the load comes from spam and virus filtering - which shows up as cpu load on amavisd, and clamd, as well as a lot of disk i/o). The one place I see this effect behavior, if for email clients accessing IMAP - I've been seeing timeouts, and exceptionally high delays to load an inbox, or move stuff to the trash. This pattern is new - and there's really nothing that I've changed in terms of configuration or loading that I can see. So... any thoughts? Any diagnostic approaches? Thanks much, Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra
Re: odd load patterns
On 9/14/16 2:53 AM, Frédéric Marchal wrote: On Tuesday 13 September 2016 20:09:26 Miles Fidelman wrote: Hi, Lately, our server has been showing high loading, but top shows that the CPU is mostly in wait mode, and iotop shows low disk i/o traffic. How do you know the load is high? Where is the indication coming from? Umm... "top" and "iotop" (which addresses your own follow-up question) I'm interested in more opinions and diagnostic tools too because my laptop suddenly became very slow and unresponsive yesterday until I restarted it. top was showing a mostly idle cpu but kde system activity was displaying a lot of "disk sleep". -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra
Re: Debian Jessie : regular console instead of a hi-res one!
David Wright composed on 2016-09-13 13:36 (UTC-0500): Rather curious to see a regular participant here with a .co.uk mailing address apparently in a university environment in a UTC-0500 time zone. Curiosity makes it for me a recurring distraction, wondering just what part of the world this might be, somewhere north of Wisconsin, Minnesota or North Dakota? :-p On Thu 08 Sep 2016 at 12:53:49 (-0400), Felix Miata wrote: David Wright composed on 2016-09-08 09:08 (UTC-0500): >You can play with framebuffers and kernel drivers all you like. >What you cannot do is alter the layout of pixels on the screen. Absolutely true. >If you don't use a resolution that matches those pixels exactly, >nothing you do can compensate. False. The difference from one resolution to the next is easily lost if the screen resolution is beyond the resolving power of the eyes. >You are deluding yourself if you think you can. Been doing it for years. One factor is called natural optical deterioration. There's a limit to resolving power that typically gets worse with age. It's a primary reason why complaints are ever made about tiny fonts accompanying increased pixel density. The main reason people complain about tiny fonts I'd like to see a cite for the assertion of this "main" reason. ? is because they're often difficult to change, or changing them leads to undesirable effects, like web pages that don't re-wrap lines to take account of the change. I rather think the *main* reason is difficulty reading them, closely followed by, or in conjunction with, their pervasiveness, which is almost as commonly coupled with gray color instead of best contrast black. Probably for most people, most of computing any more is within the confines of a browser window. Now that ≤IE6 support is history, more and more websites have taken to defining all sizes in px, with text sizes most commonly those suited for the lowest pixel density screens, rather rarely as large as 16px, which on a larger than average size but also higher than average density 2560x1440 screen is only 9.8pt, while a much more common 13px is <8pt and a not uncommon 10px is 6.1pt. Others with poorer than it used to be eyesight, like myself, or at least poorer than average, and/or higher density screens, surely get rather tired as do I of the need to either zoom on entry to every previously unvisited domain, or suffer the ill effects of either configuring use of a minimum text size or disabling site styles altogether. But with an armoury of font sizes, six in my case from tiny to vast, there's no difficulty changing at all, as long as one is prepared to visit the bash prompt (or use a shell-escape). Easy for you to say. Do you have a realistic idea how hard it is to do anything when the defaults start difficult to manage in the first place, the proverbial chicken and egg problem? It's a whole lot easier to make too big text smaller than it is to make too small text bigger. Maybe size 6 isn't so vast when density is double the reference standard and the acuity is below average. It's easy to be misled by just considering the means to resolve two dots of lines from each other as the only function of display resolution. The crispness of a font depends on the angles of edges to which the eye is very sensitive, even when it can't resolve the actual dots themselves that make up that edge. Maybe it's time to emulate some senior eyeballs. Hang some cheesecloth in front of your face, turn screen brightness down below 33%, let plenty of bright sunlight into the area where the display faces, and double or triple the normal distance between screen and face, then try to discern any difference in crispness between the vtty's default 9x16 font at 1280x720, and larger pixel size fonts on the same display at a native 1920x1080. Once the threshhold is reached, more px density is wasted. Another factor has to do with screen size and distance, not necessarily caused by deterioration, but because of eyes never that good to begin with, and corrective lenses that do a better job at particular focal lengths. Too close and pixels can become apparent and bothersome. More distance can work better. If the pixels are as large as to be bothersome, then make them smaller, ie use a higher resolution on the screen! Why would you ever use a lower resolution in that case? Visual threshhold vs. ease of (re)configuring. For a lot of people, the only way they know to deal with everything being too small is to reduce resolution. Is it ideal? Of course not! Do people do it? It's common among the simple minded and the elderly. IOW: 1-Don't knock it if you haven't tried it. By this I don't mean tried only on Debian installations either. The default framebuffer font of Debian and its derivatives is very commonly different from non-Debian distros, represented by the spindly ugly thing used by Ubuntu. Without Plymouth, one can typically see the
Re: How to get Jessie to run at boot time -- Problem solved
On Wed 14 Sep 2016 at 02:44:14 -0400, Felix Miata wrote: > Alan McConnell composed on 2016-09-13 20:50 (UTC-0400): > ... > >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 . . . " > > As explained by Brian on 2016-09-13 15:40 (UTC+0100), first came Jessie, > then came Windows 10, and an apparent solution has since been provided for > those who choose to install a Debian version younger than Windows 10. I might have come to an invalid conclusion from reading the changelog snippet quoted earlier and then went to lay far too much emphasis on Jessie d-i preceding Windows 10. What is fixed is not whether an entry for Windows 10 is displayed but the wording of the entry in the GRUB menu. Apologies for anything misleading. > 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. Yes it does appear curious, especially as the implication in the changelog (and a few reports I've seen elsewhere) is that a Windows 10 install can be discovered by os-prober but provides "Windows Recovery Partition" as GRUB's menu entry. > Should you be game to try installing Jessie again, you might try a network > installation started via a Stretch installer. Possibly (I haven't tried, and > not only do I have no interest in kicking either of my sleeping dog Windows > 10s, I'm exclusively responsible for primary bootloader maintenance on all > my computers, and rarely allow os-prober to run.) the os-prober shortcoming > that troubled you might be avoided in such manner. os-prober from stretch/unstable should install on Jessie with 'dpkg -i' but I am much less confident it would fix a missing entry, even though it should do no harm to try. Another possibilty is https://wiki.debian.org/DualBoot/Windows10
Re: odd load patterns
On 2016-09-14, Miles Fidelman wrote: > Hi, > > I wonder if anybody might have some thoughts on this: > > Lately, our server has been showing high loading, but top shows that the > CPU is mostly in wait mode, and iotop shows low disk i/o traffic. I'm looking here (maybe a little outdated from 2010?): https://www.tummy.com/articles/isolating-heavy-load/ Maybe an idea or two. > Usually, the system shows high load when either > > a. Someone is indexing our web server (which shows up as CPU load on > apache). > > b. Our list manager is processing a bunch of traffic (most of the load > comes from spam and virus filtering - which shows up as cpu load on > amavisd, and clamd, as well as a lot of disk i/o). > > The one place I see this effect behavior, if for email clients accessing > IMAP - I've been seeing timeouts, and exceptionally high delays to load > an inbox, or move stuff to the trash. > > This pattern is new - and there's really nothing that I've changed in > terms of configuration or loading that I can see. > > So... any thoughts? Any diagnostic approaches? > > Thanks much, > > Miles Fidelman > -- “Whatever is rejected from the self, appears in the world as an event.” C.G. Jung
Re: How to get Jessie to run at boot time -- Problem solved
On Wednesday 14 September 2016 01:50:44 Alan McConnell wrote: >Re Royal Holloway: boys were added in 1966, a year before my time > there. But there were always male faculty there, especially in math, which > subject has, most unfortunately, suffered from a dearth of qualified women. > This is beginning to change: the AMS puts a lot of effort in supporting > women and departments supporting women. But: https://en.wikipedia.org/wiki/Charlotte_Scott and https://en.wikipedia.org/wiki/Philippa_Fawcett Quality, not quantity. Lisi
Re: How to get Jessie to run at boot time -- Problem solved
On Wednesday 14 September 2016 01:50:44 Alan McConnell wrote: > More perhaps tomorrow. I have tasks to perform before bed. 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 . . . " It can. But MS put a lot of effort into making it difficult to dual boot with Windows 10, and the installer you are using was, as you have been told, written before Windows 10 was released. The first installer to be written AFTER Windows 10 can apparently handle it well. I haven't tried. Lisi
