2016-06-13 11:11 keltezéssel, jdd írta:

...

Le 13/06/2016 11:08, Albert, Oszkó a écrit :

...

Hi all,

I need your advice and help. I got a new laptop at my workplace, with the cheapest version of Win 10 pre-installed. It has a 16 GB SDD and a 1TB HDD. I would like to change it to Leap, and have my Win7 in a virtualbox. I have never used an SSD before. Is that 16 GB sufficient to to put / onto it, and have /home on HDD? What filesystems do you suggest?

yes.

keep ext4 and avoid btrfs

I have the same (with a bit more: 24Gb ssd)

jdd

Thanks,

I am trying to partiton it properly

Albert

Le 13/06/2016 11:21, Albert, Oszkó a écrit : the ssd is probably used by windows for fast start. I don't remember if I did something to disable this, probably not At first I tried to use the ssd as bcache, but it's much too complicated, so I simply install root on it - it's very fast :-)) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 13/06/2016 16:07, Albert, Oszkó a écrit :

a feeling that it is not fast enough, I mean what could be expected from the hardware.

my i3 asus works like a charm with any opensuse :-( jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 06/13/2016 11:31 AM, Christopher Myers wrote:

...

...

...

...

jdd 06/13/16 9:35 AM >>> Le 13/06/2016 16:07, Albert, Oszkó a écrit :

...

...

a feeling that it is not fast enough, I mean what could be expected from the hardware.

...

my i3 asus works like a charm with any opensuse :-(

My HP TC4400 works beautifully too (even better than the Windows XP tablet edition it was built for,) and it's almost a decade old...

I have a HP that is actually a relabelled Compaq design from shortly after HP took over Compaq; that's what, just after the turn of the century. Being a 32-bit machine it can’t run 64-bit LEAP, but it runs 13.2 on a 10G "/" partition on an 80G drive with 1.25G of memory and acts as my database/Maria server for a number of web services.

From the moment I bought it new, for what now, seems an incredible price but was a bargain at the time, its been running Linux, initially Mandrake Linux, or "Mandriva" since 2005, but I switched it to openSuse when EdgdeIT, a subsidiary of Mandriva that was producing the freeware, folded in 2011 and the developers fled to make Mageia. Yes, the laptop was built for W/XP, and dual booted until I converted to openSuse and LVM.

So "not fast enough" and "adequate disk" *may" be a problem with LEAP, but if you go with 13.2/Evergreen I can't see how it will be. Try that as reassurance. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- 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-06-13 a las 18:40 +0200, jdd escribió:

Le 13/06/2016 18:20, Anton Aylward a écrit :

...

So "not fast enough" and "adequate disk" *may" be a problem with LEAP, but if you go with 13.2/Evergreen I can't see how it will be. Try that as reassurance.

That would be 13.1, because 13.2 is not an Evergreen version.

But one must understand than Leap 42.1 is a *stable* Long time life version, so using more modern hardware may be a bit harder, as it is for Debian Weezy

I don't have it clear in what sense 42.1 is an LTS, because it seems that we have to upgrade to 42.2. 42.1 is mantained for 2 years only, I understand. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlde50oACgkQja8UbcUWM1wj8wD6AuawzGjXfku3BgnC58Sp7XiZ a8Duo4WNWDONsiD/ii4A/jLE4zsrNBJ4+VcLYjvRX9ChaM6KYYJqxwDhRV9qfp40 =CA1A -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2016-06-13 a las 19:18 +0200, Yamaban escribió:

On Mon, 13 Jun 2016 19:03, Carlos E. R. wrote:

...

...

But one must understand than Leap 42.1 is a *stable* Long time life version, so using more modern hardware may be a bit harder, as it is for Debian Weezy

I don't have it clear in what sense 42.1 is an LTS, because it seems that we have to upgrade to 42.2. 42.1 is mantained for 2 years only, I understand.

There is a little missunderstanding going on. Leap 42.1 is based on SLE 12 SP1, and Leap 42.2 will be based on SLE12 SP2.

Yes, I know. About ⅓ is taken from SLES, the rest comes from tumbleweed.

The keyword here is "based" not identical. Leap is based on SLE which in turn is LTS.

Ah. So ⅓ is an LTS, the rest is not :-)

Tumbleweed gets every kernel-release. Leap gets the LTS kernel of the year.

Well, there was some recent talk about which kernel to use. Was it finally decided to use the kernel from SLE 12 SP2?

So, if your Hardware is based on a CPU / chipset that is less than a year old, there can be trouble with Leap, such "new / fresh" Hardware is a case for Tumbleweed, at least until the next Leap release.

I know.

Here, in this case, I'd suggest either 13.2 (which is NOT Evergreen), or Tumbleweed the get the box up and running to satisfaction, at least until the next Leap release (in November, AFAICT)

Yes, I know that was the suggestion. Which will push out a percent of users. I suggested an alternate non fully suported kernel from a more recent branch for those people. I don't have the skills to do such a thing myself, except take a KOD and build locally, for me only. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlde7xAACgkQja8UbcUWM1zVRgD/XRYoJZdZ08G/OWmGIuB393Ox XMrLSwh8tZWfr8AmgAYBAIAroMcfPuEPvW4t3ZKRzbdx2KSex3eNxingckgKLd3C =uo2w -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-06-13 20:22, jdd wrote:

Le 13/06/2016 19:36, Carlos E. R. a écrit :

...

Ah. So ⅓ is an LTS, the rest is not :-)

