I thought that was succinct. But apparently I have to add some letters to make it a valid post. So here are some: QWERTYUIOP
OpenSUSE has rolled up its Factory and Tumbleweed into a single project that will carry the name Tumbleweed from November 4. The devs had created a measure of confusion among users by elevating Factory – once an indicator of the current unstable code-cut – to the same rolling-release status as Tumbleweed. As Linuxveda writer …
Have been running 13.2 from beta to RC1 here on an old ( circa 2007 ) dual core Samsung R60 laptop that I use for testing, a few niggles during beta but the RC is as stable as my 13.1 install, just one or two very, very minor glitches ( Plymouth ) but does not affect anything.
Give it a try, or wait a week for the GM.
I'll pitch and say I use it on everything of mine - partly because my lab (and the supercomputers) use it, but because it has a "stable edge" to it.
I am still on 12.2, and I'm getting ready to make a change....but so far it has been rock solid with reboots every 6 months for the desktop (I have 32GB of memory and that is not enough, apparently....).
The point about Tumbleweed and Factory was that it used to be "update and bleeding edge". But opensuse has done the work to make "bleeding edge" into just an update. Hence, you only need one.
My biggest problem with ALL of this is that 2 things make updates "dangerous". Changing the kernel (rebooted needed) or restarting the desktop (session restart is not quite perfect....).
Other than that, the delta-rpms make updating very quick. And I have backported many packages using "rpmbuild -bb" for the various security scares we have had this year...
Software doofus here. Tried to install Suse a couple of months ago, but they package the distro differently so I could not use the usual .iso tools to make a bootable usb. When I tried Suse's tool I got permission problems on two different Windows machines with two different Win OS. Gave up and made a Mint usb. Shame because the machine I wanted to put it on had an outdated Suse install and I'd liked it.
Boot with a live CD (SUSE or any other) and make sure you can use the file browser to see the ISO file wherever it is. Then open a command line. Plug your USB stick (make sure you can browse its contents) and execute a dmesg command to see where in /dev your USB drive is. Usually there will be at the end of dmesg output a message saying where a USB device was detected in the form of
dd if=<path to your ISO file> of=<path to your USB device>
(you may need to be root to do this) And once it finishes you should have a bootable USB drive.
Mind you, two important warnings. The contents of the USB device will be obviously lost when you do this. But be EXTRA CAREFUL to get the <path to your USB device> correct because if you get it wrong you could overwrite any other partition, including your hard disk.
Issues with making a bootable disk are not exclusive of Suse, I've experienced them with lots of other distros.
And yes, it is a shame to have to do these tricks just to create a bootable drive.
Biting the hand that feeds IT © 1998–2019