I’ve installed openSuse 8 and 10 on laptops and desktops that also had Windows installed. All of those attempts went…well…let’s say it was a trial and I’d spend a day trying to get things to work. That’s just the system and didn’t include Apache, MySQL, PHP, Samba, printer support, and the other things that makes a computer useful. I’m not a sysadmin, nor do I want to be.
So, it was with a lot of trepidation when I decided to upgrade. I had plenty of ibuprofen and beer ready.
I bought a new computer and since my son in law and step-son had their hard drives crash, I decided to make an old desktop computer a file server networked to two laptops and two desktops. One laptop was pure Vista 64 (no dual boot), one desktop was Vista 32 (dual boot), and two other desktops were going to have Windows 7 dual boot.
So… off I went.
WOW! 11.2 installed flawlessly on ALL of the computers! Even GRUB worked flawlessly! Printers - no problem - USB and networked. Samba, the problem was mine. Apache, MySQL, PHP, were installed using Yast and with some time figuring out configurations and new versions my website is up and running. Much, much faster than installing those the manual way.
Congratulations to the openSuse team for all of your hard work and dedication! You’ve done a super job with 11.2 so I guess it must have been me. I must have done something wrong
Two questions for you experts:
On the file server I have a BIOS RAID. openSuse sees it as two different HDs. I have no idea what type of MB it is. It’s a Gateway computer bought at Best Buy. When I shutdown openSuse I get a segment fault. Something to the effect RAID isw_cgfbhigiiji_Backups1 is not active. Hasn’t happened all the time, just twice. Any ideas?
I use another desktop for development. I’ve been switching sessions a lot between user and root adjusting configuration files for Apache and MySQL. Twice it’s done a ‘soft’ reboot staying in Linux, but I need to re-log in again and have lost all of my open applications. Any ideas?
All-In-All, a real sweet job installing 11.2! Thanks!
Is there a reason why you have BIOS RAID? If you want to run RAID under Linux, you should rather setup a software RAID (you can do that in YaST during install) and use either SATA or AHCI mode in your BIOS.
You don’t need to switch sessions to configure Apache and MySQL. You can use either sudo + command
or **su ** to do things as root while logged in as user.
You don’t need to reboot to test your configuration. Just restart the services with
**sudo service apache2 restart
sudo service mysql restart
**
Do not understand this. Do you really mean that you log in as root? The main sin in any Unix/Linux system. SDB:Login as root - openSUSE
And as side effect, when you do not log in as root, you do not have to log out as user. BTW you can log in as usera and userb and userc (and thus also as root if that would be an intelligent option) all at the same time. No need to log out. Use the Change User option from the main menu, or from a screen locked session.
and, in the end decided that anyone who used both “openSuse 8” and
“openSuse 10” on a laptop; and had a “11.2 installed flawlessly”
experience on four (or six–i lost count) mix of desk- and lap-top
computers (with different graphics adapters??) had to know the way
to use root powers absolutely 100% correctly–else we would have heard
from him before yesterday…
at least once…
i have to snicker as i think maybe his post is a practical joke: he is
gonna wait until we tell him how to fix the intermittent RAID
problem and then laugh at our childish trouble shooting abilities…
hopefully it will do it without coming back and publically laughing in
our face, to shame us…
I use bios raid because that system is dual-boot with Windows. I clicked on restart to boot back into Windows and that’s when the seg faults occurred.
Log in, log out. I probably wasn’t clear. I log in as a user then create another session as root to do root stuff. I will then switch session back to the user, find out I didn’t do something right and switch back to the root session. I don’t actually “Log out” then “Log in”. Sorry for the confusion.
Switching session to root, rather than setup sudo for each possible need, suited me better because I had flexibility. I could change default.config for apache2, create a different directory for webfiles and change its permissions,etc, etc, etc. Once things are set up correctly I rarely use root.
My post wasn’t/isn’t a practical joke. Over the last 10-12 years I have installed those versions of Suse. I’m not a sysadmin and don’t want to be. Once I get things running I do web development and other programming stuff for the most part. 11.2 is the most error free and easiest so far.
I start and stop apache and mysql using runlevel services in Yast.
I saw another poster complaining of sudden soft reboots. I’m probably going to post there and give my system information.
But you still log in as root, in the GUI if I understand you. That is still amajor sin. You should open terminal and use
su -
when you want a root CLI at hand. No need for sudo when you do not like it (I do not use it myself).
But never log in into the GUI as root. It is not only dangerous, but also useless. Either you need a GUI tool as root (YaST, File manager in system manager mode, konsole in system manager mode) and those are available from the user GUI. Or you need the CLI as root and then you use su - or the konsole in system management mode from the menu (which is in fact the same as a normal terminal and su -).
All take a gander at this.
I’ll bet you don’t have an actual raid or raid configuration. I’ll bet that you have one hard drive. This would mean openSUSE did this as a software raid. Any OS would see a raid as multiple hard drives. This purpose of raid is to have a backup of your data so that if the disk fails, you have a backup. The segmentation fault is just to let you know that the backup that the raid is supposed to be doing, isn’t working. Take a look at this. It’ll help explain this subject better. How to install openSUSE on software RAID - openSUSE
As others have said, logging in directly as root is extremely bad. Using terminal is certainly not slow. Awkward, if your not used to it, yes. But you need to learn to do things the right way.
Settle down for a minute, read some documentation, slow down and do it right. You don’t have to be a sysadmin, but you should know how to do what your doing.
That’s a good reason … but what will you do if your mainboard dies? Those BIOS raids (also called ‘faked’ raids) are not much faster than Linux soft raids and make data recovering under circumstances much more difficult.
You could make a separate fileserver running openSUSE and soft raid and export filesystems, either with samba to other Windows machines or with NFS to other Linux clients. Or you could of course work on the fileserver yourself.
Or you could have Windows in a virtual machine, importing samba shared drives from the host … and do a bunch of things (maybe not Eclipse though … with 4GB of RAM or less).
Below is my fstab. /windows/C is the raid disk and I can rw to it using Samba and using NFS from other computers. Still don’t get the seg fault but if it should happen again I’ll be posting somewhere.
Did you notice, that in your own fstab entry the device ID is the same. What is different is the partitions. You have a simulated raid. A raid via partitions, not actual hard disks.
First you have the partitions for Linux.
The rest is not relevant to the hard drive, at least for what we are discussing. Now notice this segment of the fstab.
/dev/disk/by-id/ata-WDC_WD5000AAKS-00YGA0_WD-WCAS81278582
and how that in each instance, it is the same. It is after the device ID, where things get different.
/dev/disk/by-id/raid-isw_cgfbigiiji_Backups
after I posted. I did a Google search, then I narrowed it down. A basic Google search shows isw raid has is a fake raid and has problems on other distros as well. Ubuntu and Fedora showed up as some. When I narrowed it down to openSUSE, I saw bug reports and feature requests. isw raid site:opensuse.org - Google Search
