[opensuse] runlevel 3 openSUSE versus Mint 17.3
Is there anyone here with Mint 17 experience along with SuSE experience. I have been trying Mint 17.3 and find myself comparing to what I know with SuSE, I guess since I have worked with that a lot longer. I am installing a new Nvidia 960 video card on a Mint 17.3 system and am running into problems that I once could solve easily. After some Googling and searching this list, I may have some answers but I am hoping that someone here can tell me if I am on the right track. One thing I don't know with either system is how do I get the system to recognize the new card and reconfigure the xserver for the new card? How is this done with SuSE (I haven't tried it yet)? In all my searching so far I haven't found the method for Mint either. I downloaded the 960 driver from Nvidia but the instructions said I have to be in text only with no xserver. I spent a few evenings on that problem with Mint. Most forum suggestions seemed very old and useless for the current Mint. The one that finally worked was to tamper with /etc/default/grub, changing three lines so now it boots and stays in text mode and I can run startx if I want to. I see from this list that systemd has changed the runlevel concept and now the method for SuSE (if I understand correctly) is systemctl set-default multi-user.target Is this correct? Is YaST System->Boot Loader->Boot Loader Options just another way to accomplish that? It seems that Mint 17 doesn't yet have systemd so am I correct in understanding that for Mint I tamper with /etc/default/grub while for SuSE I use the systemctl method? One forum (don't remember which forum) post that suggested the grub tampering that worked for me said that I must also do the systemctl in addition to the grub tampering. Does SuSE have the /etc/default/grub and if so, would I have to tamper with that in addition to the systemctl? Damon Register -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Jul 28, 2016 at 1:56 PM, Damon Register <damon.w.register@lmco.com> wrote:
It seems that Mint 17 doesn't yet have systemd so am I correct in understanding that for Mint I tamper with /etc/default/grub while for SuSE I use the systemctl method?
On openSUSE both will work.
One forum (don't remember which forum) post that suggested the grub tampering that worked for me said that I must also do the systemctl in addition to the grub tampering. Does SuSE have the /etc/default/grub and if so, would I have to tamper with that in addition to the systemctl?
Yes, openSUSE has /etc/default/grub. You can also simply edit kernel command line in boot menu to avoid any permanent modifications. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2016-07-28 a las 06:56 -0400, Damon Register escribió:
I downloaded the 960 driver from Nvidia but the instructions said I have to be in text only with no xserver. I spent a few evenings on that problem with Mint. Most forum suggestions seemed very old and useless for the current Mint. The one that finally worked was to tamper with /etc/default/grub, changing three lines so now it boots and stays in text mode and I can run startx if I want to.
I see from this list that systemd has changed the runlevel concept and now the method for SuSE (if I understand correctly) is systemctl set-default multi-user.target Is this correct? Is YaST System->Boot Loader->Boot Loader Options just another way to accomplish that?
The procedure for openSUSE is the same as always. Yes, there are new methods, but the old one also works and will work, so most of those old advices will work. Do: log out from graphical session. Press keys simultaneously: ctrl-alt-f1 to switch to a text console (press ctrl-alt-f7 to return to graphics if you wish). Login there (TTY 1) as root. Type "init 3" and enter. There you are, graphics mode killed, you can now install the nvidia driver. Run "startx" to try. Type "init 5" to start graphics mode again. Same as has been for decades. Notice that if you search "nvidia" on our wiki you will find a link with the correct instructions. Read that before asking ;-) Do not modify grub settings to do this. That is a permanent change, you only need a change for the current session. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAleZ+p8ACgkQja8UbcUWM1zjhgD/d5a8h/DebRIjaYYcdbMZRzU0 ezfItIQcDCVKLqZaxN4BAIXIqnn6zHD7HiSeoRH0uCuNTTD56o1rYDiuBbC060db =Fgf7 -----END PGP SIGNATURE-----
On 07/28/2016 08:29 AM, Carlos E. R. wrote:
The procedure for openSUSE is the same as always. Yes, there are new methods, but the old one also works and will work, so most of those old advices will work. Like sax2? :-)
Login there (TTY 1) as root. Type "init 3" and enter. There you are, graphics mode killed, you can now install the nvidia driver. Run "startx" to try. Type "init 5" to start graphics mode again. Same I know about the alternate console but did not know about needing init 3 to kill the server. I will write that in my "tips to remember"
Notice that if you search "nvidia" on our wiki you will find a link with the correct instructions. Read that before asking ;-) I tried that but either I am doing something wrong or the wiki has issues. This is where I should go, right? https://en.opensuse.org/Portal:Wiki I entered nvidia in the search field, top right on black menu bar. I got nothing but but a few pieces of text that looked like a scripting language. I tried "Find a Page" and get zero results.
Do not modify grub settings to do this. That is a permanent change, you only need a change for the current session. got it. thanks
Damon Register -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-08-08 01:40, Damon Register wrote:
On 07/28/2016 08:29 AM, Carlos E. R. wrote:
The procedure for openSUSE is the same as always. Yes, there are new methods, but the old one also works and will work, so most of those old advices will work. Like sax2? :-)
Ha, good catch. Nope, not sax2. Maybe sax3, but it was not finished :-}
Login there (TTY 1) as root. Type "init 3" and enter. There you are, graphics mode killed, you can now install the nvidia driver. Run "startx" to try. Type "init 5" to start graphics mode again. Same I know about the alternate console but did not know about needing init 3 to kill the server. I will write that in my "tips to remember"
It is somewhere in the driver preparation instructions.
Notice that if you search "nvidia" on our wiki you will find a link with the correct instructions. Read that before asking ;-) I tried that but either I am doing something wrong or the wiki has issues.
The wiki has issues. :-/ I used google the other day to find the pages for somebody else, I'll try to find the post. [...] Here: https://en.opensuse.org/SDB:NVIDIA https://en.opensuse.org/SDB:NVIDIA_drivers https://en.opensuse.org/SDB:NVIDIA_troubleshooting http://users.suse.com/~sndirsch/nvidia-installer-HOWTO.html -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Damon Register composed on 2016-07-28 06:56 (UTC-0400):
Is there anyone here with Mint 17 experience along with SuSE experience. I have been trying Mint 17.3 and find myself comparing to what I know with SuSE, I guess since I have worked with that a lot longer.
Mint is a Debian derivative. I installed both 17 and LMDE 2 Betsy (same OS but with a different DE) on one machine. 17 was a full install, and was corrupted by lack of / filesystem freespace not long after installation, so only LMDE works on it any more.
I am installing a new Nvidia 960 video card on a Mint 17.3 system and am running into problems that I once could solve easily. After some Googling and searching this list, I may have some answers but I am hoping that someone here can tell me if I am on the right track.
What gfxcard is the 960 replacing? If whatever the old one was was using a FOSS driver, then the 960 should have worked automagically, unless the FOSS driver for the new (xserver-xorg-video-nouveau is the .deb containing it in Mint; xf86-video-nouveau is the .rpm containing it in openSUSE) was not already installed.
One thing I don't know with either system is how do I get the system to recognize the new card and reconfigure the xserver for the new card? How is this done with SuSE (I haven't tried it yet)? In all my searching so far I haven't found the method for Mint either.
Default behavior on both Debians and openSUSE is there is no configuration to be done. IOW, gfxcard recognition is supposed to be automagically handled. The primary deviation from default behavior results from NVidia gfxcard owners who cannot be satisfied with a 100% FOSS installation, breaking from the default by installing a proprietary video driver that does require manipulation of otherwise unnecessary X configuration. Swapping gfxcards around here is a fairly common occurrence, and simple, because proprietary video drivers are never used here in any Linux distro. As long as the video driver a gfxcard requires is actually installed, X will normally find and use it automagically. With the latest gfxchips that cannot always be expected to work except maybe in Tumbleweed, as there's normally weeks or months long time lag between new hardware release and support in Linux. Given that the 960 launch was 18 months ago, I would expect full FOSS support for it to exist in both 42.1 and TW, but not in 13.2.
I downloaded the 960 driver from Nvidia but the instructions said I have to be in text only with no xserver. I spent a few evenings on that problem with Mint. Most forum suggestions seemed very old and useless for the current Mint.
Search engines often provide stale hits unless directed to limit results to a recent time period. With Google I commonly click on the one year limitation.
The one that finally worked was to tamper with /etc/default/grub, changing three lines so now it boots and stays in text mode and I can run startx if I want to.
I see from this list that systemd has changed the runlevel concept and now the method for SuSE (if I understand correctly) is systemctl set-default multi-user.target Is this correct?
It is if your goal is to make systemd's closest equivalent to "runlevel 3" your default - your preference being to use startx instead of a GUI greeter to launch your X sessions.
Is YaST System->Boot Loader->Boot Loader Options just another way to accomplish that?
It seems that Mint 17 doesn't yet have systemd so am I correct in
Why do you think that? According to distrowatch.com, Mint has been using systemd since v15. LMDE 2 uses it, so I have to think distrowatch is correct about 17.
understanding that for Mint I tamper with /etc/default/grub while for SuSE I use the systemctl method? One forum (don't remember which forum) post that suggested the grub tampering that worked for me said that I must also do the systemctl in addition to the grub tampering. Does SuSE have the /etc/default/grub and if so, would I
That answer depends on your openSUSE version, and which Grub is enabled. That file is owned by Grub2, which has been openSUSE's default for several releases, but not the only possible choice in it.
have to tamper with that in addition to the systemctl?
The "grub tampering" you're referring to must have to do with the NVidia driver's requirement to disable KMS by including nomodeset as a cmdline parameter at boot time. For the Intel, AMD/ATI and NVidia FOSS drivers to work properly, nomodeset must not be present on the kernel cmdline at boot time. There is no distinction between openSUSE and Mint in this regard. -- "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/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thursday, July 28, 2016 3:32:07 PM PDT Felix Miata wrote:
Damon Register composed on 2016-07-28 06:56 (UTC-0400):
Is there anyone here with Mint 17 experience along with SuSE experience. I have been trying Mint 17.3 and find myself comparing to what I know with SuSE, I guess since I have worked with that a lot longer.
Mint is a Debian derivative. I installed both 17 and LMDE 2 Betsy (same OS but with a different DE) on one machine. 17 was a full install, and was corrupted by lack of / filesystem freespace not long after installation, so only LMDE works on it any more.
I am installing a new Nvidia 960 video card on a Mint 17.3 system and am running into problems that I once could solve easily. After some Googling and searching this list, I may have some answers but I am hoping that someone here can tell me if I am on the right track.
What gfxcard is the 960 replacing? If whatever the old one was was using a FOSS driver, then the 960 should have worked automagically, unless the FOSS driver for the new (xserver-xorg-video-nouveau is the .deb containing it in Mint; xf86-video-nouveau is the .rpm containing it in openSUSE) was not already installed.
One thing I don't know with either system is how do I get the system to recognize the new card and reconfigure the xserver for the new card? How is this done with SuSE (I haven't tried it yet)? In all my searching so far I haven't found the method for Mint either.
Default behavior on both Debians and openSUSE is there is no configuration to be done. IOW, gfxcard recognition is supposed to be automagically handled. The primary deviation from default behavior results from NVidia gfxcard owners who cannot be satisfied with a 100% FOSS installation, breaking from the default by installing a proprietary video driver that does require manipulation of otherwise unnecessary X configuration.
Swapping gfxcards around here is a fairly common occurrence, and simple, because proprietary video drivers are never used here in any Linux distro. As long as the video driver a gfxcard requires is actually installed, X will normally find and use it automagically. With the latest gfxchips that cannot always be expected to work except maybe in Tumbleweed, as there's normally weeks or months long time lag between new hardware release and support in Linux.
Given that the 960 launch was 18 months ago, I would expect full FOSS support for it to exist in both 42.1 and TW, but not in 13.2.
I downloaded the 960 driver from Nvidia but the instructions said I have to be in text only with no xserver. I spent a few evenings on that problem with Mint. Most forum suggestions seemed very old and useless for the current Mint.
Search engines often provide stale hits unless directed to limit results to a recent time period. With Google I commonly click on the one year limitation.
The one that finally worked was
to tamper with /etc/default/grub, changing three lines so now it boots and stays in text mode and I can run startx if I want to.
I see from this list that systemd has changed the runlevel concept and now the method for SuSE (if I understand correctly) is systemctl set-default multi-user.target Is this correct?
It is if your goal is to make systemd's closest equivalent to "runlevel 3" your default - your preference being to use startx instead of a GUI greeter to launch your X sessions.
Is YaST System->Boot Loader->Boot Loader Options just another way to accomplish that?
It seems that Mint 17 doesn't yet have systemd so am I correct in
Why do you think that? According to distrowatch.com, Mint has been using systemd since v15. LMDE 2 uses it, so I have to think distrowatch is correct about 17.
understanding that for Mint I tamper with /etc/default/grub while for SuSE I use the systemctl method? One forum (don't remember which forum) post that suggested the grub tampering that worked for me said that I must also do the systemctl in addition to the grub tampering. Does SuSE have the /etc/default/grub and if so, would I
That answer depends on your openSUSE version, and which Grub is enabled. That file is owned by Grub2, which has been openSUSE's default for several releases, but not the only possible choice in it.
have to tamper with that in addition to the systemctl?
The "grub tampering" you're referring to must have to do with the NVidia driver's requirement to disable KMS by including nomodeset as a cmdline parameter at boot time. For the Intel, AMD/ATI and NVidia FOSS drivers to work properly, nomodeset must not be present on the kernel cmdline at boot time. There is no distinction between openSUSE and Mint in this regard.
mint17.x has core ubuntu-14.04 and is not using systemd if it matters :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
emanuel composed on 2016-07-28 14:14 (UTC-0700):
mint17.x has core ubuntu-14.04 and is not using systemd if it matters :)
That does not seem to be an entirely accurate statement. I booted a 17.3 DVD: $ uname -a Linux mint 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:37:25 UTC 2015 i686 i686 i686 GNU/Linux $ cat /etc/linuxmint/info RELEASE=17.3 CODENAME=rosa EDITION="MATE 32-bit" DESCRIPTION="Linux Mint 17.3 Rosa" DESKTOP=MATE TOOLKIT=GTK NEW_FEATURES_URL=http://www.linuxmint.com/rel_rosa_mate_whatsnew.php RELEASE_NOTES_URL=http://www.linuxmint.com/rel_rosa_mate.php USER_GUIDE_URL=help:linuxmint GRUB_TITLE=Linux Mint 17.3 MATE 32-bit $ dpkg -l | egrep 'upstart|systemd|sysvinit' ii upstart 1.12.1-0ubuntu4.2 i386 event-based init daemon ii libpam-systemd:i386 204-5ubuntu20.15linuxmint1 i386 system and service manager - PAM module ii libsystemd-daemon0:i386 204-5ubuntu20.15linuxmint1 i386 systemd utility library ii libsystemd-login0:i386 204-5ubuntu20.15linuxmint1 i386 systemd login utility library ii systemd-services 204-5ubuntu20.15linuxmint1 i386 systemd runtime services ii systemd-shim 6-2bzr1 i386 shim for systemd ii sysvinit-utils 2.88dsf-41ubuntu6.2 i386 System-V-like utilities -- "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/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday, July 29, 2016 12:16:56 AM PDT Felix Miata wrote:
emanuel composed on 2016-07-28 14:14 (UTC-0700):
mint17.x has core ubuntu-14.04 and is not using systemd if it matters :)
That does not seem to be an entirely accurate statement. I booted a 17.3 DVD:
$ uname -a Linux mint 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:37:25 UTC 2015 i686 i686 i686 GNU/Linux
$ cat /etc/linuxmint/info RELEASE=17.3 CODENAME=rosa EDITION="MATE 32-bit" DESCRIPTION="Linux Mint 17.3 Rosa" DESKTOP=MATE TOOLKIT=GTK NEW_FEATURES_URL=http://www.linuxmint.com/rel_rosa_mate_whatsnew.php RELEASE_NOTES_URL=http://www.linuxmint.com/rel_rosa_mate.php USER_GUIDE_URL=help:linuxmint GRUB_TITLE=Linux Mint 17.3 MATE 32-bit
$ dpkg -l | egrep 'upstart|systemd|sysvinit' ii upstart 1.12.1-0ubuntu4.2 i386 event-based init daemon ii libpam-systemd:i386 204-5ubuntu20.15linuxmint1 i386 system and service manager - PAM module ii libsystemd-daemon0:i386 204-5ubuntu20.15linuxmint1 i386 systemd utility library ii libsystemd-login0:i386 204-5ubuntu20.15linuxmint1 i386 systemd login utility library ii systemd-services 204-5ubuntu20.15linuxmint1 i386 systemd runtime services ii systemd-shim 6-2bzr1 i386 shim for systemd ii sysvinit-utils 2.88dsf-41ubuntu6.2 i386 System-V-like utilities
tried some of those systemd tools yet? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/28/2016 03:32 PM, Felix Miata wrote:
Mint is a Debian derivative. I installed both 17 and LMDE 2 Betsy (same OS but gets confusing. I could be wrong but I got the impression that mint was derived from Ubuntu which is from Debian. Is that not correct?
What gfxcard is the 960 replacing? If whatever the old one was was using a it is an ATI that was OEM in an HP computer. It doesn't have much of any marking on it and since it is no longer in the computer, I don't have an easy way to check how it was identified. I think it was something like 6250
FOSS driver, then the 960 should have worked automagically, unless the FOSS driver for the new (xserver-xorg-video-nouveau is the .deb containing it in Mint; xf86-video-nouveau is the .rpm containing it in openSUSE) was not already installed. I bet that might have been the reason it didn't work. I guess I should have checked for its presence before replacing the old one. Anyway, the new Nvidia seems to be working ok now with the Nvidia proprietary driver on the host system. At this point I have no idea if the problems I am having with Virtualbox guest systems is at all related. I don't think I mentioned it in my original post but Virtualbox was the reason I wanted to get a newer and better card because in the process of experimenting, I began to think the old card wasn't well supported.
Default behavior on both Debians and openSUSE is there is no configuration to be done. IOW, gfxcard recognition is supposed to be automagically handled. Meaning that the new card will be detected and the xserver will be reconfigured?
The primary deviation from default behavior results from NVidia gfxcard owners who cannot be satisfied with a 100% FOSS I started with the FOSS but it seemed to be not behaving well (it appeared to be be in a low res fbdev type of operation). I guess I should have written the errors I saw for future reference.
Swapping gfxcards around here is a fairly common occurrence, and simple, because proprietary video drivers are never used here in any Linux distro. Where is "here"? your house, SuSE community, linux users in general? So you are saying that generally many don't like the proprietary?
the latest gfxchips that cannot always be expected to work except maybe in Tumbleweed, as there's normally weeks or months long Tumblweed is what I started with while trying to get SuSE as a Virtualbox guest.
Given that the 960 launch was 18 months ago, I would expect full FOSS Maybe I will try the Leap next.
It is if your goal is to make systemd's closest equivalent to "runlevel 3" your default - your preference being to use startx instead of a GUI greeter to launch your X sessions. OK, thanks
It seems that Mint 17 doesn't yet have systemd so am I correct in
Why do you think that? According to distrowatch.com, Mint has been using I am certainly not an expert on that but I wonder why they say that? I "think that" because I read somewhere in one of the forums that 17 is not yet using systemd.
systemd since v15. LMDE 2 uses it, so I have to think distrowatch is correct about 17. While it seems that $ dpkg -l | egrep 'upstart|systemd|sysvinit' might show some things related to systemd, it might not yet really be there? Is not the existence of systemctl a key part of having systemd (I am really new on that so I don't know)? I get systemctl: command not found
That answer depends on your openSUSE version, and which Grub is enabled. I started with the latest Tumbleweed but since that is almost totally broken (for me), I will try the Leap 42.1.
have to tamper with that in addition to the systemctl?
The "grub tampering" you're referring to must have to do with the NVidia driver's requirement to disable KMS by including nomodeset as a cmdline I don't know/remember if that was required or if it is just a need to not have the xserver running.
parameter at boot time. For the Intel, AMD/ATI and NVidia FOSS drivers to work properly, nomodeset must not be present on the kernel cmdline at boot time. There is no distinction between openSUSE and Mint in this regard. That is good to know. Thanks for the info.
Thanks to everyone for the help on this one. The host system now seems to be working well with the Mint 17.3 and the new Nvidia. Now I am having a lot of trouble with getting other OS including SuSE to work as a Virtualbox guest. Tumbleweed won't even run in graphical mode so I will make a separate post on that. Damon Register -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Damon Register composed on 2016-08-07 20:25 (UTC-0400):
Felix Miata wrote:
Mint is a Debian derivative. I installed both 17 and LMDE 2 Betsy (same OS but
gets confusing. I could be wrong but I got the impression that mint was derived from Ubuntu which is from Debian. Is that not correct?
Without Debian, *buntu would not exist. Mint depends on Debian for existence, but indirectly, with *buntu as a pass-through. Debian has quite a few other derivative distros. Debian depends directly on none of them.
What gfxcard is the 960 replacing? If whatever the old one was was using a
it is an ATI that was OEM in an HP computer. It doesn't have much of any marking on it and since it is no longer in the computer, I don't have an easy way to check how it was identified. I think it was something like 6250
Likely HD6250. :-)
FOSS driver, then the 960 should have worked automagically, unless the FOSS driver for the new (xserver-xorg-video-nouveau is the .deb containing it in Mint; xf86-video-nouveau is the .rpm containing it in openSUSE) was not already installed.
I bet that might have been the reason it didn't work. I guess I should have checked for its presence before replacing the old one. Anyway, the new Nvidia seems to be working ok now with the Nvidia proprietary driver on the host system. At this point I have no idea if the problems I am having with Virtualbox guest systems is at all related. I don't think I mentioned it in my original post but Virtualbox was the reason I wanted to get a newer and better card because in the process of experimenting, I began to think the old card wasn't well supported.
Default behavior on both Debians and openSUSE is there is no configuration to be done. IOW, gfxcard recognition is supposed to be automagically handled.
Meaning that the new card will be detected and the xserver will be reconfigured?
Depends on the definition of "configured", and the distro. For quite some years now in most distros, the default manor of configuring Xorg is automagically, that is, without any preconfiguration registered in /etc/X11/xorg.con*. The proprietary NVidia driver is probably the biggest exception to the general rule. Mageia through v5 at least has been a distro that inexplicably includes /etc/X11/xorg.conf apparently by default.
Swapping gfxcards around here is a fairly common occurrence, and simple, because proprietary video drivers are never used here in any Linux distro.
Where is "here"? your house, SuSE community, linux users in general?
Under my roof there are dozens of functional machines, and hundreds of OS installations.
So you are saying that generally many don't like the proprietary?
Who likes it or not I can't say. Linux does have some vocal purist adherents. I've always found it unnecessary to use non-FOSS drivers with any of my Linux installations. I've probably spent little more than $100 in my lifetime on NVidia hardware and several times that on ATI/AMD. Intel is hard to count because it comes as part of so many motherboards, but over the past decade's new offerings I don't think I've felt compelled in any case to add a PCIe card for performance reasons, but only for testing and QA.
It seems that Mint 17 doesn't yet have systemd so am I correct in
Why do you think that? According to distrowatch.com, Mint has been using
I am certainly not an expert on that but I wonder why they say that? I "think that" because I read somewhere in one of the forums that 17 is not yet using systemd.
Among Debian and its derivatives there remains a lot of derision of systemd, besides options. Some versions offer a choice. so it can be hard to say whether any particular one does or doesn't "have" it. According to Distrowatch, which lists for it neither sysvinit nor upstart, Mint has included systemd in all releases 15 & up, after April 2013.
systemd since v15. LMDE 2 uses it, so I have to think distrowatch is correct about 17.
While it seems that $ dpkg -l | egrep 'upstart|systemd|sysvinit' might show some things related to systemd, it might not yet really be there? Is not the existence of systemctl a key part of having systemd (I am really new on that so I don't know)? I get systemctl: command not found
CNF happens here too. *buntu uses upstart. AFAIK neither sysvinit nor systemd are options in *buntu releases of late. Mint 17.3 does have upstart, but on my only installation of it it also has systemd-shim and systemd-services, so it looks like one of the confusing hybrids. -- "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/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
08.08.2016 06:34, Felix Miata пишет:
CNF happens here too. *buntu uses upstart. AFAIK neither sysvinit nor systemd are options in *buntu releases of late.
Ubuntu 16.04 definitely switched to systemd, I believe this actually happened earlier (I am interested in LTS mostly). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 8/7/2016 11:39 PM, Andrei Borzenkov wrote:
Ubuntu 16.04 definitely switched to systemd, I believe this actually happened earlier (I am interested in LTS mostly). I downloaded that last night along with the latest Leap. I want to try both with Virtualbox to compare the experiences.
Damon Register -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
Damon Register -
Damon Register -
emanuel -
Felix Miata