Re: preseeding: disable systemd
On 13/09/14 07:40, Jonathan Dowland wrote: On Fri, Sep 12, 2014 at 07:02:06PM +0100, Iain M Conochie wrote: Not at all. This is a basic preseed file I was using for wheezy installs. I am testing it again on a new VM - gimmie an hour or so and I will post the results The one you posted was exactly that - a late_command to manually switch the inits. As explained - my late_command did not do that. As Brian has explained elsewhere, you can manually script a switch of the init system. So I guess the answer for the OP is not by default, but you can script it. Cheers Iain -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5413f0c4.4020...@thargoid.co.uk
Fwd: Upgrade issue
Forwarding to the list, I believe Björn meant for it to go there. Anyone know what could have caused this? Or how to fix this? Björn, are there any programs that you might need that do not work with debian wheezy? Before any more troubleshooting goes into this I would recommend you backup the important stuff in your home directory and anywhere you might have them and go with a fresh install. -- Forwarded message -- From: "Björn Djisktra" Date: Sep 13, 2014 2:10 AM Subject: Upgrade issue To: Cc: > Hi, > > When I upgraded my system from lenny to squeezy with apt-get upgrade, > this happened: > > Fetched 135MB in 19min29s (126.2kB/s) > Extracting templates from packages: 100% > Preconfiguring packages ... > Can't locate object method "new" via package > "Debconf::Element::Noninteractive::Note" (perhaps you forgot to load > "Debconf::Element::Noninteractive::Note"?) at > /usr/share/perl5/Debconf/FrontEnd.pm line 68, line 5. > /bin/tar: line 1: syntax error near unexpected token `>' > /bin/tar: line 1: `w1.0-0 (>= 1.7.2), libgtop2-7 (>= 2.20.0), libhal1 > (>= 0.5.8.1), libice6 (>= 1:1.0.0), libmetacity0 (>= 1:2.22.0), > libnautilus-burn4, liborbit2 (>= 1:2.14.10), libpanel-applet2-0 (>= > 2.19.3), libpango1.0-0 (>= 1.20.3), libpopt0 (>= 1.14), librsvg2-2 (>= > 2.18.1), libsm6, libstartup-notification0 (>= 0.8-1), > libtotem-plparser10 (>= 2.21.92), libwnck22 (>= 2.22.0), libxml2 (>= > 2.6.27), zlib1g (>= 1:1.1.4), librsvg2-common' > dpkg-deb: subprocess tar returned error exit status 2 > dpkg: error processing > /var/cache/apt/archives/base-files_6.0squeeze10_i386.deb (--unpack): > subprocess dpkg-deb --control returned error exit status 2 > Errors were encountered while processing: > /var/cache/apt/archives/base-files_6.0squeeze10_i386.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Can you help me?
Re: Re: Problems with lilypond-doc
Hi, Tried suggestions on apt-get purge lilypond-doc. The following happened thereafter : root@debian:/home/glenn# apt-get purge lilypond-doc + apt-get purge lilypond-doc Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: lilypond-doc* 0 upgraded, 0 newly installed, 1 to remove and 59 not upgraded. 20 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y dpkg: error processing package lilypond-doc (--purge): package is in a very bad inconsistent state; you should reinstall it before attempting a removal Errors were encountered while processing: lilypond-doc E: Sub-process /usr/bin/dpkg returned an error code (1) Do not know how to get rid of lilypond :-( Rgds, Glenn K. Agilan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/541467c9.1090...@gmail.com
Re: Problems with lilypond-doc
On 2014-09-13, Golden Chariot Charterers wrote: > > Tried suggestions on apt-get purge lilypond-doc. The following happened > thereafter : > > Do not know how to get rid of lilypond :-( > man dpkg says PACKAGE FLAGS reinst-required A package marked reinst-required is broken and requires reinstallation. These packages cannot be removed, unless forced with option --force-remove-reinstreq so perhaps dpkg --remove --force-remove-reinstreq lilypond-doc is the way to go. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnm180au.22n.cu...@einstein.electron.org
Re: Re: Problems with lilypond-doc
On Sat 13 Sep 2014 at 15:50:33 +, Golden Chariot Charterers wrote: > Hi, > > Tried suggestions on apt-get purge lilypond-doc. The following > happened thereafter : > > root@debian:/home/glenn# apt-get purge lilypond-doc > + apt-get purge lilypond-doc > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following packages will be REMOVED: > lilypond-doc* > 0 upgraded, 0 newly installed, 1 to remove and 59 not upgraded. > 20 not fully installed or removed. > After this operation, 0 B of additional disk space will be used. > Do you want to continue? [Y/n] Y > dpkg: error processing package lilypond-doc (--purge): > package is in a very bad inconsistent state; you should > reinstall it before attempting a removal > Errors were encountered while processing: > lilypond-doc > E: Sub-process /usr/bin/dpkg returned an error code (1) > > > Do not know how to get rid of lilypond :-( Obtain version 2.14.2-4 from Wheezy at https://www.debian.org/distrib/packages Alternatively, see if you have it in /var/cache/apt/archives. Then dpkg -i lilypond-doc_2.14.2-4_all.deb Now uninstall it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/13092014093712.9b8a7316a...@desktop.copernicus.demon.co.uk
Re: Making keyboard remap changes permanent without reboot.
On Sat 13 Sep 2014 at 01:53:57 +0300, Alexandros Prekates wrote: > On Fri, 12 Sep 2014 16:59:30 +0200 > B wrote: > > > On Fri, 12 Sep 2014 17:48:50 +0300 > > Alexandros Prekates wrote: > > > > > You are right. With fvwm the new settings are active all time. > > > With the default xfce window manager the settings are lost after > > > some time. Even if i reboot /etc/default/keyboard changes wont hold! > > > So i guess its an xfce's xfwm4 bug? > > > > Just in case, check all possible logs to see if you find > > a trace of this reverse action. > > > > I checked slim's log , xorg's log and . .xsessions_error > > No luck. But i think i narrowed the failure trigger to the instant > screensaver starts executing. How did you go about doing that? You're using xscreensaver? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140913091232.gx4...@copernicus.demon.co.uk
how to reinstall bash
By some mistake, I remove the /bin/bash Any suggestions? Thanks, -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAG9cJmk=uE0MU32A7a_rGKraH9eqVyjLBfnQ=nauifnp_c3...@mail.gmail.com
Re: how to reinstall bash [Update]
Am Samstag, 13. September 2014, 17:39:04 schrieb lina: > By some mistake, I remove the /bin/bash > > Any suggestions? > > Thanks, If my previos hints, do not work, start a livefile system (debian live or knoppix), get the binary from there, mount the partiion wherer /usr/bin resides and copy the binary from there. Best Hans -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/18096031.s2GflDIiAy@protheus2
Re: how to reinstall bash
Done by following the link: http://ubuntuforums.org/showthread.php?t=1618902 namely, 1] ln -sf /bin/sh /bin/bash 2] apt-get install --reinstall bash -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAG9cJmm=bdoCoHHOFU=wjxf6ymih9c-ehgrtq78sv_xqtco...@mail.gmail.com
Re: how to reinstall bash
Le samedi 13 septembre 2014 à 17:39 +0800, lina a écrit : > By some mistake, I remove the /bin/bash > > Any suggestions? In a console: $ sudo aptitude reinstall bash -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1410601486.2213.204.ca...@obry.net
Re: how to reinstall bash
Am Samstag, 13. September 2014, 17:39:04 schrieb lina: > By some mistake, I remove the /bin/bash > > Any suggestions? > > Thanks, Try first: apt-get --reinstall install bash if this does not work, try dpkg --force-overwrite -i /var/cache/apt/archive/bash.deb if this does not work, try: apt-get remove bash apt-get install bash Good luck Hans -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1783505.HrkSpcY2Vb@protheus2
Re: preseeding: disable systemd
Le 12/09/2014 23:43, Brian a écrit : > On Fri 12 Sep 2014 at 22:10:28 +0200, Martin Vegter wrote: > >> I read somewhere that Jessie will still support the old SysVinit (even >> if it's not the default init). I intend to use Debian as long as I can >> avoid using systemd. > After installation you definitely need to do: > > apt-get install sysvinit-core > > You may also have to do: > > apt-get install systemd-shim > > before issuing the first command. > > That's NOT removing systemd. You'll still get systemd with this. De facto yiu cannot opt out systemd. It is compulsory. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54141adc.1020...@rail.eu.org
OpenCV 2.4.9 HIGHGUI ERROR: V4L2: Could not obtain specifics of capture window.
Hi, In first place sorry for my bad english. I am very new in OpenCV, I am trying to record a video stream from a "Hauppauge HS PVR" usb device (ID 2040:4903). I am using "Debian GNU/Linux jessie/sid" from testing branch. I was compiled OpenCV using this instructions: http://docs.opencv.org/doc/tutorials/introduction/desktop_java/java_dev_intro.html (OpenCV was not download using git as the instructions says, it was downloaded manually from opencv web page at version 2.4.9) The compilation was fine. This is the output of CMAKE that was compiled good: -- = START OF CMAKE OUTPUT == -- root@debian:/usr/src/opencv-2.4.9# cmake -DBUILD_SHARED_LIBS=OFF -DWITH_QT=ON ../opencv-2.4.9/ -- Detected version of GNU GCC: 49 (409) -- Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR) -- Could NOT find TIFF (missing: TIFF_LIBRARY TIFF_INCLUDE_DIR) -- Could NOT find JPEG (missing: JPEG_LIBRARY JPEG_INCLUDE_DIR) -- Could NOT find Jasper (missing: JASPER_LIBRARIES JASPER_INCLUDE_DIR) -- Could NOT find PNG (missing: PNG_LIBRARY PNG_PNG_INCLUDE_DIR) CMake Warning at cmake/OpenCVFindLibsGUI.cmake:18 (find_package): By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Core", but CMake did not find one. Could not find a package configuration file provided by "Qt5Core" with any of the following names: Qt5CoreConfig.cmake qt5core-config.cmake Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set "Qt5Core_DIR" to a directory containing one of the above files. If "Qt5Core" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:466 (include) CMake Warning at cmake/OpenCVFindLibsGUI.cmake:19 (find_package): By not providing "FindQt5Gui.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Gui", but CMake did not find one. Could not find a package configuration file provided by "Qt5Gui" with any of the following names: Qt5GuiConfig.cmake qt5gui-config.cmake Add the installation prefix of "Qt5Gui" to CMAKE_PREFIX_PATH or set "Qt5Gui_DIR" to a directory containing one of the above files. If "Qt5Gui" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:466 (include) CMake Warning at cmake/OpenCVFindLibsGUI.cmake:20 (find_package): By not providing "FindQt5Widgets.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Widgets", but CMake did not find one. Could not find a package configuration file provided by "Qt5Widgets" with any of the following names: Qt5WidgetsConfig.cmake qt5widgets-config.cmake Add the installation prefix of "Qt5Widgets" to CMAKE_PREFIX_PATH or set "Qt5Widgets_DIR" to a directory containing one of the above files. If "Qt5Widgets" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:466 (include) CMake Warning at cmake/OpenCVFindLibsGUI.cmake:21 (find_package): By not providing "FindQt5Test.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Test", but CMake did not find one. Could not find a package configuration file provided by "Qt5Test" with any of the following names: Qt5TestConfig.cmake qt5test-config.cmake Add the installation prefix of "Qt5Test" to CMAKE_PREFIX_PATH or set "Qt5Test_DIR" to a directory containing one of the above files. If "Qt5Test" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:466 (include) CMake Warning at cmake/OpenCVFindLibsGUI.cmake:22 (find_package): By not providing "FindQt5Concurrent.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Concurrent", but CMake did not find one. Could not find a package configuration file provided by "Qt5Concurrent" with any of the following names: Qt5ConcurrentConfig.cmake qt5concurrent-config.cmake Add the installation prefix of "Qt5Concurrent" to CMAKE_PREFIX_PATH or set "Qt5Concurrent_DIR" to a directory containing one of the above files. If "Qt5Concurrent" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:466 (include) -- Looking for Q_WS_X11 -- Looking for Q_WS_X11 - found -- Looking for Q_WS_WIN -- Looking for Q_WS_WIN - not found -- Looking for Q_WS_QWS -- Looking for Q_WS_QWS - not foun
Re: preseeding: disable systemd
Am 13.09.2014 um 12:22 schrieb Erwan David: > Le 12/09/2014 23:43, Brian a écrit : >> On Fri 12 Sep 2014 at 22:10:28 +0200, Martin Vegter wrote: >> >>> I read somewhere that Jessie will still support the old SysVinit (even >>> if it's not the default init). I intend to use Debian as long as I can >>> avoid using systemd. >> After installation you definitely need to do: >> >> apt-get install sysvinit-core >> >> You may also have to do: >> >> apt-get install systemd-shim >> >> before issuing the first command. >> >> > That's NOT removing systemd. You'll still get systemd with this. > > De facto yiu cannot opt out systemd. It is compulsory. Nope, you are wrong and you should know better by now as this has been explained many times already. -- 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: preseeding: disable systemd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/13/2014 at 07:42 AM, Michael Biebl wrote: > Am 13.09.2014 um 12:22 schrieb Erwan David: > >> Le 12/09/2014 23:43, Brian a écrit : >>> After installation you definitely need to do: >>> >>> apt-get install sysvinit-core >>> >>> You may also have to do: >>> >>> apt-get install systemd-shim >>> >>> before issuing the first command. >>> >>> >> That's NOT removing systemd. You'll still get systemd with this. >> >> De facto yiu cannot opt out systemd. It is compulsory. > > Nope, you are wrong and you should know better by now as this has > been explained many times already. Again, I think this is another example of people disagreeing about what it means to - as it was expressed in this case - "get systemd". I raised this point in an earlier thread, here: https://lists.debian.org/debian-user/2014/08/msg01591.html I think clarifying what people mean by this, rather than merely contradicting one another back and forth, could be more constructive. - -- The Wanderer Secrecy is the beginning of tyranny. A government exists to serve its citizens, not to control them. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUFDPXAAoJEASpNY00KDJrR7gP/jzSOyp4+SiuN+fP+1YROdg5 gfPJApbLLe1b1t0KYdDwPqeBg0VM+svqHMiJqhBA1hioTQCLsGAcMOOXIa1P7Z0J 8yKlzP0ZKCk1SN+R0JpU9r3a9HT9+emBpvfnO4S/L6sitD7ESYLwJY77okdEr4fo GPxGyZ9C9IJZcPQ8171RlPkAuVqJDo4kdHkjUkaPdKGRx/CY3FPo/oDEFDXFFUOI WKNMDkCZJ/uCnIV4dztHDFaR6u02GUIerAq8muXfMu+F/e2Q0tzhYW9ha03bl8mu 3Y6QnZOE0VZ8iTfPRNVuk0A272GvEZdR9oWFAbkDqaJLFngsOg+jtgyJgJDYIjcc 3XZXI+HUjfPuJ1boFtzn3GFO2argMzlKuwjZeTKkBWsPKrpyyj6Xass6nzZTL2a1 F555+HbVirpRRHix0qqRCknNCRdpeAgl2ggrAk2UpO7nlfYxNhNLONum95LJ/hf0 X6V8yyB2M1Od6YxoIM6Gm/hvk/++MQqVGO7IxmnSkkDwmanAfOZ6h9SGLKg4MNRI 4Ki5r8GaImxdzn211bfNaXqqkpsojldFidJyN1jrOOhphnRlr0+bEF6BveQ2yxNQ Kh4QrdGz7bJeYSHsCOg3UmZL8NKFAk8buycxubMuvLIH5POy4QY93JcoaORMDbM1 9c0mNjgSNe9d3sAI1NgM =4nhm -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/541433d7.8040...@fastmail.fm
Re: need suggestion on Virtualization backup/DR site.
On Fri, Sep 12, 2014 at 08:33:39PM +0200, B wrote: > On Fri, 12 Sep 2014 22:57:57 +0500 > Muhammad Yousuf Khan wrote: > > > Thanks for the input i really appreciate that. but i have a confusion > > to clear. if i use direct rsync and rsync with Backuppc what is the > > difference? > > First, backups are nightly compressed and same files are hardlinked, > so keeping a looong history is not a problem at all (AFA you have > enough free inodes; I's recommend XFS as the reception FS); 2nd, > you can trigger another backup (or restore) whenever you want, > 3rd if you have users, they can also trigger a backup/restore when > needed from the http(s) backuppc interface, 4th as backups are > presented as a tree which goes down to the file level, you can > just B/R one file at a time if needed. > More reasons to use backuppc: There's a handy web interface. If the machine to be backed up isn't reachable, it tries again later (1 hour by default). You can configure blackout periods, so no backups will take place during certain hours. You can override the blackout periods based on how old the latest backup is. There is an active email support list (backuppc-us...@lists.sourceforge.net). -Rob signature.asc Description: Digital signature
Re: need suggestion on Virtualization backup/DR site.
On Sat, 13 Sep 2014 08:53:55 -0400 Rob Owens wrote: > There's a handy web interface. > If the machine to be backed up isn't reachable, it tries again later (1 > hour by default). > You can configure blackout periods, so no backups will take place > during certain hours. > You can override the blackout periods based on how old the latest > backup is. > There is an active email support list > (backuppc-us...@lists.sourceforge.net). To be clear, it is the archetype of mandatory programs you completely forget once correctly configured ;-) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140913145754.1cf5ca6f@msi.defcon1
Re: preseeding: disable systemd
On Sat 13 Sep 2014 at 08:08:55 -0400, The Wanderer wrote: > On 09/13/2014 at 07:42 AM, Michael Biebl wrote: > > > Am 13.09.2014 um 12:22 schrieb Erwan David: > > > >> Le 12/09/2014 23:43, Brian a écrit : > > >>> After installation you definitely need to do: > >>> > >>> apt-get install sysvinit-core > >>> > >>> You may also have to do: > >>> > >>> apt-get install systemd-shim > >>> > >>> before issuing the first command. > >>> > >>> > >> That's NOT removing systemd. You'll still get systemd with this. > >> > >> De facto yiu cannot opt out systemd. It is compulsory. > > > > Nope, you are wrong and you should know better by now as this has > > been explained many times already. > > Again, I think this is another example of people disagreeing about what > it means to - as it was expressed in this case - "get systemd". Everyone in this thread, bar one, has a good understanding that the OP was clearly asking about an init system for PID 1. > I raised this point in an earlier thread, here: > > https://lists.debian.org/debian-user/2014/08/msg01591.html > > I think clarifying what people mean by this, rather than merely > contradicting one another back and forth, could be more constructive. Nothing needs to clarified. The only contradictory post is based on not grasping what the OP asked. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140913124839.gy4...@copernicus.demon.co.uk
Re: Re: how to reinstall bash
> Done by following the link: > http://ubuntuforums.org/showthread.php?t=1618902 > namely, > > 1] ln -sf /bin/sh /bin/bash That is an unfortunate mistake; the link name and target are the wrong way round. It will make /bin/bash into a symbolic link when it should be an ELF binary. > 2] apt-get install --reinstall bash I'm not sure whether that would repair the damage caused by [1]. To check, please run this command and paste the output into your reply: ls -l /bin/sh /bin/bash /bin/dash -- Cheers, Clive -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140913150638.GA11020@rimmer.localdomain
Re: Is there any documentation on how to configure the Gnome Desktop environment?
On Fri 12 Sep 2014 at 16:35:05 -0700, Rick Thomas wrote: > > On 09/11/14 06:14, Brian wrote: > >On Wed 10 Sep 2014 at 23:35:53 -0700, Rick Thomas wrote: > > > >>In particular, I’m interested in getting Gnome under Jessie to use a > >>terminal program that isn’t gnome-terminal. > >Activities -> Show Applications -> Settings -> Keyboard -> Shortcuts > > > >Custom Shortcuts -> Name/Command -> Apply > > > >Click on "Disabled" -> Then press key(s) you want to launch an xterm > > Thanks! That helped alot! (-: But it's really buried quite deep > in the menus. /-: Reduce the digging: a right click on the desktop takes you to "Settings". And you only have to do it the once. > Now, the question is: how do I make xterm (or lxterm) the > "local-official" terminal app under my local version of Gnome. Is > there a place buried even deeper in the menus for that? Bring up an xterm from gnome-terminal; its icon will be under "Activities". Right click on the icon; "Add to Favourites". -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/13092014163814.e025017d3...@desktop.copernicus.demon.co.uk
Sound and Vision - Problems with my computer speakers and video drivers
Hello everyone, https://www.youtube.com/watch?v=GYEOlxcirX0 I'm having two technical issues trying to get Debian (Jessie) set up running on my Lenovo T430 laptop, and I wanted to ask if someone would be able to help me out with either. 1. I'd like to upgrade my video drivers (for playing some games on Steam). I've got an NVIDIA GF108M (NVS 5400M) and tried to run # aptitude install lib-gl1-nvidia-glx:i386 (Having previously set up i386 architecture) And, after restarting my computer, my OS would not load. I ended up reformatting and reinstalling everything. Needless to say (but said anyway), I'm a little gun-shy about trying that again. Is there a better way to try and update my video drivers? 2. As part of the whole reformat and reinstall, my computer is no longer playing anything on its embedded speakers. The headphone jack works just fine, it's just the embedded speakers. This was also a problem when I installed (from CD) to Wheezy. Looking at documentation online, there seems to be a lot of reference to ALSA, but AFAIK that seems to have been depreciated for Jessie (and the alsa_base.conf file is not present in /etc/modprobe.d/). Does anyone have any recommendations? Thank you for your help, Paul -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5414645b.6020...@caltech.edu
Re: systemd vs debian soc (was ... Re: brasero requires gvfs)
On Fri, Sep 12, 2014 at 07:52:28PM +0200, Slavko wrote: > Ahoj, > > Dňa Thu, 11 Sep 2014 20:15:59 +0200 lee napísal: > > > Supporting systemd violates Debians' social contract. > > Can you be more verbose about this, please? Why? How? By what? > Item 4 says: "We will be guided by the needs of our users and the free software community. We will place their interests first in our priorities. We will support the needs of our users for operation in many different kinds of computing environments." The way I see it, there is a large amount of doubt on who's insterested in systemd and there is no doubt that many users are being forced into using it and, according to your recent post on the subject, those users have currently no way of purging systemd from their systems without losing the ability of running an imense chainload of userland software. So are we trying to support the need of our users for operation in many different kinds of computing environments or are we pushing some distro that actualy did that into becoming a GiB monolith? Are kFreeBSD and Hurd becoming farther and farther to reach? signature.asc Description: Digital signature
Tip: apt-listbugs (Was: policykit + systemd)
On 9/4/14, Darac Marjal wrote:
> On Wed, Sep 03, 2014 at 06:35:30PM -0700, Rusi Mody wrote:
>>
>> Now dist-upgrade is bringing back these (and some others):
>>
>> libpolkit-agent-1-0{a} libpolkit-backend-1-0{a} libupower-glib3{a}
>> policykit-1{a}
>>
>> Is that ok?
>
> If in doubt, install apt-listbugs first. That will warn you if there are
> any important bugs affecting the to-be-installed versions. Read the bug
> reports and see if they apply in your situation and then either install
> the packages or use apt-listbugs to apply a pin which will skip the
> installation of the buggy package (when a fixed package arrives, you'll
> get the opportunity to upgrade as normal).
Stumbled back on this while trying to find threads referencing
policykit. Feels appropriate to highlight with it seeming there's a
lot of mention of bugs lately. Had never heard of apt-listbugs.
Installed after reading the above suggestion. A basic example of its
output:
elf@northpole:~$ apt-listbugs list apt
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
serious bugs of apt (-> )
#558784 - apt: re-adds removed keys (Fixed: 0.9.10)
#701048 - many squeeze->wheezy upgrades fail with "Could not perform
immediate configuration" (Fixed: apt/0.9.9)
Merged with: 645713
Summary:
apt(2 bugs)
I've also had it interrupt installs by pointing out a bug or bugs then
asking if the user wants to continue installing or abort to do further
research first. I can't help wondering out loud if broader use of any
tool of this type that is specific to a user's CHOICE of package
managers might somehow draw in faster bug fixes purely due to more
exposure..
Cindy :)
--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with duct tape *
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/CAO1P-kBiBAxAU5+JyPUyKa56ciqLZBg=BQp0cuNZ=4pda+f...@mail.gmail.com
Re: terminal doesn't come up in Jessie Beta-1?
On Sep 13, 2014, at 11:14 AM, Cindy-Sue Causey wrote: > On 9/8/14, B wrote: >> >> From what I read (I'm not an expert, so I may be wrong), >> gnome-terminal called gdbus that called dbus, asking it to >> spawn a child of itself but this child (?) exited with a status of 8. >> >> From this error, I found what you should have found with a bit >> of personal research: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746415 >> https://bbs.archlinux.org/viewtopic.php?id=180103 > > > Throwing this out there because I had a "similarly different" > experience while following this thread. Mine is solved. I was lurking > along with you all and saw B mention GDBus. Every time I rebooted > recently, have been getting this: > > "error GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An > authentication agent already exists for the given subject" > > YES, *unrelated* but my ears perked at B's mention of GDBus. You > never know so I followed the links offered, thought on it then > upgraded what /var/log/apt/history.log shows is: > > libvte-common libvte9 libvte-2.90-common libvte-2.90-9 > > I figured what could it hurt since it's an upgrade that needs done > anyway, right? WRONG. Gnome-terminal that was working previously in my > case was no longer accessible. Became very similar to as described > in this thread but no locale related error. > > None of the alternative ways of launching worked. Error message I got > when trying to launch via xterm was: > > gnome-terminal: symbol lookup error: gnome-terminal: undefined symbol: > vte_terminal_set_alternate_screen_scroll > > Received that error in two different places, for those liking alternatives: > > * Was the above output from attempting to launch gnome-terminal in xterm > * Tripped over it in ~/home//.xsession-errors while following > along with the "Query about .xsession-errors file" Debian-User thread > > Couldn't stand not being able to copy and paste (xterm wasn't > responding to various methods) so I researched the error message. > Ended up upgrading/installing more based on other users' success and > suggestions ( http://ubuntuforums.org/showthread.php?t=1894439 ): > > gir1.2-vte-2.90 libglib2.0-data libvte-2.90-9 libvte-2.90-common (yes, > 2 are duplicates that were previously handled) > > Still nothing then I FINALLY got the bright idea to upgrade > gnome-terminal. CTRL+ALT+T and... IT WORKS! > > Again, went ahead and wrote this up because maybe somehow those > package mentions MIGHT help someone else finding their own > gnome-terminal suddenly not responding to various launch methods. > > Having fixed mine now, I keep thinking on it. It was just a matter of > timing that I was "playing along" with you all, and that's what caused > mine to fail. Chances are decent it still would have malfunctioned > soon as I slowly upgrade this latest install.. And .xsessions-errors > has now become a new favorite go-to because this user-induced error > helped highlight that file's function. It's all good. :) > > Cindy :) Thank you Cindy, What level of Debian are you using? Wheezy or Jessie? My problems were occurring with the Jessie beta-1 fully updated to the latest everything. So upgrading to a newer version of something isn’t an option without venturing into “experimental” territory. I’d be willing to try something from an experimental repo — after all, this is a testing machine and I’m a tester by inclination. But that doesn’t sound like what you were doing? Am I misreading? Thanks! Rick -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1ec1257e-ba63-47bf-8bcd-13779f30e...@pobox.com
Re: Power Mac G4 stuck "Loading second stage bootstrap"
On 12/09/14 04:35, bruno evangelista wrote: > [...] I have right now the very same DVD with Ubuntu iso > file in the tray inside the computer. When I start the computer and > hold c key nothing happens. If I shut down the computer and restart it > I have exactly the same thing on the screen right from its start. If I > hold the c key when I start the computer it will replace (for about 30 > seconds) the last line that reads *"Loading second stage bootstrap..."* > with "*Loadind CD ROM...".* But then it returns to *"Loading second > stage bootstrap...". *It does not do anything after that and **I can't > get out of it. I'm sorry, I don't know enough about the Power Mac G4 to help with this. I suspect you might have a hardware problem. You could also try to ask in Ubuntu user forums about this. I can only suggest to disconnect the internal hard drive to see if it is still possible to boot from the CD/DVDs that worked before. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54149123.7070...@pyro.eu.org
configuration of LightDM
Hello again, This refers to a Sharp Mebius laptop with current Wheezy. https://wiki.debian.org/LightDM instructs "To change the current default Display Manager, run dpkg-reconfigure lightdm" root@mebius:~# dpkg-reconfigure lightdm [] Reloading system message bus config...Failed to open connection to "syste m" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory invoke-rc.d: initscript dbus, action "reload" failed. root@mebius:~# Several bug reports and messages have intersecting words. Any ideas or tips before I start reading? Thanks,... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 12 Tel +1 360 639 0202 http://carnot.yi.org/ Bcc: peter at easthope. ca -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/E1XSsky-0003lR-SS@dalton.invalid
Re: Sound and Vision - Problems with my computer speakers and video drivers
On 09/13/2014 11:35 AM, Paul Anzel wrote: Hello everyone, https://www.youtube.com/watch?v=GYEOlxcirX0 I'm having two technical issues trying to get Debian (Jessie) set up running on my Lenovo T430 laptop, and I wanted to ask if someone would be able to help me out with either. 1. I'd like to upgrade my video drivers (for playing some games on Steam). I've got an NVIDIA GF108M (NVS 5400M) and tried to run # aptitude install lib-gl1-nvidia-glx:i386 (Having previously set up i386 architecture) And, after restarting my computer, my OS would not load. I ended up reformatting and reinstalling everything. Needless to say (but said anyway), I'm a little gun-shy about trying that again. Is there a better way to try and update my video drivers? 2. As part of the whole reformat and reinstall, my computer is no longer playing anything on its embedded speakers. The headphone jack works just fine, it's just the embedded speakers. This was also a problem when I installed (from CD) to Wheezy. Looking at documentation online, there seems to be a lot of reference to ALSA, but AFAIK that seems to have been depreciated for Jessie (and the alsa_base.conf file is not present in /etc/modprobe.d/). Does anyone have any recommendations? Thank you for your help, Paul You didn't get into the computer speakers, but I recommend one of two solutions for computer speakers: the best is to find some good hi-fi speakers--ones made for record/cd playing in a living room-- and an amplifier or receiver, and push your computer sound thru that. The next best thing, but quite a ways down the list, is a Logitech setup. The Logitech system consists of a sub-woofer that you put under your table or desk, and two satellite speakers that can sit on the computer table or hang on the wall. This system sounds quite good, altho IO found that the bass is exagerated it you pur the sub-woofer up against the wall. I wound up putting an octave- band equalizer between the computer and the Logitech system. Those little amplified speakers that sell for almost nothing are pure junk. If you have any, throw them out! BTW: Yard sales/garage sales always seem to have hi-fi amps and receivers for practically nothing, but it's tough to find decent hi-fi speakers. If you do find speaker cabinets, take off the front grille and see that the surround on the main speaker is not torn up. If it is, don't buy it! Personally, I'm not a fan of "bookshelf" speakers. I like to see a cabinet about 14" wide by 12" deep by 2 feet high, or thereabouts. --doug -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5414afa2.80...@optonline.net
Re: Query about existence of way to free up unnecessary RAM usage
B writes: > On Thu, 11 Sep 2014 20:22:01 +0200 > lee wrote: > >> Why would you say that? > > root denied access to sysctl keys (that doesn't even exist on my > systems). I got some denied, too, and some didn't exist. -- Knowledge is volatile and fluid. Software is power. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87bnqjw894@yun.yagibdah.de
Re: Issues upgrading Wheezy --> Jessie (was ... Re: brasero requires gvfs)
Slavko writes: > Ahoj, > > Dňa Thu, 11 Sep 2014 20:15:59 +0200 lee napísal: > >> Supporting systemd violates Debians' social contract. > > Can you be more verbose about this, please? Why? How? By what? I'm finding it pretty obvious. The social contract says: "Our priorities are our users and free software We will be guided by the needs of our users and the free software community. We will place their interests first in our priorities. We will support the needs of our users for operation in many different kinds of computing environments. [...] we will provide an integrated system of high-quality materials"[1] Debian has decided to make systemd the default init system, and apparently they are going to decide that even on mere distribution upgrades, systemd will be the default init system without the users at least being given a choice. I claim that it is *not* in the interest of the users or of "the free software community" to make something the default init system which is broken by design, is encumbered with serious issues and raises a lot of concern amongst the users. The developers of this init system, or at least some of them, apparently have a reputation for thinking that their software can break whatever they want and to leave it up to others to modify their software to fix what the systemd-people broke. I am warning of relying on software made by developers with an attitude like this because it's prone to cause trouble. It may cause the more trouble the more Debian depends on this software, and trouble like that is *not* in the interest of the users. Debian is not only making a very troublesome init system the future default. They also allow a great number of packages providing software which is totally unrelated to an init system to depend on this init system, effectively making the whole distribution depend on a particular init system, or parts thereof. I claim that a Linux system, or distribution, as a whole *must not* depend on a particular init system and that in doing so, choices are being taken away and users' freedom is diminished. Designing a Linux system/distribution this way makes the system/distribution broken by design. This state of broken design may be a reflection of the brokenness-by-design of the init system many people have pointed out. I fail to see how it could be in the interest of the users or of "the free software community" to turn Linux systems, or Linux distributions, into systems or distributions that are broken by design and which abandon substantial ideas that have contributed greatly not only to the quality and reliability of Linux systems but also to the freedom of their users: the idea being that a particular software shall do one thing according to its purpose, do that well and no more. This idea has resulted to choices being available to users which allow them to pick which software to use and to the reliability of their systems, and it has given them control over their systems. AFAIK, users have had no saying whatsoever in the decision about the future default init system, and they still have none. I claim that Debian *does not* make its users their priority by making such a decision without consulting their users, especially not when they leave them no choice but to use the default init system, no matter whether through dependencies or through forcibly installing it in the process of upgrading from one distribution to another. I see that delivering a distribution which is broken by design does *not* mean that Debian provides "an integrated system of high-quality"[1]. However, it's arguable what this part of the social contract is supposed to mean: Providing a distribution which is broken by design doesn't make it impossible to provide "high quality materials"[1] as part of it. Yet I would assume that the intention is not only to provide some material of high quality but to provide a Linux distribution which is of high quality. When Debian is truly "guided by the needs of"[1] their "users and"[1] of "the free software community"[1], and when Debian places "their interests first in"[1] their "priorities"[1], then would Debian not have to strive to make /a distribution of high quality/ rather than striving to make /a distribution that has some material which is of high quality/? There may be more points in their social contract or otherwhere that are violated by the decision to make systemd the default init system and by simply accepting that virtually the whole distribution depends on it. Feel free to point them out --- so far, my reasoning seems to have been ignored, and I might actually have to make a bug report (against Debian itself) to get a response to these concerns. I'd be happy to see some support. I cannot speak for "the users" or for "the free software community". You users, and the community members, whoever they are, need to speak as well. [1]: https://www.debian.org/social_contract -- Knowledge is volatile and fl
Re: Query about existence of way to free up unnecessary RAM usage
Curt writes: > On 2014-09-12, Jonathan Dowland wrote: >> >> Possibly because nobody has stepped up to write a new algorithm. >> > > Seems more like simple multiplication than algorithmic calculation to me. Multiplication is an algorithmic operation. -- Knowledge is volatile and fluid. Software is power. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/877g17w86n@yun.yagibdah.de
Re: brasero requires gvfs
Steve Litt writes: > When Jessie goes stable, I'm actually going to try Jessie to see whether > it will work reasonably, and if so I'll hold my nose and use the > monolithic entanglement. FWIW, I can tell you that it works for Fedora. So with a new installation, it can potentially work for Debian, too. Whether upgrading would work is a another question. > 2) Use Gentoo. If that goes systemd, move to Funtoo. Can you have, say, KDE on Gentoo without systemd? "Without systemd" means *all* of systemd, like systemd-login0 etc.. > 3) Use OpenBSD, with a virtual machine running [Debian | Ubuntu] for >the specific purpose of running Sigil and other stuff that won't run >on OpenBSD. > > I'm having trouble getting qemu to input from my keyboard in OpenBSD, > but that's a question for another mailing list. Not really because it concerns everyone considering to switch away from Debian. What options does OpenBSD have for virtualization? Can you use xen? And how do you pass an NVIDIA card through so that you can run things in VMs for which there is no BSD version? Are there even NVIDIA drivers for BSD? -- Knowledge is volatile and fluid. Software is power. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87oaujwb1r@yun.yagibdah.de
Re: Query about existence of way to free up unnecessary RAM usage
Don Armstrong writes: > On Thu, 11 Sep 2014, lee wrote: >> "Go down" can have various meanings. When you run a server and a >> server process (like an MTA or an IMAP or web server) is killed >> because the system runs out of memory, the server is effectively down. > > This is why you use things like systemd or similar which are capable of > tracking processes and restarting them when they are killed or fail for > whatever reason. Do these systems check or somehow predict whether there is enough memory available to restart the processes that were killed? Unless they do that, they may very well make the problem worse. >> It may not be unstable (though I consider a system without an >> operational MTA as non-functional), yet you never know what process >> will be killed. > > You're trading having a few processes killed off (often, the very > process which is consuming too much memory) with thrashing, and all > processes either being just slow (if you're lucky) or so slow that they > hit timeouts. If it's thrashing swap that badly, it might as well be > down. There's always the chance that the system recovers. If I can intervene, that chance is really good. > Worse, when a machine is thrashing that badly, it's often impossible to > see what is happening with the machine at all, because even starting a > shell (or launching processes) requires swap. All you can do is use > magic sysrq and hope that it will give you enough information about what > is going on for you to kill something off. I haven't run into this problem yet. >> You could have ZFS with fuse, and what prevents such processes from >> being killed? > > You can inform the OOM killer which processes should not be killed > fairly trivially. [Things like fuse, sshd, and similar should already be > informing the OOM killer that they should not be killed;[1] if not, > that's a bug.] > > 1: For ssh this is already the case. That's a good thing :) What would you rather have: A smoke alarm or something that actually prevents the fire, unless it's a really big fire? -- Knowledge is volatile and fluid. Software is power. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87fvfvw8a6@yun.yagibdah.de
Re: brasero requires gvfs
Slavko writes: > BTW, if someone is interested in, while this investigation i generated > graphs of dependencies on some systemd packages on my system, they > will be accessible for some time here: > > http://anfo.slavino.sk/libpam-systemd.png > http://anfo.slavino.sk/libsystemd-daemon0.png > http://anfo.slavino.sk/libsystemd-journal0.png > http://anfo.slavino.sk/libsystemd-login0.png How did you create these? Would you mind if I downloaded the images and put them on my web server, potentially with some explanation? I've been sending some posts to debian-devel, and these graphs might come in handy sooner or later. Especially the last one is rather interesting since it clearly shows that basically the whole system depends on systemd. How would such graphs look for sysvinit? -- Knowledge is volatile and fluid. Software is power. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87sijvwbfg@yun.yagibdah.de
Re: Query about existence of way to free up unnecessary RAM usage
The Wanderer writes: > On 09/12/2014 at 12:25 PM, Bret Busby wrote: > >> On 12/09/2014, The Wanderer wrote: >> >>> On 09/10/2014 at 04:00 AM, Bret Busby wrote: >> >> So, whether or not the swap partition is bigger than needed, >> should not influence the inability of the system, to use the swap >> partition, and, thence, whether or not the swap partition is too >> big, has no bearing on the problem. >> >> Correct? > > Sounds right to me. > > Unless I'm missing a twist somewhere, the only effects of having a > too-big swap partition should be: > > * Wasted disk space, which could otherwise be used for other purposes. > > * Inordinately large likelihood that the system will at some point swap > important processes out, thereby slowing down normal system operation, > because it thinks it needs to keep some huge static data in active RAM. What or how has the size of the swap partition to do with what the system figures which data needs to be kept in RAM? The amount of RAM seems to have a much greater influence on how much RAM is being used than the size of the swap partition. I've seen seamonkey with 2GB RAM usage when 8GB was available. Now it's running on a VM that has only 2GB RAM, and seamonkey needs "only" 1GB. -- Knowledge is volatile and fluid. Software is power. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8738bvw7sv@yun.yagibdah.de
Re: Making keyboard remap changes permanent without reboot.
Alexandros Prekates writes: > My system is Debian stable with xfce. > > Wanting to swap CAPSLOCK with CONTROL i changed /etc/default/keyboard > and following debian wiki page on keyboard i executed: > > sudo udevadm trigger --subsystem-match=input --action=change > > It worked! But .. after some minutes the swap is reverted back to the > initial config withoud doing sth. > > How can that be avoided? , [ /etc/X11/xorg.conf ] | | Section "InputDevice" | Identifier "Keyboard0" | Driver "kbd" | Option "XKBOptions" "ctrl:nocaps" | #Option "XkbModel" "pc105" | Option "XkbModel" "pc102" | Option "XkbLayout" "de" | EndSection ` Make sure you adjust to your particular keyboard, and you *must* have set up the keyboard for the console correctly. When you cannot switch with Ctrl+Alt+Fn to the console, that may be an indication that your keyboard is not set up correctly to begin with (switching can be disabled by config and usually isn't by default). , [ ~/.Xmodmap ] | | keycode 66 = Control_L Control_L Control_L Control_L ` Look at 'xmodmap -pk', use 'xev' to get the keycodes and you can set it up as you like. -- Knowledge is volatile and fluid. Software is power. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87tx4busj8@yun.yagibdah.de
Re: Query about existence of way to free up unnecessary RAM usage
B writes: > On Thu, 11 Sep 2014 20:32:08 +0200 > lee wrote: > >> Mounting swap partitions with the same priority does not provide >> redundancy. > > As RAID doesn't provide data integrity w/ regular RAM. RAID doesn't provide data integrity even with ECC RAM. It only provides redundancy (with some RAID levels). Use ECC RAM and a file system that does checksumming for data integrity --- might be a bit difficult for swap, though. Does swapping to partitions use checksumming for data integrity? If not, you can always swap to files. -- Knowledge is volatile and fluid. Software is power. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87y4tnut09@yun.yagibdah.de
Re: git: how to figure out with a script what the last commit on remote repo is without fetching it
Joel Rees writes: > 2014/09/12 3:35 "lee" : >> >> [...] >> Well, I don't want to program some sort of meta-git ... I merely want a >> simple way to be informed about new commits. > > I'm still wondering whether a cron job that does a status request on the > head in question wouldn't be good enough. Like Jonathan suggested? That would probably work fine for what I'm doing with the repos reachable via https. > I don't recall svn or cvs doing this without using a hook, either, even > though a commit does mean something else there. I suspect that the makers of these systems might not want users to pull the information and thus decided not to implement a feature that allows to get it in some easy way ... -- Knowledge is volatile and fluid. Software is power. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87mwa3ur04@yun.yagibdah.de
Re: Issues upgrading Wheezy --> Jessie (was ... Re: brasero requires gvfs)
On Sat, 13 Sep 2014 22:46:31 +0200 lee wrote: All interesting things you said, plus a bunch of other readings confort me in my first impression: Linux was becoming too much secured for the taste of agencies (and which better candidate than a gas plant that hammers its looong claws down to… dbus, which assume most of the machine exchanges, and a convenient "project" that big that it inevitably will produce nice and juicy security bugs for the next decades to come). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140914001022.017d4a7e@msi.defcon1
Re: Query about existence of way to free up unnecessary RAM usage
On Sat, 13 Sep 2014 22:56:48 +0200 lee wrote: > Multiplication is an algorithmic operation. Well, technically speaking, it is additions. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140914001350.3e64da65@msi.defcon1
Re: Query about existence of way to free up unnecessary RAM usage
On Sat, 13 Sep 2014 23:09:58 +0200 lee wrote: > RAID doesn't provide data integrity even with ECC RAM. You still have much more chances to avoid writing a bad byte w/ ECC than with regular RAM, though. > It only provides redundancy (with some RAID levels). Use ECC RAM and a > file system that does checksumming for data integrity --- might be a > bit difficult for swap, though. That's why I like this FS, which is now more usable with powerful chipsets/CPUs. > Does swapping to partitions use > checksumming for data integrity? Not that I know of (but I always make a looong destructive test before use, either on regular partitions and swaps). > If not, you can always swap to files. This isn't a good idea, perfs are much degraded using that. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140914002430.6b21785f@msi.defcon1
Chroot/Debootstrap Mechanisms (Was: terminal doesn't come up in Jessie Beta-1?)
On 9/13/14, Rick Thomas wrote: > > What level of Debian are you using? Wheezy or Jessie? My problems were > occurring with the Jessie beta-1 fully updated to the latest everything. So > upgrading to a newer version of something isn’t an option without venturing > into “experimental” territory. I’d be willing to try something from an > experimental repo — after all, this is a testing machine and I’m a tester by > inclination. But that doesn’t sound like what you were doing? Am I > misreading? > > Thanks! You're welcome, Rick.. Wasn't sure if I should change the subject or not. It seems to draw away from your problem so figured it should be changed. :) Yeah, I'm just the other side of ready to attempt testing. Soon. Very soon. Life keeps getting in the way. Truthfully not sure what I've got. The simple stuff, like determining version, eludes me often.. DID miraculously just have uname come to mind so ended up with this snippet from "uname -a": 3.8.0-34-generic #49~precise1-Ubuntu SMP Wed Nov 13 18:05:00 UTC 2013 Ubuntu 12.04 LTS is stated under System Settings > Details. Between that and what I've been finding on the Net last few days, I'm officially confused as to what Debian release was used. Rumors hint it's Wheezy but can't find fact. Even tried Wikipedia. ONE SINGLE MENTION of Debian period within the entire content. YES, am TRYING to switch to 100% Debian by name. That's sitting under chroot but other stuff keeps taking priority. Brings me to the subject line change and a DISCLAIMER up front: Apologies in advance if this turns out to just be noise. Am sure I'm simply not yet understanding the whole debooststrap/chroot process, but I keep getting this "feeling" about it based on my experiences last couple weeks. :) What you all have going. I don't know the right terminology to use to ask.. Let me try it this way. If you're suddenly having a lot of compatibility problems, are you working out of a root hierarchy or instead out of something "embedded" via debootstrap or a similar alternative? For that matter, even if you're working out of a natural root hierarchy, do you maybe have another release "harmlessly" embedded, possibly even forgotten under something like /var/chroot? Reason I'm asking is I had an ah-ha moment last week where I realized my successfully debootstrapped release was actively pulling at least part of live sessions into its subdirectories. Couple days later just happened to open /etc/fstab and see entries like /proc, /sys and /dev pointing to the chroot directory. I recognize that as a debootstrap installation check point so I had no problem seeing it. Instead am now starting to wonder how much that might play into problems I've suddenly been having. Whatever problem I was having couple weeks ago was echoed in various ways on the Net and always with people saying, BUT I DID *NOT* DO THAT!" It boiled down to something about inconsistently mixing package versions incompatibly across stable, testing, etc, releases.. Really got me to wondering about how much of the problems we're seeing questioned on lists now MIGHT be somehow tied to the word "bootstrap" and its derivatives *seeming* to appear more frequently across listservs lately.. OR NOT. :) Before sending this, I just hit up the Net again. What I'm seeing is really starting to make me wonder about this.. I wonder now if some notable number of recent problems don't just boil down to some of us debootstrap "newbies" not commanding the process optimally, maybe including simply not understanding the true power and reach of what we've undertaken... OR NOT. :D Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with duct tape * -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAO1P-kBO31Q+=tdj1dx+nqzvixqox4lk44wgvtmvghx5nbg...@mail.gmail.com
Re: MDADM RAID1 of external USB 3.0 Drives
On Thu, Sep 11, 2014 at 06:17:00PM +0200, Linux-Fan wrote: > some time ago, I bought two external Seagate 2 TB USB 3.0 HDDs in order > to expand my local storage (all internal slots are already in use). > Having created a RAID1 with MDADM just as normal, it all seemed to work, > until at one system startup MDADM told me via local mail that the Array > was degraded. In fact, one of the devices had not been recognized by the > system. Reconnecting the drive however, did not allow me to simply > continue as normal -- I had to add the device back into the RAID and > thereby triggered a resync. This did not seem a problem at the > beginning, but as the problem occurred a second time, I thought I should > search for a solution (which did not bring up anything interesting or > related) and then ask: > > Is there any means to configure MDADM (or such) to make sure that all > devices are recognized before attempting to start the array so that I > could manually reconnect the missing disk and then start the array > without any resync? > > If not, might it be a good idea to write a script to check if the > devices are available and only then enable that RAID? > > I want to avoid doing superflous resyncs as this always takes a lot of > time and seems to be an unnecessary load for the drives. What's actually happening here is that mdadm is rejecting one or the other disk because of a problem reading or writing to that. It's almost certainly a real problem, and in my experience it is not the disk itself which is bad, but something in the path (the USB port, the USB cable, the USB-SATA interface) or the power supply for the disk. You will continue to have these problems if you persist in doing this, up until the day that one disk actually fails. Time to do something else. If you can change to ESATA or invest in a SAS controller and external SAS multi-disk chassis, you can get reliable data storage again. In the meantime, you can: - add a bitmap file to the RAID, which will speed up rebuilds. - use the --no-degraded flag, to prevent assembly of a RAID that is lacking a disk. -dsr- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140914000659.gh13...@randomstring.org
Re: preseeding: disable systemd
2014/09/13 22:06 "Brian" : > > On Sat 13 Sep 2014 at 08:08:55 -0400, The Wanderer wrote: > > > On 09/13/2014 at 07:42 AM, Michael Biebl wrote: > > > > > Am 13.09.2014 um 12:22 schrieb Erwan David: > > > > > >> Le 12/09/2014 23:43, Brian a écrit : > > > > >>> After installation you definitely need to do: > > >>> > > >>> apt-get install sysvinit-core > > >>> > > >>> You may also have to do: > > >>> > > >>> apt-get install systemd-shim > > >>> > > >>> before issuing the first command. > > >>> > > >>> > > >> That's NOT removing systemd. You'll still get systemd with this. > > >> > > >> De facto yiu cannot opt out systemd. It is compulsory. > > > > > > Nope, you are wrong and you should know better by now as this has > > > been explained many times already. > > > > Again, I think this is another example of people disagreeing about what > > it means to - as it was expressed in this case - "get systemd". > > Everyone in this thread, bar one, has a good understanding that the OP > was clearly asking about an init system for PID 1. > > > I raised this point in an earlier thread, here: > > > >https://lists.debian.org/debian-user/2014/08/msg01591.html > > > > I think clarifying what people mean by this, rather than merely > > contradicting one another back and forth, could be more constructive. > > Nothing needs to clarified. The only contradictory post is based on not > grasping what the OP asked. Is your name Martin? Should we ask Martin whether he would be satisfied if (1) systemd runs at some pid higher than 1? (2) systemd is loaded, but doesn't actually run at all? (3) systemd libraries are loaded, but systemd itself is not? (4) Some emulation layer provides the functionality and no code from the systemd project gets to touch his disks? or (5) None of the apps he needs ask the OS to do any of the sort of things that systemd uniquely does? I personally am not going to be satisfied unless #5 is met. That's how deep I perceive the design bugs in systemd to extend. The marginal real functionality of systemd can and should be done another way, to avoid opening huge security holes in the OS. That few people seem to understand those holes is well apparent to me, but that doesn't mean I should pretend they don't exist. But, of course, I am not the OP, and I don't like systemd, so I don't count. What does Martin have to say? Joel Rees Computer memory is just fancy paper, CPUs just fancy pens. All is a stream of text flowing from the past into the future.
Re: Flightgear
Would be nice if all the available tiles of scenery were in the Debian archive, that way we could get the area we're interested without having to go through a huge PITA. On Fri, Sep 12, 2014 at 4:00 AM, David Baron wrote: > This has a huge amount of data, 1.5 gig. It is not possible to install on > using partitions set up by Debian installer. > > An alternative installation modus for Flightgear is in order, however. > There > is no need for that data to fill up /usr or to install in one go and run > out of > /var space. Whole business might be better on a DVD but that might be too > slow. > > So: Option to install data piece by piece to a different partition with > space > for it. > Option to install the application itself by itself to /usr as usual (now > will > try to pull the whole kitandkaboodle). > > Will need to move /usr and /var (more difficult) but not just for > flightgear. > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: https://lists.debian.org/1532954.NiMnOz5U8k@dovidhalevi > >
Re: Re: how to reinstall bash
Thanks for your scrupulous attitude. $ ls -l /bin/sh /bin/bash /bin/dash -rwxr-xr-x 1 root root 1029624 Aug 22 05:15 /bin/bash -rwxr-xr-x 1 root root 117176 Jan 10 2014 /bin/dash lrwxrwxrwx 1 root root 9 Sep 13 17:48 /bin/sh -> /bin/bash Now it is sane, the mistake came at the first place was due to my slip in treating 'ln -sf /bin/sh /bin/bash' and then I realized that mistakes but unconsciously still possess enough amount of intuition to repeat this mistake. Have a nice weekend, P.S. I have some lousy code, which complained the 'sh: Syntax error: Bad fd number', which drove me to compromise to link the sh with the bash, not dash. On Sat, Sep 13, 2014 at 11:06 PM, Clive Standbridge wrote: >> Done by following the link: >> http://ubuntuforums.org/showthread.php?t=1618902 >> namely, >> >> 1] ln -sf /bin/sh /bin/bash > > That is an unfortunate mistake; the link name and target are the wrong > way round. It will make /bin/bash into a symbolic link when it should > be an ELF binary. > >> 2] apt-get install --reinstall bash > > I'm not sure whether that would repair the damage caused by [1]. To > check, please run this command and paste the output into your reply: > > ls -l /bin/sh /bin/bash /bin/dash > > > -- > Cheers, > Clive > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: https://lists.debian.org/20140913150638.GA11020@rimmer.localdomain > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cag9cjmmmbh+cos7wci5xk8bewn-4uracuxffidpwxh9eo_j...@mail.gmail.com
Re: how to reinstall bash
On Sun, 14 Sep 2014 13:29:15 +0800 lina wrote: > $ ls -l /bin/sh /bin/bash /bin/dash > -rwxr-xr-x 1 root root 1029624 Aug 22 05:15 /bin/bash > -rwxr-xr-x 1 root root 117176 Jan 10 2014 /bin/dash > lrwxrwxrwx 1 root root 9 Sep 13 17:48 /bin/sh -> /bin/bash > > Now it is sane, the mistake came at the first place was due to my slip > in treating 'ln -sf /bin/sh /bin/bash' and then I realized that > mistakes but unconsciously still possess enough amount of intuition to > repeat this mistake. I don't know what Debian release do you use, but since Squeeze, /bin/sh should point to dash. Kind regards -- http://markorandjelovic.hopto.org One should not be afraid of humans. Well, I am not afraid of humans, but of what is inhuman in them. Ivo Andric, "Signs near the travel-road" -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140914084454.50319...@sbb.rs