I don't see it exactly like this.

even SLE 12 SP2 will be very conservative.

what I mean is that I expect Leap 42.x to be LTS. Every change in "x" (1->2...) should be very simple and harmless, like service pack for windows, so somebody using Leap should never have to "reinstall" as we often did from 13.1 to 13.2 for example, so may be we have to be carefull to go from 42 to 43?

How would a service pack for Leap be applied, different YaST module? But it would only apply to the core that comes from SLE. The current kernel doesn't. There are many components that don't come from SLE, like I think the entire KDE. That would be a normal upgrade, like from 13.1 to 13.2.

anyway we will have more info at OSC16 (I go there mostly for that), and for sure in November when going one step on.

Ok, we'll find out then :-) No, I can't go. I'll have to watch via youtube or similar. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAldfFhUACgkQja8UbcUWM1zPfAD/exEEU8KBs3T+6C1dTOwypI1Z TveCS81YAc4WcYEV6zQA/3HADwVl4H2MGbnsDF8FflyxyFoJjI004NRLBOdFMfKZ =PJqf -----END PGP SIGNATURE----- -- 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-06-16 a las 10:21 +0200, Werner Flamme escribió:

Carlos E. R. [13.06.2016 22:22]:

...

But it would only apply to the core that comes from SLE.

How would I know before the update procedure is known?

No, a package coming from the TW side would not have the same warranty level as one coming from the SLES side, no matter what procedure is used to apply it. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAldiZVMACgkQja8UbcUWM1wMLAD8CiKLSqYO5otTUHxP+3Sczd67 1h9vurST751IVp4BZkEBAIJhitfgHD7g2319MH3QLbZn+DZvtguWi4kMjXymdFLD =+z/1 -----END PGP SIGNATURE-----

On Mon, Jun 13, 2016 at 1:36 PM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

El 2016-06-13 a las 19:18 +0200, Yamaban escribió:

...

On Mon, 13 Jun 2016 19:03, Carlos E. R. wrote:

...

...

...

But one must understand than Leap 42.1 is a *stable* Long time life version, so using more modern hardware may be a bit harder, as it is for Debian Weezy

I don't have it clear in what sense 42.1 is an LTS, because it seems that we have to upgrade to 42.2. 42.1 is mantained for 2 years only, I understand.

The old model was 2N+2 (ie. support for 2 releases, plus 2 months of extended overlapping support.) If a release every 8 months (as was the hope), that meant 18 months of support. The new model is N+6 (i.e. 1 release at a time, plus 6 months of overlapping support). The Leap release schedule appears to be once a year, so that too is every 18 months.

...

There is a little missunderstanding going on. Leap 42.1 is based on SLE 12 SP1, and Leap 42.2 will be based on SLE12 SP2.

Yes, I know. About ⅓ is taken from SLES, the rest comes from tumbleweed.

...

