Re: How to arrange for booting to console
On Sun, 2016-09-11 at 19:03 -0400, The Wanderer wrote: > AFAIK, the GRUB2 menu is defined from /boot/grub/grub.cfg; the headers > of that file say that it's generated from templates in /etc/grub.d/ and > settings in /etc/default/grub. > > Based on a quick look in those locations, you probably want to adjust > one of the GRUB_CMDLINE_LINUX* settings in the latter file. I haven't > done much tweaking in that area myself, however (I only migrated to > GRUB2 within the last year, give or take), so I can't confirm that with > any certainty. That's how I tweak grub to change things like the boot timeout and kernel commandline. I.e. edit etc/default/grub and as that file says "run 'update-grub' afterwards". -- Tixy
Re: How to arrange for booting to console
On Sun, 11 Sep 2016, Harry Putnam wrote: That sounds promissing. Used one of the methods below and quickly realized I was expecting a nice big framebuffered text console with a much higher resolution than the standard. (Previously my OS of choice was gentoo), But of course all that has to be setup as I recall it is done with a few extra bits on the kernel line grub.conf Using grub2 I'm thoroughly lost what or where one would edit to allow a console frame buffer. Maybe OP will find this thread helpful: "Debian Jessie : regular console instead of a hi-res one!" https://lists.debian.org/debian-user/2016/09/msg00127.html
Re: Gnome 3.21: how to define compose key?
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.
Re: SSH Connection Behind A Router/Firewall
On Thu, Sep 8, 2016 at 10:49 AM, Tim McDonough wrote: > I have a very straightforward Debian Jessie machine on my network. For SSH > it uses the standard/default Port 22 and accessing it via ssh works just > fine from anywhere on the local network. > > I also have a NetGear router configured so that a connection from the > outside world using Port 1024 gets forwarded to the local IP and Port 22 on > the LAN. My problem is when I attempt a connection from the outside world > the connection is refused. Presuming the ssh "client" is on the WAN, have you set the "destination" port to 1024 in that client? For example in *nix box, it would be "ssh -p 1024 someuser@your_wan_pub_ip" -- Arun Khan
Re: How to get Jessie to run at boot time -- Problem solved
David Wright composed on 2016-09-11 21:44 (UTC-0500): ... Subject: Re: How to get Jessie to run at boot time -- Problem solved ... How is it beneficial to list anyone here or searching list archives to continue a thread by chastising an OP for being imperfect more than 12 hours after OP added string "solved" to the subject and thanked people who provided useful help? https://lists.debian.org/debian-user/2016/09/msg00398.html -- "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: Fwd: How to get Jessie to run at boot time -- Problem solved
On Sun 11 Sep 2016 at 18:49:47 (-0400), Alan McConnell wrote: > From: "Brian" > Sent: Sunday, September 11, 2016 2:51:50 PM > Subject: 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? > > Windows 10. If there is a more exact name, I don't know it. > > Deconstruction of this statement follows: > Brian, you are in a bad temper. Did you read the amended title of > this > and previous messages? "Problem solved". > > Suggestion: simply don't reply to any of my (perhaps) forthcoming > questions > and/or comments. That will save both you and me time and spare us > both > annoyance. This is a summary of what I've gleaned from your posts: https://lists.debian.org/debian-user/2016/09/msg00296.html How do I boot the new jessie installation? https://lists.debian.org/debian-user/2016/09/msg00337.html I don't need [rescue mode]. I played with the BIOS. I am busy installing stuff. How do I do it? [sic] https://lists.debian.org/debian-user/2016/09/msg00364.html Do I want to install a different grub? I'd like a response from one of them(if they exist here) letting me know how [a dual boot system] works. https://lists.debian.org/debian-user/2016/09/msg00398.html What works for me now is the following: [and your solution] I shudder to think of someone taking my advice [etc] 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. https://lists.debian.org/debian-user/2016/09/msg00408.html 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. Now, I'm happy that you have what you consider is a working solution. I don't know what you see when you press F12, and I don't understand what the "L or M" business is in times past. I can't find any description of what your actual problem is, with some symptoms, other than that the computer doesn't do what you want it to do, in some way that's unspecified. I don't think that the maintainers of grub or the Debian installer will be interested in this, beyond asking you to read the Debian installation guide and the grub documentation (a long web page). You need to report more specifically where what you read diverges from what happens with your computer, including objective descriptions of the problem rather than vague complaints. People here will try to help you, but they can't divine what's happening on your machine in the absence of facts. If there's really a bug, then you may get help on how to either fix it, or report it in such a way that the busy maintainers can isolate and act upon it. Re your last post quoted above, what's the problem with running jessie and reporting the information you were asked for? I assume that you installed jessie so that you could run it occasionally. I know some people on this list treat it like the telephone ("I'm going to bed now, and will try it in the morning" kind of thing) but the list will wait for the next occasion that you boot up your jessie. In fact, it often pays *not* to give quick responses because it gives you time to think on the problem, and you *are* the best-placed person to come up with a solution (as you have done, in a way). Cheers, David.
Re: Gnome 3.21: how to define compose key?
On Sun, 11 Sep 2016, Joost Kraaijeveld wrote: I want to use my right super key (right win) as my compose key to be able to type accented letters. I don't use gnome, but I expect $ setxkbmap -option "compose:rwin" would do what you want. 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. So, for example, if I found this there, originally, XKBOPTIONS="lv3:caps_switch,compose:ralt,grp:menu_toggle" I would replace it like so: #XKBOPTIONS="lv3:caps_switch,compose:ralt,grp:menu_toggle" XKBOPTIONS="lv3:caps_switch,compose:rwin,grp:menu_toggle" I would expect it to work. Maybe it will.
Re: [resolved] FireFox broken,
On Sun 11 Sep 2016 at 15:28:03 (-0500), Mark Allums wrote: > >I was amazed a couple days ago, I switched my default browser to > >chromium, more for S&G than any other reason, as its now quite long in > >the tooth. I had to go thru an email driven procedure to verify the pw > >at PP, but then it worked. And its kept on working... > > > >And I've been using it for my daily dose of fake news from the mainsleaze > >news sites, and except for cbsnews.com, nearly every video plays AND > >stays in lip synch. > > > >I can now buy something online, and it works again. I think I'll leave it > >that way for a while. :-) > > > >Firefox is still busted. > > Agreed. And yet there are few complaints here. Up to the time of writing, I've had no problem reaching the sites you mentioned, and no security warnings (except that I intentionally browse with an old flashplayer configured so that it doesn't start playing them but asks for confirmation instead). > I believed our problems were related, and I still do. I > have run into other problems since I installed libnss3 from sid, > problems that I haven't had time to relate here on debian-user up to > now. For instance, I couldn't verify my email with a certain site > using Firefox, the site simply said email not verified. (You know, > how they send you an email, and you click on a link.) I copied the > link address to Google Chrome, and it worked, first try. There are > a number of examples like this that I won't bother to enumerate, > because they are incidental. The problems surfaced with an update > to firefox, that's why I blame Firefox. I thought you just wrote "I have run into other problems since I installed libnss3 from sid" above and "I blame a crypto update for this" earlier. I couldn't follow your posts because I read a lot of statements of blame before I saw any evidence of what your problems were. > I think now that Gene's > problems won't all be cured by installing a recent libnss3. Some > people blame the age of Gene's system, Gene and I both run "wheezy" (though I run jessie too). He has many problems, often reported here, and some of the fixes he uses are very un-Debian to say the least. (I wrote "wheezy" because Gene's system is really only *based on* wheezy.) > but I am running stretch, and > I have run into the same problems (plural). You can blame my > problems on my running Testing, but it's funny that both of us on > two completely different systmes starting having trouble with the > same update to Firefox/Iceweasel. I've still only seen your assertions that they're the same problems?/symptoms?/messages? (Not even sure which of these applies.) Hoping things sort themselves out (often happens on testing)... Cheers, David.
Re: Fwd: How to get Jessie to run at boot time -- Problem solved
On Sun, Sep 11, 2016 at 06:49:47PM -0400, Alan McConnell wrote: > Deconstruction of this statement follows: > Brian, you are in a bad temper. Did you read the amended title of > this > and previous messages? "Problem solved". > > Suggestion: simply don't reply to any of my (perhaps) forthcoming > questions > and/or comments. That will save both you and me time and spare us > both > annoyance. Given your responses to someone who was, in any event, trying to help, cross me off your list as well. *PLONK*
Re: How to arrange for booting to console
On 2016-09-11 at 18:52, Harry Putnam wrote: > The Wanderer writes: > >> On 2016-09-11 at 17:04, Harry Putnam wrote: >> >>> How can I arrange to boot to console mode rather than X. With >>> the ability to startx when I feel like it. >> The way I usually do it is to uninstall gdm, kdm, xdm, et cetera; >> those are the packages which hook in to provide a graphical login >> prompt. With none of them present, what you get is the traditional >> text-mode login prompt, and your configured shell after login. > > That sounds promissing. Used one of the methods below and quickly > realized I was expecting a nice big framebuffered text console with > a much higher resolution than the standard. (Previously my OS of > choice was gentoo), But of course all that has to be setup as I > recall it is done with a few extra bits on the kernel line > grub.conf > > Using grub2 I'm thoroughly lost what or where one would edit to > allow a console frame buffer. AFAIK, the GRUB2 menu is defined from /boot/grub/grub.cfg; the headers of that file say that it's generated from templates in /etc/grub.d/ and settings in /etc/default/grub. Based on a quick look in those locations, you probably want to adjust one of the GRUB_CMDLINE_LINUX* settings in the latter file. I haven't done much tweaking in that area myself, however (I only migrated to GRUB2 within the last year, give or take), so I can't confirm that with any certainty. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: How to arrange for booting to console
The Wanderer writes: > On 2016-09-11 at 17:04, Harry Putnam wrote: > >> How can I arrange to boot to console mode rather than X. With the >> ability to startx when I feel like it. >> [...] > The way I usually do it is to uninstall gdm, kdm, xdm, et cetera; those > are the packages which hook in to provide a graphical login prompt. With > none of them present, what you get is the traditional text-mode login > prompt, and your configured shell after login. > [...] That sounds promissing. Used one of the methods below and quickly realized I was expecting a nice big framebuffered text console with a much higher resolution than the standard. (Previously my OS of choice was gentoo), But of course all that has to be setup as I recall it is done with a few extra bits on the kernel line grub.conf Using grub2 I'm thoroughly lost what or where one would edit to allow a console frame buffer. Michael Biebl wrote: > Assuming you use jessie (and systemd), > > systemctl set-default multi-user.target > > should do the trick. You can get the current default with > > systemctl get-default > > It's typically graphical.target. Thanks, I actually used your suggestion of systemctl set-default multi-user.target Worked just as suggested. I have the job running that was running out of memory.. so I'll see if leaving X out of things is enough to allow it to complete. See above for some sniveling about the default console. david...@freevolt.org writes: > If using systemd, these look relevant: > >> How can I arrange to boot to console mode rather than X. > > > https://www.freedesktop.org/wiki/Software/systemd/TipsAndTricks/#changingthedefaultboottarget > > # ln -sf /usr/lib/systemd/system/multi-user.target > /etc/systemd/system/default.target > >> With the ability to startx when I feel like it. > > https://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions > > # systemctl isolate graphical.target Thanks, your suggestion is a little more complete version of Davidson above again thanks.
Fwd: How to get Jessie to run at boot time -- Problem solved
I tried to send this only to Brian, but he has set his system to not accept messages to him. So I have to send this to the whole List. Sorry. - Forwarded Message - From: "Alan McConnell" To: "Brian" Sent: Sunday, September 11, 2016 3:38:06 PM Subject: Re: How to get Jessie to run at boot time -- Problem solved This only to you, Brian. - Original Message - From: "Brian" To: debian-user@lists.debian.org Sent: Sunday, September 11, 2016 2:51:50 PM Subject: 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? > Windows 10. If there is a more exact name, I don't know it. Deconstruction of this statement follows: Brian, you are in a bad temper. Did you read the amended title of this and previous messages? "Problem solved". Suggestion: simply don't reply to any of my (perhaps) forthcoming questions and/or comments. That will save both you and me time and spare us both annoyance. Best wishes, Alan McConnell
Re: How to arrange for booting to console
If using systemd, these look relevant: How can I arrange to boot to console mode rather than X. https://www.freedesktop.org/wiki/Software/systemd/TipsAndTricks/#changingthedefaultboottarget # ln -sf /usr/lib/systemd/system/multi-user.target /etc/systemd/system/default.target With the ability to startx when I feel like it. https://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions # systemctl isolate graphical.target
Re: How to arrange for booting to console
Am 11.09.2016 um 23:04 schrieb Harry Putnam: > How can I arrange to boot to console mode rather than X. With the > ability to startx when I feel like it. > > I'm not familiar with grub2 and the debian vm I'm using on a solaris > host appears to be using grub2. > > Can anyone stear me to the files I'd need to edit? > Assuming you use jessie (and systemd), systemctl set-default multi-user.target should do the trick. You can get the current default with systemctl get-default It's typically graphical.target. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: How to arrange for booting to console
On 2016-09-11 at 17:04, Harry Putnam wrote: > How can I arrange to boot to console mode rather than X. With the > ability to startx when I feel like it. > > I'm not familiar with grub2 and the debian vm I'm using on a solaris > host appears to be using grub2. > > Can anyone stear me to the files I'd need to edit? Unless you actually want to be able to get to the graphical login prompt, I don't believe you need to mess with GRUB, the bootloader, or the initrd at all. The way I usually do it is to uninstall gdm, kdm, xdm, et cetera; those are the packages which hook in to provide a graphical login prompt. With none of them present, what you get is the traditional text-mode login prompt, and your configured shell after login. From there, assuming other permissions are configured correctly (which I seem to recall may take some tweaking, under the systemd paradigm), 'startx' should work normally. It may or may not pick up your desired window manager; I believe the Debian Way to specify that is to select one as the preferred alternative for the 'x-window-manager' link group. If you do want to keep one or more of those packages present, or if you want to do this more explicitly / manually, you'll probably need to look at those packages and figure out what it is they do to hook themselves in as the login prompt. I haven't investigated exactly what they change in order to do that, so I can't directly help you there. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
How to arrange for booting to console
How can I arrange to boot to console mode rather than X. With the ability to startx when I feel like it. I'm not familiar with grub2 and the debian vm I'm using on a solaris host appears to be using grub2. Can anyone stear me to the files I'd need to edit?
Re: [resolved] FireFox broken,
I was amazed a couple days ago, I switched my default browser to chromium, more for S&G than any other reason, as its now quite long in the tooth. I had to go thru an email driven procedure to verify the pw at PP, but then it worked. And its kept on working... And I've been using it for my daily dose of fake news from the mainsleaze news sites, and except for cbsnews.com, nearly every video plays AND stays in lip synch. I can now buy something online, and it works again. I think I'll leave it that way for a while. :-) Firefox is still busted. Cheers, Gene Heskett Agreed. I believed our problems were related, and I still do. I have run into other problems since I installed libnss3 from sid, problems that I haven't had time to relate here on debian-user up to now. For instance, I couldn't verify my email with a certain site using Firefox, the site simply said email not verified. (You know, how they send you an email, and you click on a link.) I copied the link address to Google Chrome, and it worked, first try. There are a number of examples like this that I won't bother to enumerate, because they are incidental. The problems surfaced with an update to firefox, that's why I blame Firefox. I think now that Gene's problems won't all be cured by installing a recent libnss3. Some people blame the age of Gene's system, but I am running stretch, and I have run into the same problems (plural). You can blame my problems on my running Testing, but it's funny that both of us on two completely different systmes starting having trouble with the same update to Firefox/Iceweasel. MArk Allums
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? > 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 > >for each package > > 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?
Re: How to get Jessie to run at boot time -- Problem solved
- Original Message - From: "Brian" 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? 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 for each package 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
Re: mount problems Please Help! Can't sshfs mount remote debian server, mount local 2nd hdd, nothing...
On Sonntag, 11. September 2016 11:43:17 PYT Tony Baldwin wrote: > On 09/11/2016 08:59 AM, Eike Lantzsch wrote: > > On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote: > >> On 09/11/2016 06:37 AM, Anthony Baldwin wrote: > >>> On 09/10/2016 07:57 PM, Anthony Baldwin wrote: > On 09/10/2016 03:34 PM, Anthony Baldwin wrote: > > On 09/10/2016 03:28 PM, Tony Baldwin wrote: > >> On 09/10/2016 03:07 PM, Nicolas George wrote: > >>> Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit : > I apologize, but, I've never quite figured out what to do with > dmesg, > or what to look for in its output, etc.. > it really just confuses me... > I saw this: 15.690807] EXT3-fs (sda1): warning: checktime reached, > running > e2fsck is recommended > [ 15.722318] EXT3-fs (sda1): using internal journal > >>> > >>> Looking for places that talk about the device causing problems would > >>> be a > >>> good start. Your problems are on /dev/sdb, so why do you bother with > >>> lines > >>> about /dev/sda? > >>> > and tried to e2fsk /dev/sdb2 > >>> > >>> And yet again you did not read part of my previous mail, the one > >>> about > >>> using > >>> Linux's fsck on microsoft's filesystems. > > > > I have no knowlege of what a windows equivalent to fsck would be. > > I hardly use that system. > > I only even installed it, because for a brief while I was doing some > > work for the State (I work freelance from home) that required windows > > only software (my contacts with the state didn't even know what > > gnu/linux is), and it had to be run on bare metal, not in a virtual > > environment. > > Thankfully, I am no longer doing that work. > > That system is so slow, stupid and crippled that it's maddening! > > I let windows do it's auto-repair thingy, and when I booted back to > Debian, things looked like maybe they were back to normal. I was able > to > do: > $ ls -li > total 12 > 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown > 1357617 drwxr-xr-x 2 root root 4096 Jul 10 2015 win7 > 1357619 drwxr-xr-x 2 root root 4096 Jul 10 2015 winhome > > Then I tried do mount them again, and got the I/O error, > and they're back to doing this: > $ ls -li > ls: cannot access winhome: Input/output error > ls: cannot access win7: Input/output error > total 4 > 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown > > ? d? ? ?? ?? win7 > ? d? ? ?? ?? winhome > > I don't get it... > >>> > >>> This can't have anything to do with "the microsoft version of fsck", > >>> because the windows disk (which is actually split into two partitions, > >>> one with the win7 system, and one that's just storage) is running fine > >>> when I boot it (for a crippled OS, anyway), and mounting the storage > >>> partition fine, too. > >>> PLus, I'm having trouble sshfs mounting a remote server running Debian, > >>> which worked fine days ago, now when I try it I get the same I/O errors, > >>> and wierd inode issues I'm getting with this local hdd. > >> > >> To confirm. > >> I booted back to windows and did a chkdsk (I'm assuming this is the > >> nearest thing to a Windows approximation of fsck) for both C:// (the > >> win7 system and /dev/sdb2) and D:// (storage, /dev/sdb3), and still > >> cannot mount either partition on this drive when I come back to my > >> Debian system. > >> The disk itself is fine, the problem is with the debian system somewhere. > >> Oh, and I have been able to sshfs mount my remote server again, btw > >> > >> ]$ dmesg | grep sdb > >> [3.098300] sd 5:0:0:0: [sdb] 2930277168 512-byte logical blocks: > >> (1.50 TB/1.36 TiB) > >> [3.098341] sd 5:0:0:0: [sdb] Write Protect is off > >> [3.098343] sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00 > >> [3.098360] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: > >> enabled, doesn't support DPO or FUA > >> [3.132979] sdb: sdb1 sdb2 sdb3 > >> [3.133999] sd 5:0:0:0: [sdb] Attached SCSI disk > >> > ./Tony > > > > sorry should have read: > > df -h *and* df -hi > > neither seems to indicate any problem: > ]$ df -h > Filesystem Size Used Avail Use% Mounted on > /dev/sda128G 16G 11G 61% / > udev 10M 0 10M 0% /dev > tmpfs 3.2G 9.4M 3.2G 1% /run > tmpfs 7.9G 23M 7.9G 1% /dev/shm > tmpfs 5.0M 4.0K 5.0M 1% /run/lock > tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup > /dev/sda6 1.3T 589G 663G 48% /home > tmpfs 1.6G 8.0K 1.6G 1% /run/user/1000 > [504][tony.deathstar: /home/tony]$ df -hi > Filesystem Inodes IUsed IFree IUse% Mounted on > /dev/sda11.8M 514K 1.3M 29%
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 for each package 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.
Re: Installing a MINIMAL Mate Desktop How?
On Sun 11 Sep 2016 at 10:04:06 -0500, Richard Owlett wrote: > While waiting for response(s) to my my post I installed marco, xorg, xterm, > mate-terminal, mate-panel, mate-session-manager and lightdm. > > I now have a workable, if ugly *MINIMAL* install. ;) > Now to find some decorative elements and chose the applications I want. The meaning of "minimal" is very difficult to define as it very much depends on the purpose of the install, what functionality is required, how it is to be used now and in the future and who it is to be used by. If I were doing what you are doing I wouldn't install xorg because it would take some 213 MB of space on this machine without the recommended packages. Instead (without recommended packages) I'd have xserver-org, xserver-org-input-evdev and xserver-xorg-video-nouveau for 15 MB of disk space. I doubt much (if anything) is lost by taking that route to X. Adding xterm to my basic X install is 3 MB of space extra. mate-terminal is 105 MB, so it is no contest if space taken is a major criterion. You could see less ugliness in mate-terminal so there is little point in arguing about what is minimal. lightdm looks nice and only adds an extra 2 MB. nodm adds hardly anything. Is a fancy DM necessary? I'd use mc instead of marco but wouldn't give it to a user who expects clickety-click things and automounting. Do you see what I am getting at? It could be said that minimal (like beauty) is in the eye of the beholder. -- Brian.
Systemd problem regarding resource control
Hi Debian users :) Well i'm back again with another problem i absolutely can't figure out. First of some information regarding my system and systemd: mo@srv:~$ systemd --version systemd 215 +PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR mo@srv:~$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux 8.5 (jessie) Release:8.5 Codename: jessie The problem is the following: According to the systemd.resource-control man page it is possible to manage the resources of slices, scopes, sockets and mount points. However, always when i try to set a property on one of my virtual machine slices the changes have no effect at all.. no matter what i try. The commands will be listed in order: $ sudo systemctl set-property --runtime machine-qemu"\x2d"ts.scope CPUQuota=10% No reply or error returned, so we should be good, then i type: $ systemctl show machine-qemu\x2dts.scope | grep CPU CPUAccounting=yes CPUShares=18446744073709551615 StartupCPUShares=18446744073709551615 CPUQuotaPerSecUSec=(null) As you can see CPUQutoa is _not_ listed here... which is quite strange to me. (Since systemctl did not return any error of any kind) The vm runs under the user "libvirt-qemu" and is started by hand via virsh. I honestly can't tell what seems to be wrong. It would be great if any of you guys has a idea what the reason could be. Thanks in advance :) Greets mo
Re: Installing a MINIMAL Mate Desktop How?
On 9/11/2016 11:46 AM, Curt wrote: On 2016-09-11, Richard Owlett wrote: "apt-get install mate-desktop-environment-core" does not install marco, xorg, xterm, nor lightdm. My brute force diagnostic procedure was to install each of them in the order listed with a reboot in between to see if everything worked. It did not. After installing each of the 1st three I was left at the command line. After installing lightdm I was presented with a blank screen. Well installing xorg without a display manager (lightdm in your case) would take you to the console, from where you'd have to issue a "startx" to get into the graphical environment I do believe. Rebooting each time seems like a waste of time, unless you can explain what magical spell that is supposed to cast upon the whole affair. Only as a reproducible test to see if I had installed all the right pieces ;) After installing lightdm you get a blank screen, so you're making progress (perhaps a graphic card/driver issue lurking in there somewhere). I was reporting sucess as you were writing. Futher experiments await purchasing DVD's of the upcoming point release. As I have minimal bandwidth available I am installing from purchased DVD's - currently version 8.0.0 . After the point release later this month I will obtain the latest. Has anyone successfully done such a minimal install as I am attempting? TIA
Re: Installing a MINIMAL Mate Desktop How?
On 2016-09-11, Richard Owlett wrote: > > "apt-get install mate-desktop-environment-core" does not install > marco, xorg, xterm, nor lightdm. My brute force diagnostic > procedure was to install each of them in the order listed with a > reboot in between to see if everything worked. It did not. After > installing each of the 1st three I was left at the command line. > After installing lightdm I was presented with a blank screen. Well installing xorg without a display manager (lightdm in your case) would take you to the console, from where you'd have to issue a "startx" to get into the graphical environment I do believe. Rebooting each time seems like a waste of time, unless you can explain what magical spell that is supposed to cast upon the whole affair. After installing lightdm you get a blank screen, so you're making progress (perhaps a graphic card/driver issue lurking in there somewhere). > As I have minimal bandwidth available I am installing from > purchased DVD's - currently version 8.0.0 . After the point > release later this month I will obtain the latest. > > Has anyone successfully done such a minimal install as I am > attempting? > TIA > > > -- “Whatever is rejected from the self, appears in the world as an event.” C.G. Jung
Re: Installing a MINIMAL Mate Desktop How?
On 9/11/2016 10:04 AM, Richard Owlett wrote: On 9/11/2016 9:14 AM, Brian wrote: [snip] "apt-get install mate-desktop-environment-core" does not install marco, xorg, xterm, nor lightdm. My brute force diagnostic procedure was to install each of them in the order listed with a reboot in between to see if everything worked. It did not. After installing each of the 1st three I was left at the command line. After installing lightdm I was presented with a blank screen. mate-desktop-environment-core depends on marco. There is something seriously wrong if it was not installed. Huumm I see another test install in my future as it is listed as such in the packages file for the DVD I installed from. Something is definitely *FLAKY* at least. I just did another test install on another partition. This time I only had to install xorg, xterm, and lightdm after installing mate-desktop-environment-core. This time it even has the same visual appearance as the full Mate install on the same machine. As Debian 8.6 is due soon, I'll wait until then and copy the DVD's to a flash drive and do an install from them. In the meantime I'll create an appropriate preseed.cfg to aid repeatably to my trials.
Re: mount problems Please Help! Can't sshfs mount remote debian server, mount local 2nd hdd, nothing...
On 09/11/2016 08:59 AM, Eike Lantzsch wrote: On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote: On 09/11/2016 06:37 AM, Anthony Baldwin wrote: On 09/10/2016 07:57 PM, Anthony Baldwin wrote: On 09/10/2016 03:34 PM, Anthony Baldwin wrote: On 09/10/2016 03:28 PM, Tony Baldwin wrote: On 09/10/2016 03:07 PM, Nicolas George wrote: Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit : I apologize, but, I've never quite figured out what to do with dmesg, or what to look for in its output, etc.. it really just confuses me... I saw this: 15.690807] EXT3-fs (sda1): warning: checktime reached, running e2fsck is recommended [ 15.722318] EXT3-fs (sda1): using internal journal Looking for places that talk about the device causing problems would be a good start. Your problems are on /dev/sdb, so why do you bother with lines about /dev/sda? and tried to e2fsk /dev/sdb2 And yet again you did not read part of my previous mail, the one about using Linux's fsck on microsoft's filesystems. I have no knowlege of what a windows equivalent to fsck would be. I hardly use that system. I only even installed it, because for a brief while I was doing some work for the State (I work freelance from home) that required windows only software (my contacts with the state didn't even know what gnu/linux is), and it had to be run on bare metal, not in a virtual environment. Thankfully, I am no longer doing that work. That system is so slow, stupid and crippled that it's maddening! I let windows do it's auto-repair thingy, and when I booted back to Debian, things looked like maybe they were back to normal. I was able to do: $ ls -li total 12 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown 1357617 drwxr-xr-x 2 root root 4096 Jul 10 2015 win7 1357619 drwxr-xr-x 2 root root 4096 Jul 10 2015 winhome Then I tried do mount them again, and got the I/O error, and they're back to doing this: $ ls -li ls: cannot access winhome: Input/output error ls: cannot access win7: Input/output error total 4 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown ? d? ? ?? ?? win7 ? d? ? ?? ?? winhome I don't get it... This can't have anything to do with "the microsoft version of fsck", because the windows disk (which is actually split into two partitions, one with the win7 system, and one that's just storage) is running fine when I boot it (for a crippled OS, anyway), and mounting the storage partition fine, too. PLus, I'm having trouble sshfs mounting a remote server running Debian, which worked fine days ago, now when I try it I get the same I/O errors, and wierd inode issues I'm getting with this local hdd. To confirm. I booted back to windows and did a chkdsk (I'm assuming this is the nearest thing to a Windows approximation of fsck) for both C:// (the win7 system and /dev/sdb2) and D:// (storage, /dev/sdb3), and still cannot mount either partition on this drive when I come back to my Debian system. The disk itself is fine, the problem is with the debian system somewhere. Oh, and I have been able to sshfs mount my remote server again, btw ]$ dmesg | grep sdb [3.098300] sd 5:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) [3.098341] sd 5:0:0:0: [sdb] Write Protect is off [3.098343] sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [3.098360] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.132979] sdb: sdb1 sdb2 sdb3 [3.133999] sd 5:0:0:0: [sdb] Attached SCSI disk ./Tony sorry should have read: df -h *and* df -hi neither seems to indicate any problem: ]$ df -h Filesystem Size Used Avail Use% Mounted on /dev/sda128G 16G 11G 61% / udev 10M 0 10M 0% /dev tmpfs 3.2G 9.4M 3.2G 1% /run tmpfs 7.9G 23M 7.9G 1% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup /dev/sda6 1.3T 589G 663G 48% /home tmpfs 1.6G 8.0K 1.6G 1% /run/user/1000 [504][tony.deathstar: /home/tony]$ df -hi Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sda11.8M 514K 1.3M 29% / udev 2.0M 453 2.0M1% /dev tmpfs2.0M 776 2.0M1% /run tmpfs2.0M33 2.0M1% /dev/shm tmpfs2.0M 5 2.0M1% /run/lock tmpfs2.0M11 2.0M1% /sys/fs/cgroup /dev/sda6 84M 1.2M 83M2% /home tmpfs2.0M15 2.0M1% /run/user/1000 I was able to load a Trisquel mini liveCD up and mount that hdd from that system, and recover some of the most important stuff by rsyncing it back to the hdd my Jessie is on. Still, I'd like to understand and amend the problem and be able to mount this disk like I used to on the Jessie system. Since both Windows and Trisquel can mount and access is, the problem must be somewhere here in Jessie... But I h
Re: Using the result of equivs (dummy package for dependencies)
On 2016-09-11 at 11:13, Mark Fletcher wrote: > So I've used the equivs-control and equivs-build commands from the > equivs package to create a dummy package which has all the needed > dependencies. My problem is I can't do anything with the created > package -- I obviously can't dpkg -i it because dpkg just complains > about the missing dependencies -- which was the point of creating the > dummy package in the first place! > > Is there a way I can get aptitude to add this package to its > knowledge base, and then let me install it as if it came from a > debian repository? You almost certainly want one or more of dpkg's '--force' options. As a first attempt, try 'dpkg -i pkgname.deb --force-depends', or similar. If that doesn't work, look through that section of the man page and see what else you may find. After it's installed, 'apt-get -f install' (or a comparable aptitude command) should get you the missing dependencies, as intended. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: How to get Jessie to run at boot time -- Problem solved
- Original Message - From: "Felix Miata" 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
Using the result of equivs (dummy package for dependencies)
Hello the list! I am trying to install an open-source submarine simulation game called Danger From The Deep onto Jessie. The game is not packaged for Debian, although an old version is packaged for Ubuntu, I've just noticed. The game has recently seen a lot of developer activity after a long pause, and I want to try out the latest bells and whistles. So I've cloned the git repository of the source code and am all set to build the game from source. Some years ago I did this and got the game to work, but made a bit of a mess of my installed packages in the process. Specifically, the game needs a bunch of OpenGL, SDL etc libraries and their -dev equivalents. Many of the libraries themselves were already installed but the -dev equivalents weren't. Last time, I installed them using aptitude install, which was fine until it came time to upgrade, either from wheezy to jessie or from squeeze to wheezy, I forget which... Anyway, that upgrade replaced many of the libraries not with newer versions, but with new library packages altogether which conflicted with the old ones. Because the dev libraries were explicitly installed, and not automatically installed, aptitude couldn't see that it could actually remove them, and so it was desperately trying to come up with a solution and ended up wanting to completely remove Gnome (not a terrible idea, some might argue :) ). I got out of the mess by using aptitude markauto on the -dev packages and then aptitude was able to figure out that it could remove them, and hence what to do to resolve the dependencies. So, this time, I want to avoid that, and I had the idea to create a dummy package that has all the dependencies that Danger From The Deep needs. Then, I can install that package and have aptitude install the missing dependencies and mark them as auto-installed. Then, if I get into a future similar upgrade situation, aptitude will be able to see it can resolve the dependencies by removing the Danger From The Deep package, not ripping out half my system. Also if I go off Danger From the Deep I can remove the package and have aptitude remove all the dependencies that were only there for it -- keep things tidy. So I've used the equivs-control and equivs-build commands from the equivs package to create a dummy package which has all the needed dependencies. My problem is I can't do anything with the created package -- I obviously can't dpkg -i it because dpkg just complains about the missing dependencies -- which was the point of creating the dummy package in the first place! Is there a way I can get aptitude to add this package to its knowledge base, and then let me install it as if it came from a debian repository? (Its sole purpose is to reflect the dependency on the required libraries so they are installed and marked as auto-installed, and not immediately removed as long as the dummy package is in place) Do I have to set up a local repository? If so, any pointers to references on doing that? But, better, can that be avoided? Is there a simpler way? A lot of the info on the web says create your package with equivs-build then install it with dpkg -i -- which I can't do as described above. (I'm an aptitude man but apt-get based solutions also entirely acceptable!) Thanks in advance! Mark
Re: Installing a MINIMAL Mate Desktop How?
On 9/11/2016 9:14 AM, Brian wrote: On Sun 11 Sep 2016 at 06:47:23 -0500, Richard Owlett wrote: When Squeeze was the latest I was able to install without any desktop. I would then do apt-get install gnome-session gdm3 gedit gnome-terminal gparted The result was a nice uncluttered desktop to which I could add what *I* needed rather than what the proverbial "everybody" should have ;) gnome-session pulls in xserver-org-video-all and installs it on the *same* machine. Graphical programs like gnome-terminal and gedit run on the *same* machine as the X server runs on and will display an output there. This is a very common situation but it does not have to be like that. An X server runs and produces an output on the machine you are sitting in front of. Programs like gedit could be on a *different* machine. This is just as valid a setup as the "common" one. It implies that such things as, for example, window manager packages do not depend on an X server being installed. I think I follow the point you are trying to make. Just to be clear, everything *I* do is on a standalone machine [a laptop]. According to http://wiki.mate-desktop.org/download#debian I should be able to do apt-get install mate-desktop-environment-core That is not enough, it leaves me with only a command line. You got what was promised - a minimal mate install. You need an X server on that machine or another one if you want other than the command line. Whether or not it qualifies as an "install" or not is a matter of definition/perspective. A few years ago I thinking about a possible Debian Pure Blend aimed at the bandwidth challenged - at the time I was on dialup. Someone suggested "Desert Island Swirl" as a working title. That would fit my perspective on how an installer should interact with a user. The user could be described as one person, with one computer and one stack of DVD's. I have the full Mate desktop on one machine. Using Synaptic on that machine and using apt-get install on the other I was able too identify some missing pieces. "apt-get install mate-desktop-environment-core" does not install marco, xorg, xterm, nor lightdm. My brute force diagnostic procedure was to install each of them in the order listed with a reboot in between to see if everything worked. It did not. After installing each of the 1st three I was left at the command line. After installing lightdm I was presented with a blank screen. mate-desktop-environment-core depends on marco. There is something seriously wrong if it was not installed. Huumm I see another test install in my future as it is listed as such in the packages file for the DVD I installed from. xorg isn't required to be on the same machine as mate; that is why it was not installed. mate-terminal does the same job as xterm. The mate maintainers might have decided not have a DM as a depended on or recommended package. While waiting for response(s) to my my post I installed marco, xorg, xterm, mate-terminal, mate-panel, mate-session-manager and lightdm. I now have a workable, if ugly *MINIMAL* install. ;) Now to find some decorative elements and chose the applications I want.
Re: mount problems Please Help! Can't sshfs mount remote debian server, mount local 2nd hdd, nothing...
On Sonntag, 11. September 2016 09:17:41 PYT Anthony Baldwin wrote: > On 09/11/2016 08:54 AM, Eike Lantzsch wrote: > > On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote: > >> On 09/11/2016 06:37 AM, Anthony Baldwin wrote: > >>> On 09/10/2016 07:57 PM, Anthony Baldwin wrote: > On 09/10/2016 03:34 PM, Anthony Baldwin wrote: > > On 09/10/2016 03:28 PM, Tony Baldwin wrote: > >> On 09/10/2016 03:07 PM, Nicolas George wrote: > >>> Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit : > I apologize, but, I've never quite figured out what to do with > dmesg, > or what to look for in its output, etc.. > it really just confuses me... > I saw this: 15.690807] EXT3-fs (sda1): warning: checktime reached, > running > e2fsck is recommended > [ 15.722318] EXT3-fs (sda1): using internal journal > >>> > >>> Looking for places that talk about the device causing problems would > >>> be a > >>> good start. Your problems are on /dev/sdb, so why do you bother with > >>> lines > >>> about /dev/sda? > >>> > and tried to e2fsk /dev/sdb2 > >>> > >>> And yet again you did not read part of my previous mail, the one > >>> about > >>> using > >>> Linux's fsck on microsoft's filesystems. > > > > I have no knowlege of what a windows equivalent to fsck would be. > > I hardly use that system. > > I only even installed it, because for a brief while I was doing some > > work for the State (I work freelance from home) that required windows > > only software (my contacts with the state didn't even know what > > gnu/linux is), and it had to be run on bare metal, not in a virtual > > environment. > > Thankfully, I am no longer doing that work. > > That system is so slow, stupid and crippled that it's maddening! > > I let windows do it's auto-repair thingy, and when I booted back to > Debian, things looked like maybe they were back to normal. I was able > to > do: > $ ls -li > total 12 > 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown > 1357617 drwxr-xr-x 2 root root 4096 Jul 10 2015 win7 > 1357619 drwxr-xr-x 2 root root 4096 Jul 10 2015 winhome > > Then I tried do mount them again, and got the I/O error, > and they're back to doing this: > $ ls -li > ls: cannot access winhome: Input/output error > ls: cannot access win7: Input/output error > total 4 > 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown > > ? d? ? ?? ?? win7 > ? d? ? ?? ?? winhome > > I don't get it... > >>> > >>> This can't have anything to do with "the microsoft version of fsck", > >>> because the windows disk (which is actually split into two partitions, > >>> one with the win7 system, and one that's just storage) is running fine > >>> when I boot it (for a crippled OS, anyway), and mounting the storage > >>> partition fine, too. > >>> PLus, I'm having trouble sshfs mounting a remote server running Debian, > >>> which worked fine days ago, now when I try it I get the same I/O errors, > >>> and wierd inode issues I'm getting with this local hdd. > >> > >> To confirm. > >> I booted back to windows and did a chkdsk (I'm assuming this is the > >> nearest thing to a Windows approximation of fsck) for both C:// (the > >> win7 system and /dev/sdb2) and D:// (storage, /dev/sdb3), and still > >> cannot mount either partition on this drive when I come back to my > >> Debian system. > >> The disk itself is fine, the problem is with the debian system somewhere. > >> Oh, and I have been able to sshfs mount my remote server again, btw > >> > >> ]$ dmesg | grep sdb > >> [3.098300] sd 5:0:0:0: [sdb] 2930277168 512-byte logical blocks: > >> (1.50 TB/1.36 TiB) > >> [3.098341] sd 5:0:0:0: [sdb] Write Protect is off > >> [3.098343] sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00 > >> [3.098360] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: > >> enabled, doesn't support DPO or FUA > >> [3.132979] sdb: sdb1 sdb2 sdb3 > >> [3.133999] sd 5:0:0:0: [sdb] Attached SCSI disk > >> > ./Tony > > > > The problem seems to be your system and not the mounted disks with NTFS or > > any remote shares. > > That's what I'd been trying to say. > > > shot into the dark: > > might be that your root partition is full or ran out of inodes? > > df -hi > > > > also start your system using a live cd, e.g. knoppix > > > > [boot with "knoppix 2" to use only command line] and "fsck /dev/sdxn" > > where x> > > is the letter of the hard disk where your system resides and n is the > > number of the pertinent partition(s). > > I had gparted try to check/repair that disk (not mounted anyway, so why > not?), which failed. > I have posted the output here: > http://tonybaldwin.me/f
Re: Installing a MINIMAL Mate Desktop How?
On Sun 11 Sep 2016 at 06:47:23 -0500, Richard Owlett wrote: > When Squeeze was the latest I was able to install without any desktop. > I would then do >apt-get install gnome-session gdm3 gedit gnome-terminal gparted > The result was a nice uncluttered desktop to which I could add what *I* > needed rather than what the proverbial "everybody" should have ;) gnome-session pulls in xserver-org-video-all and installs it on the *same* machine. Graphical programs like gnome-terminal and gedit run on the *same* machine as the X server runs on and will display an output there. This is a very common situation but it does not have to be like that. An X server runs and produces an output on the machine you are sitting in front of. Programs like gedit could be on a *different* machine. This is just as valid a setup as the "common" one. It implies that such things as, for example, window manager packages do not depend on an X server being installed. > According to http://wiki.mate-desktop.org/download#debian I should be able > to do >apt-get install mate-desktop-environment-core > > That is not enough, it leaves me with only a command line. You got what was promised - a minimal mate install. You need an X server on that machine or another one if you want other than the command line. > I have the full Mate desktop on one machine. Using Synaptic on that machine > and using apt-get install on the other I was able too identify some > missing pieces. > > "apt-get install mate-desktop-environment-core" does not install marco, > xorg, xterm, nor lightdm. My brute force diagnostic procedure was to install > each of them in the order listed with a reboot in between to see if > everything worked. It did not. After installing each of the 1st three I was > left at the command line. After installing lightdm I was presented with a > blank screen. mate-desktop-environment-core depends on marco. There is something seriously wrong if it was not installed. xorg isn't required to be on the same machine as mate; that is why it was not installed. mate-terminal does the same job as xterm. The mate maintainers might have decided not have a DM as a depended on or recommended package. -- Brian.
Re: Jessie & Fixed IP Address_Solved
On Fri, 2016-09-09 at 09:40 +0100, Joe wrote: > On Fri, 09 Sep 2016 09:12:14 +0100 > David wrote: > > > > > > > > Firstly an apology, I did not realise there was a Debian Jessie and > > a > > Raspbian Jessie. > > > > I'm working with Raspbian Jessie. > > > > Debian is the root of many other distributions such as Knoppix and > Ubuntu, and many less famous. > > Raspbian is one that rings bells because it is based on the ARM, > which > probably no full-sized computer is these days (the Acorn Archimedes > series used it almost thirty years ago). The range of Debian packages > ported to the ARM RISC architecture is significantly smaller than > those > for i386 and amd64, so some things have to be done differently. The > limitations of the system-on-chip which composes almost all of the Pi > hardware imposes further limitations, compared to general-purpose > desktop hardware or even laptop hardware. The relatively small > storage > space available again imposes restrictions. > > So Raspbian may well be quite different to a stock amd64 Jessie, > utilising many of the tricks of older days of computing to make the > best of limited hardware. > Many thanks to all those that replied. The problem was that the person who created the SD card for the Pi did a few odd things, hence some things did not work. One was reading the DNS server settings when in fixed IP mode, resolv.conf was empty. Putting the Pi back into DHCP mode caused a whole multitude of problems. The thing learnt here is to wipe the SD card clean, I use GPARTED, then write the image to the SD card, I use Susie Image Writer. Just to confirm Raspbian Jessie is working correctly with the instructions given previously to get it into fixed IP mode. David.
Re: mount problems Please Help! Can't sshfs mount remote debian server, mount local 2nd hdd, nothing...
On 09/11/2016 08:54 AM, Eike Lantzsch wrote: On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote: On 09/11/2016 06:37 AM, Anthony Baldwin wrote: On 09/10/2016 07:57 PM, Anthony Baldwin wrote: On 09/10/2016 03:34 PM, Anthony Baldwin wrote: On 09/10/2016 03:28 PM, Tony Baldwin wrote: On 09/10/2016 03:07 PM, Nicolas George wrote: Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit : I apologize, but, I've never quite figured out what to do with dmesg, or what to look for in its output, etc.. it really just confuses me... I saw this: 15.690807] EXT3-fs (sda1): warning: checktime reached, running e2fsck is recommended [ 15.722318] EXT3-fs (sda1): using internal journal Looking for places that talk about the device causing problems would be a good start. Your problems are on /dev/sdb, so why do you bother with lines about /dev/sda? and tried to e2fsk /dev/sdb2 And yet again you did not read part of my previous mail, the one about using Linux's fsck on microsoft's filesystems. I have no knowlege of what a windows equivalent to fsck would be. I hardly use that system. I only even installed it, because for a brief while I was doing some work for the State (I work freelance from home) that required windows only software (my contacts with the state didn't even know what gnu/linux is), and it had to be run on bare metal, not in a virtual environment. Thankfully, I am no longer doing that work. That system is so slow, stupid and crippled that it's maddening! I let windows do it's auto-repair thingy, and when I booted back to Debian, things looked like maybe they were back to normal. I was able to do: $ ls -li total 12 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown 1357617 drwxr-xr-x 2 root root 4096 Jul 10 2015 win7 1357619 drwxr-xr-x 2 root root 4096 Jul 10 2015 winhome Then I tried do mount them again, and got the I/O error, and they're back to doing this: $ ls -li ls: cannot access winhome: Input/output error ls: cannot access win7: Input/output error total 4 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown ? d? ? ?? ?? win7 ? d? ? ?? ?? winhome I don't get it... This can't have anything to do with "the microsoft version of fsck", because the windows disk (which is actually split into two partitions, one with the win7 system, and one that's just storage) is running fine when I boot it (for a crippled OS, anyway), and mounting the storage partition fine, too. PLus, I'm having trouble sshfs mounting a remote server running Debian, which worked fine days ago, now when I try it I get the same I/O errors, and wierd inode issues I'm getting with this local hdd. To confirm. I booted back to windows and did a chkdsk (I'm assuming this is the nearest thing to a Windows approximation of fsck) for both C:// (the win7 system and /dev/sdb2) and D:// (storage, /dev/sdb3), and still cannot mount either partition on this drive when I come back to my Debian system. The disk itself is fine, the problem is with the debian system somewhere. Oh, and I have been able to sshfs mount my remote server again, btw ]$ dmesg | grep sdb [3.098300] sd 5:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) [3.098341] sd 5:0:0:0: [sdb] Write Protect is off [3.098343] sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [3.098360] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.132979] sdb: sdb1 sdb2 sdb3 [3.133999] sd 5:0:0:0: [sdb] Attached SCSI disk ./Tony The problem seems to be your system and not the mounted disks with NTFS or any remote shares. That's what I'd been trying to say. shot into the dark: might be that your root partition is full or ran out of inodes? df -hi also start your system using a live cd, e.g. knoppix [boot with "knoppix 2" to use only command line] and "fsck /dev/sdxn" where x is the letter of the hard disk where your system resides and n is the number of the pertinent partition(s). I had gparted try to check/repair that disk (not mounted anyway, so why not?), which failed. I have posted the output here: http://tonybaldwin.me/files/gparted_details.htm is your /usr, /var and /tmp on the same partition than your root? Yes, my Debian system is all on one disk and one partition, even /home. hope that helps to analize the problem further Cheers Eike -- http://www.baldwinlinguas.com translations, localization, multilingual web development EN, ES, FR, PT
[Solved] Re: A few questions about cgroups in Debian 8 (Jessie)
Hello Debian users :) I have googled a little bit and came to the conclusion that cgroups should be managed with systemd. (Thanks to Nicolas George for the systemd hint :^) ) For anyone who is interested here is a good guide from RedHat about resource management with cgroups and systemd: PDF: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/pdf/Resource_Management_Guide/Red_Hat_Enterprise_Linux-7-Resource_Management_Guide-en-US.pdf Single page html: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Resource_Management_Guide/index.html Have a nice day guys ;) best regards mo
Re: mount problems Please Help! Can't sshfs mount remote debian server, mount local 2nd hdd, nothing...
On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote: > On 09/11/2016 06:37 AM, Anthony Baldwin wrote: > > On 09/10/2016 07:57 PM, Anthony Baldwin wrote: > >> On 09/10/2016 03:34 PM, Anthony Baldwin wrote: > >>> On 09/10/2016 03:28 PM, Tony Baldwin wrote: > On 09/10/2016 03:07 PM, Nicolas George wrote: > > Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit : > >> I apologize, but, I've never quite figured out what to do with dmesg, > >> or what to look for in its output, etc.. > >> it really just confuses me... > >> I saw this: 15.690807] EXT3-fs (sda1): warning: checktime reached, > >> running > >> e2fsck is recommended > >> [ 15.722318] EXT3-fs (sda1): using internal journal > > > > Looking for places that talk about the device causing problems would > > be a > > good start. Your problems are on /dev/sdb, so why do you bother with > > lines > > about /dev/sda? > > > >> and tried to e2fsk /dev/sdb2 > > > > And yet again you did not read part of my previous mail, the one about > > using > > Linux's fsck on microsoft's filesystems. > >>> > >>> I have no knowlege of what a windows equivalent to fsck would be. > >>> I hardly use that system. > >>> I only even installed it, because for a brief while I was doing some > >>> work for the State (I work freelance from home) that required windows > >>> only software (my contacts with the state didn't even know what > >>> gnu/linux is), and it had to be run on bare metal, not in a virtual > >>> environment. > >>> Thankfully, I am no longer doing that work. > >>> That system is so slow, stupid and crippled that it's maddening! > >> > >> I let windows do it's auto-repair thingy, and when I booted back to > >> Debian, things looked like maybe they were back to normal. I was able to > >> do: > >> $ ls -li > >> total 12 > >> 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown > >> 1357617 drwxr-xr-x 2 root root 4096 Jul 10 2015 win7 > >> 1357619 drwxr-xr-x 2 root root 4096 Jul 10 2015 winhome > >> > >> Then I tried do mount them again, and got the I/O error, > >> and they're back to doing this: > >> $ ls -li > >> ls: cannot access winhome: Input/output error > >> ls: cannot access win7: Input/output error > >> total 4 > >> 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown > >> > >> ? d? ? ?? ?? win7 > >> ? d? ? ?? ?? winhome > >> > >> I don't get it... > > > > This can't have anything to do with "the microsoft version of fsck", > > because the windows disk (which is actually split into two partitions, > > one with the win7 system, and one that's just storage) is running fine > > when I boot it (for a crippled OS, anyway), and mounting the storage > > partition fine, too. > > PLus, I'm having trouble sshfs mounting a remote server running Debian, > > which worked fine days ago, now when I try it I get the same I/O errors, > > and wierd inode issues I'm getting with this local hdd. > > To confirm. > I booted back to windows and did a chkdsk (I'm assuming this is the > nearest thing to a Windows approximation of fsck) for both C:// (the > win7 system and /dev/sdb2) and D:// (storage, /dev/sdb3), and still > cannot mount either partition on this drive when I come back to my > Debian system. > The disk itself is fine, the problem is with the debian system somewhere. > Oh, and I have been able to sshfs mount my remote server again, btw > > ]$ dmesg | grep sdb > [3.098300] sd 5:0:0:0: [sdb] 2930277168 512-byte logical blocks: > (1.50 TB/1.36 TiB) > [3.098341] sd 5:0:0:0: [sdb] Write Protect is off > [3.098343] sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00 > [3.098360] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: > enabled, doesn't support DPO or FUA > [3.132979] sdb: sdb1 sdb2 sdb3 > [3.133999] sd 5:0:0:0: [sdb] Attached SCSI disk > > >> ./Tony sorry should have read: df -h *and* df -hi
Re: mount problems Please Help! Can't sshfs mount remote debian server, mount local 2nd hdd, nothing...
On Sonntag, 11. September 2016 08:12:24 PYT Anthony Baldwin wrote: > On 09/11/2016 06:37 AM, Anthony Baldwin wrote: > > On 09/10/2016 07:57 PM, Anthony Baldwin wrote: > >> On 09/10/2016 03:34 PM, Anthony Baldwin wrote: > >>> On 09/10/2016 03:28 PM, Tony Baldwin wrote: > On 09/10/2016 03:07 PM, Nicolas George wrote: > > Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit : > >> I apologize, but, I've never quite figured out what to do with dmesg, > >> or what to look for in its output, etc.. > >> it really just confuses me... > >> I saw this: 15.690807] EXT3-fs (sda1): warning: checktime reached, > >> running > >> e2fsck is recommended > >> [ 15.722318] EXT3-fs (sda1): using internal journal > > > > Looking for places that talk about the device causing problems would > > be a > > good start. Your problems are on /dev/sdb, so why do you bother with > > lines > > about /dev/sda? > > > >> and tried to e2fsk /dev/sdb2 > > > > And yet again you did not read part of my previous mail, the one about > > using > > Linux's fsck on microsoft's filesystems. > >>> > >>> I have no knowlege of what a windows equivalent to fsck would be. > >>> I hardly use that system. > >>> I only even installed it, because for a brief while I was doing some > >>> work for the State (I work freelance from home) that required windows > >>> only software (my contacts with the state didn't even know what > >>> gnu/linux is), and it had to be run on bare metal, not in a virtual > >>> environment. > >>> Thankfully, I am no longer doing that work. > >>> That system is so slow, stupid and crippled that it's maddening! > >> > >> I let windows do it's auto-repair thingy, and when I booted back to > >> Debian, things looked like maybe they were back to normal. I was able to > >> do: > >> $ ls -li > >> total 12 > >> 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown > >> 1357617 drwxr-xr-x 2 root root 4096 Jul 10 2015 win7 > >> 1357619 drwxr-xr-x 2 root root 4096 Jul 10 2015 winhome > >> > >> Then I tried do mount them again, and got the I/O error, > >> and they're back to doing this: > >> $ ls -li > >> ls: cannot access winhome: Input/output error > >> ls: cannot access win7: Input/output error > >> total 4 > >> 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown > >> > >> ? d? ? ?? ?? win7 > >> ? d? ? ?? ?? winhome > >> > >> I don't get it... > > > > This can't have anything to do with "the microsoft version of fsck", > > because the windows disk (which is actually split into two partitions, > > one with the win7 system, and one that's just storage) is running fine > > when I boot it (for a crippled OS, anyway), and mounting the storage > > partition fine, too. > > PLus, I'm having trouble sshfs mounting a remote server running Debian, > > which worked fine days ago, now when I try it I get the same I/O errors, > > and wierd inode issues I'm getting with this local hdd. > > To confirm. > I booted back to windows and did a chkdsk (I'm assuming this is the > nearest thing to a Windows approximation of fsck) for both C:// (the > win7 system and /dev/sdb2) and D:// (storage, /dev/sdb3), and still > cannot mount either partition on this drive when I come back to my > Debian system. > The disk itself is fine, the problem is with the debian system somewhere. > Oh, and I have been able to sshfs mount my remote server again, btw > > ]$ dmesg | grep sdb > [3.098300] sd 5:0:0:0: [sdb] 2930277168 512-byte logical blocks: > (1.50 TB/1.36 TiB) > [3.098341] sd 5:0:0:0: [sdb] Write Protect is off > [3.098343] sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00 > [3.098360] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: > enabled, doesn't support DPO or FUA > [3.132979] sdb: sdb1 sdb2 sdb3 > [3.133999] sd 5:0:0:0: [sdb] Attached SCSI disk > > >> ./Tony The problem seems to be your system and not the mounted disks with NTFS or any remote shares. shot into the dark: might be that your root partition is full or ran out of inodes? df -hi also start your system using a live cd, e.g. knoppix [boot with "knoppix 2" to use only command line] and "fsck /dev/sdxn" where x is the letter of the hard disk where your system resides and n is the number of the pertinent partition(s). is your /usr, /var and /tmp on the same partition than your root? hope that helps to analize the problem further Cheers Eike -- Eike Lantzsch ZP6CGE
Re: mount problems Please Help! Can't sshfs mount remote debian server, mount local 2nd hdd, nothing...
On 09/11/2016 06:37 AM, Anthony Baldwin wrote: On 09/10/2016 07:57 PM, Anthony Baldwin wrote: On 09/10/2016 03:34 PM, Anthony Baldwin wrote: On 09/10/2016 03:28 PM, Tony Baldwin wrote: On 09/10/2016 03:07 PM, Nicolas George wrote: Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit : I apologize, but, I've never quite figured out what to do with dmesg, or what to look for in its output, etc.. it really just confuses me... I saw this: 15.690807] EXT3-fs (sda1): warning: checktime reached, running e2fsck is recommended [ 15.722318] EXT3-fs (sda1): using internal journal Looking for places that talk about the device causing problems would be a good start. Your problems are on /dev/sdb, so why do you bother with lines about /dev/sda? and tried to e2fsk /dev/sdb2 And yet again you did not read part of my previous mail, the one about using Linux's fsck on microsoft's filesystems. I have no knowlege of what a windows equivalent to fsck would be. I hardly use that system. I only even installed it, because for a brief while I was doing some work for the State (I work freelance from home) that required windows only software (my contacts with the state didn't even know what gnu/linux is), and it had to be run on bare metal, not in a virtual environment. Thankfully, I am no longer doing that work. That system is so slow, stupid and crippled that it's maddening! I let windows do it's auto-repair thingy, and when I booted back to Debian, things looked like maybe they were back to normal. I was able to do: $ ls -li total 12 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown 1357617 drwxr-xr-x 2 root root 4096 Jul 10 2015 win7 1357619 drwxr-xr-x 2 root root 4096 Jul 10 2015 winhome Then I tried do mount them again, and got the I/O error, and they're back to doing this: $ ls -li ls: cannot access winhome: Input/output error ls: cannot access win7: Input/output error total 4 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown ? d? ? ?? ?? win7 ? d? ? ?? ?? winhome I don't get it... This can't have anything to do with "the microsoft version of fsck", because the windows disk (which is actually split into two partitions, one with the win7 system, and one that's just storage) is running fine when I boot it (for a crippled OS, anyway), and mounting the storage partition fine, too. PLus, I'm having trouble sshfs mounting a remote server running Debian, which worked fine days ago, now when I try it I get the same I/O errors, and wierd inode issues I'm getting with this local hdd. To confirm. I booted back to windows and did a chkdsk (I'm assuming this is the nearest thing to a Windows approximation of fsck) for both C:// (the win7 system and /dev/sdb2) and D:// (storage, /dev/sdb3), and still cannot mount either partition on this drive when I come back to my Debian system. The disk itself is fine, the problem is with the debian system somewhere. Oh, and I have been able to sshfs mount my remote server again, btw ]$ dmesg | grep sdb [3.098300] sd 5:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) [3.098341] sd 5:0:0:0: [sdb] Write Protect is off [3.098343] sd 5:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [3.098360] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.132979] sdb: sdb1 sdb2 sdb3 [3.133999] sd 5:0:0:0: [sdb] Attached SCSI disk ./Tony -- http://www.baldwinlinguas.com translations, localization, multilingual web development EN, ES, FR, PT
Re: Debian server for backups of Windows clients
Hi, Celejar On 09/09/16 18:18, Celejar wrote: My laptop has 802.11 a/b/g WiFi and Fast Ethernet. Wireless data transfers are slow (~50 Mbps). Wired is twice as fast (100 Mbps); still slow. Newer WiFi (n, ac) should be faster, but only the newest WiFi hardware can match or beat Gigabit. >>> You get ~50Mbps over a/b/g? 54Mbps is the theoretical maximum, and >>> everything I've read says that 20-24Mbps is the real-world maximum. >> Still, 20-24 Mbps is more than 10 Mpbs I was seeing with rsync. There >> could be a bottleneck somewhere? > As per your own suggestion in another message, definitely benchmark > with iperf to see if that's better. Yes, it can be. I was thinking about what I said in a previous message about the control information added by rsync on the packets sent. I think this would be important only if we focus on the performance (number of bits of data sent / total number of bits sent). In this case, the focus is the transfer rate, for which the amount of control bits used would be irrelevant since I think we need to know how many bits per second we are getting, regardless of the utility have those bits. > And as we discussed in another thread some time ago, (especially) if > you're using wireless, benchmark throughput in *both* directions, > since the transmitter (or receiver) may be better on one machine than > on another. Interesting sidelight. Thanks for sharing. Kind regards, Daniel signature.asc Description: OpenPGP digital signature
Re: Installing a MINIMAL Mate Desktop How?
Hi Richard I for one always make a minimal install, which means i only install the base. (You can select that in tasksel during the installation) From there on i build the system so to speak myself. Installing xorg and the needed video driver, the core package for my DE of choice (which currently is gnome) and then i install my display manager of choice (i use gdm atm). After that you either start gdm yourself by doing: # systemctl enable gdm && systemctl start gdm or you simply do a reboot... then you should be presented with your display manager of choice and you can login to your DE. About your problem with having to less applications installed with the core mate package: Have a look at the mate-desktop-environment meta package: https://packages.debian.org/jessie/mate-desktop-environment There you can see which applications get pulled in, you can select them yourself and then you can install the mate-desktop-environment-core package and add the software you need. I hope this helps you Best regards mo Am 11.09.2016 um 13:47 schrieb Richard Owlett: When Squeeze was the latest I was able to install without any desktop. I would then do apt-get install gnome-session gdm3 gedit gnome-terminal gparted The result was a nice uncluttered desktop to which I could add what *I* needed rather than what the proverbial "everybody" should have ;) According to http://wiki.mate-desktop.org/download#debian I should be able to do apt-get install mate-desktop-environment-core That is not enough, it leaves me with only a command line. I have the full Mate desktop on one machine. Using Synaptic on that machine and using apt-get install on the other I was able too identify some missing pieces. "apt-get install mate-desktop-environment-core" does not install marco, xorg, xterm, nor lightdm. My brute force diagnostic procedure was to install each of them in the order listed with a reboot in between to see if everything worked. It did not. After installing each of the 1st three I was left at the command line. After installing lightdm I was presented with a blank screen. As I have minimal bandwidth available I am installing from purchased DVD's - currently version 8.0.0 . After the point release later this month I will obtain the latest. Has anyone successfully done such a minimal install as I am attempting? TIA
Re: Debian server for backups of Windows clients
Hi, deloptes. On 09/09/16 19:06, deloptes wrote: >> Still, 20-24 Mbps is more than 10 Mpbs I was seeing with rsync. There >> could be a bottleneck somewhere? > In my case it was the IO on the disk - I couldn't do more than 12Mbps even > on wired connection, because I have encrypted disk ... it took me a while > to understand why though. This is an interesting fact. Because 'orion' (the notebook used in the mentioned test) also has an encrypted disk. In the test, the notebook was pulling the files on the Windows VM on the wired network. root@orion:~# dmsetup ls --target crypt sda5_crypt (254, 0) root@orion:~# cryptsetup luksDump /dev/sda5 | grep Version -A3 Version:1 Cipher name:aes Cipher mode:xts-plain64 Hash spec: sha1 viper@orion:~$ lsblk --fs NAME FSTYPE LABEL UUID MOUNTPOINT sda ├─sda1 /boot ├─sda2 └─sda5 └─sda5_crypt ├─main-swap[SWAP] ├─main-root/ └─main-datos /datos sr0 I did not think this could affect so strongly in the network transfer. Kind regards, Daniel signature.asc Description: OpenPGP digital signature
Re: Installing Lenny -- how to deal with expired repo signing keys?
On Sep 10, 2016, at 3:41 AM, Andrew M.A. Cater wrote: > > Download DVD1. Install a minimum system from it (if it has enough for you, > build the whole system). In fact, the netinst will work and produce a > _really_ minimal base system if you don't add a network mirror. > > Use apt-key add to add the expired keys if you must. > > Install whatever you need. > > At this point, I'd suggest doing this _only_ in a virtual machine to start > with > before doing this for real on the machine you intend to use long-term. > > Unless this is an absolutely "must do this on Lenny, nothing later will ever > work > and there's bespoke software that we must use and it must be on a real > physical > machine" it is probably worth moving this to a VM at some point / moving to a > later > version — given that Wheezy LTS expires in 2018 (that's current oldstable) > and we'll > be releasing Debian 9 early next year at which point you'd be three major > versions > behind. > > HTH, > > All the best, > > AndyC Thanks Andy. That worked perfectly! See below for a full explanation (TL;DNR) What I needed to do was unbrick a Marvel OpenRD/Ultimate machine. But the current (Jessie/Stretch) version of the openocd package doesn’t talk to the USB serial/JTAG interface. I’ll be submitting a bugreport for that. When all was said and done, Lenny was too far back (openocd would talk to the device, but it didn’t have any config files for OpenRD). What I really needed was Squeeze. So this is what I did: Download and burn the squeeze DVD-1. Use it to install a minimal Squeeze on a spare disk in an otherwise unused Windows PC. If I didn’t have the PC available, I probably would have used a VM, as you suggested. Follow the unbricking directions at https://www.newit.co.uk/forum/index.php?topic=2835.0 and then restore the boot-loader environment as described at https://www.cyrius.com/debian/kirkwood/openrd/install/ Big thanks! to Malcolm and James at NewIT and Debian’s own Martin Michlmayr for clear and straightforward instruction on the various parts of this process. Happy ending: My OpenRD/Ultimate is back from zombie-land and feeling fine! Enjoy! Rick
Installing a MINIMAL Mate Desktop How?
When Squeeze was the latest I was able to install without any desktop. I would then do apt-get install gnome-session gdm3 gedit gnome-terminal gparted The result was a nice uncluttered desktop to which I could add what *I* needed rather than what the proverbial "everybody" should have ;) According to http://wiki.mate-desktop.org/download#debian I should be able to do apt-get install mate-desktop-environment-core That is not enough, it leaves me with only a command line. I have the full Mate desktop on one machine. Using Synaptic on that machine and using apt-get install on the other I was able too identify some missing pieces. "apt-get install mate-desktop-environment-core" does not install marco, xorg, xterm, nor lightdm. My brute force diagnostic procedure was to install each of them in the order listed with a reboot in between to see if everything worked. It did not. After installing each of the 1st three I was left at the command line. After installing lightdm I was presented with a blank screen. As I have minimal bandwidth available I am installing from purchased DVD's - currently version 8.0.0 . After the point release later this month I will obtain the latest. Has anyone successfully done such a minimal install as I am attempting? TIA
Actual problem resolution - was [Re: [Probable resolutuio] Re: How to diagnose an "apt-get instal"l problem]
On 9/10/2016 9:50 AM, Richard Owlett wrote: [snip] Made multiple further tries installing various packages. Got inconsistent results. The pattern leads me to believe the drive is becoming flaky. I will create an ISO from the DVD for use on a flash drive. 50+ years of trouble shooting in diverse environments is educational ;/ Actual problem was intermittent typos in package name. I mentally pronounce en-viron-ment as en-viro-ment. I.E. PBKAC ;/
Re: mount problems Please Help! Can't sshfs mount remote debian server, mount local 2nd hdd, nothing...
On 09/10/2016 07:57 PM, Anthony Baldwin wrote: On 09/10/2016 03:34 PM, Anthony Baldwin wrote: On 09/10/2016 03:28 PM, Tony Baldwin wrote: On 09/10/2016 03:07 PM, Nicolas George wrote: Le quintidi 25 fructidor, an CCXXIV, Anthony Baldwin a écrit : I apologize, but, I've never quite figured out what to do with dmesg, or what to look for in its output, etc.. it really just confuses me... I saw this: 15.690807] EXT3-fs (sda1): warning: checktime reached, running e2fsck is recommended [ 15.722318] EXT3-fs (sda1): using internal journal Looking for places that talk about the device causing problems would be a good start. Your problems are on /dev/sdb, so why do you bother with lines about /dev/sda? and tried to e2fsk /dev/sdb2 And yet again you did not read part of my previous mail, the one about using Linux's fsck on microsoft's filesystems. I have no knowlege of what a windows equivalent to fsck would be. I hardly use that system. I only even installed it, because for a brief while I was doing some work for the State (I work freelance from home) that required windows only software (my contacts with the state didn't even know what gnu/linux is), and it had to be run on bare metal, not in a virtual environment. Thankfully, I am no longer doing that work. That system is so slow, stupid and crippled that it's maddening! I let windows do it's auto-repair thingy, and when I booted back to Debian, things looked like maybe they were back to normal. I was able to do: $ ls -li total 12 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown 1357617 drwxr-xr-x 2 root root 4096 Jul 10 2015 win7 1357619 drwxr-xr-x 2 root root 4096 Jul 10 2015 winhome Then I tried do mount them again, and got the I/O error, and they're back to doing this: $ ls -li ls: cannot access winhome: Input/output error ls: cannot access win7: Input/output error total 4 1349304 drwxr-xr-x 2 root root 4096 Sep 5 13:55 myown ? d? ? ?? ?? win7 ? d? ? ?? ?? winhome I don't get it... This can't have anything to do with "the microsoft version of fsck", because the windows disk (which is actually split into two partitions, one with the win7 system, and one that's just storage) is running fine when I boot it (for a crippled OS, anyway), and mounting the storage partition fine, too. PLus, I'm having trouble sshfs mounting a remote server running Debian, which worked fine days ago, now when I try it I get the same I/O errors, and wierd inode issues I'm getting with this local hdd. ./Tony -- http://www.baldwinlinguas.com translations, localization, multilingual web development EN, ES, FR, PT
Resolved: no sound?
On 09/10/2016 08:07 PM, Anthony Baldwin wrote: On 09/10/2016 06:24 PM, deloptes wrote: Anthony Baldwin wrote: On 09/10/2016 12:35 PM, Tony Baldwin wrote: Suddenly I have no sound. Dunno why. I did just two days ago, when I was happily listening to Opeth. Pulseaudio is running: ps aux | grep pulseaudio tony 2340 0.5 0.0 370052 6788 ?S I have verified that there is no hardware problem. I plugged the speakers into a phone and they worked fine. Also, this machine has a 2nd hdd with win7 and I booted that and sound worked fine, so there appears to be no problem with the sound card or the speakers. Still stumped ./tony I would check if pulseaudio has the proper input/output devices correctly configured (and unmuted) I couldn't figure out how to do this (no man page for pulseaudio-utils), but eventually found something in th lxmenu for Audio->Pulseaudio Volume Contol, and found that analog output was muted. I Unmuted it and was startled by the glorious sound of YOB (doom metal), I had inadvertently left playing earlier in an instance of mocp I'd totally forgotten in a minimized terminal. Also check in alsamixer if something relevant is muted. This "Suddenly I have no sound" means what exactly: listening and it stopped or you rebooted and it was not there anymore? regards forgot to mark this resolved...done now Tony -- http://tonybaldwin.me all tony, all the time
Re: A few questions about cgroups in Debian 8 (Jessie)
I have found a Fedora guide to cgroups (I know this is Debian.. but i could really not find anything specific to Debian) They mention that there is a cgconfig service for systemd.. My problem is that i could not find a equivalent service for my Debian system. Listing all the units with "systemctl list-units" did not show anything regarding cgroups specifically... Maybe i'm blind but i don't seem to find any information. (Sorry if i totally overlooked something) Any help would be greatly appreciated. Thank you all ;)