The keyword here is "based" not identical. Leap is based on SLE which in turn is LTS.

Ah. So ⅓ is an LTS, the rest is not :-)

...

Tumbleweed gets every kernel-release. Leap gets the LTS kernel of the year.

Maybe. It is only known 42.1 got the spring 2016 LTS kernel. 42.2 will get the 2017 LTS kernel. No commitment yet about the 42.3 kernel.

Well, there was some recent talk about which kernel to use. Was it finally decided to use the kernel from SLE 12 SP2?

Yes, its a done deal.

...

So, if your Hardware is based on a CPU / chipset that is less than a year old, there can be trouble with Leap, such "new / fresh" Hardware is a case for Tumbleweed, at least until the next Leap release.

I know.

...

Here, in this case, I'd suggest either 13.2 (which is NOT Evergreen), or Tumbleweed the get the box up and running to satisfaction, at least until the next Leap release (in November, AFAICT)

Yes, I know that was the suggestion. Which will push out a percent of users.

I suggested an alternate non fully suported kernel from a more recent branch for those people. I don't have the skills to do such a thing myself, except take a KOD and build locally, for me only.

The Leap 42.2 kernel is available in at least 2 repos. Since it will be the SLE 12 SP 2 kernel too, I assume bugzilla's against that kernel will get acted on. https://build.opensuse.org/project/show/Kernel:openSUSE-42.2 http://download.opensuse.org/repositories/home:/gregfreemyer:/Kernel:/LTS/st... That second project is mine and until the end of the year should be the same as the Kernel:openSUSE-42.2 project. When the 2017 LTS kernel comes out, I will try to update my Kernel:LTS project with it, but no promises.

- -- Cheers Carlos E. R.

Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, Jun 13, 2016 at 6:31 PM, Carlos E. R. wrote:

...

...

...

Tumbleweed gets every kernel-release. Leap gets the LTS kernel of the year.

Maybe. It is only known 42.1 got the spring 2016 LTS kernel. 42.2 will get the 2017 LTS kernel.

The 2017 LTS kernel? That's wonderful. But...

...

No commitment yet about the 42.3 kernel.

...

Well, there was some recent talk about which kernel to use. Was it finally decided to use the kernel from SLE 12 SP2?

Yes, its a done deal.

Then I'm confused, because above you said it was the 2017 LTS kernel :-?

Typo? Would it be the 2016 LTS kernel? :-?

Double typo; 42.1 got the spring 2015 LTS kernel 42.2 will get the 2016 LTS kernel Greg -- Greg Freemyer www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Op maandag 13 juni 2016 16:07:11 CEST schreef Albert, Oszkó:

2016-06-13 12:04 keltezéssel, Knurpht - Gertjan Lettink írta:

...

Op maandag 13 juni 2016 11:08:52 CEST schreef Albert, Oszkó:

...

Hi all,

I need your advice and help. I got a new laptop at my workplace, with the cheapest version of Win 10 pre-installed. It has a 16 GB SDD and a 1TB HDD. I would like to change it to Leap, and have my Win7 in a virtualbox. I have never used an SSD before. Is that 16 GB sufficient to to put / onto it, and have /home on HDD? What filesystems do you suggest?

Thanks,

Albert

Yup, I'd do it that way with XFS for both / and /home The default, btrfs, will not have enough diskspace with the 16GB you have.

You are right, 16 GB was not enough. I managed to configure it with ext4 on both / on SSD and /home on HDD. I am struggling with the nvidia driver now. Installing from the nvidia repo did not let me to set resolution it is 1366x766. Installation from the geforce site led to the black screen with an underscore inthe upper left corner. And I forgot how I got rid of it. This series of ASUS K501 is a great suck with opensuse. This is with core i5, mine at home is core i7, with 940m and 950m GPU (and also an intel, I think). Difficulties with networking, GPU, touchpad does not work. logout, reboot, shutdown needs minutes, if work at all. And I have a feeling that it is not fast enough, I mean what could be expected from the hardware.

Regards, Albert

This probably has an optimus config ( Intel + NVIDIA ) and that's not going to work with the default NVIDIA blob install. You need either bumblebee, or suse- prime. Or, use bbswitch to turn off the NVIDIA completely. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org