Re: [opensuse] System not starting!
Hi! System Opensuse 13.1 Kernel 3.11 Kde Desktop graphics nvidia optimus running with bumblebee. Actually i do not think, that it is a graphic issue, insofar as nothing has changed in the last few days and the splash screen with the opensuse chameleon and the flower is showing up, so the system is loading some stuff but hangs up somewhere ...but i might be worng on this ... I meant, that the system is hanging just before the second start screen comes, where there is the box with the filesystem, network kde etc. Actually i do think that i might have changed some stuff in /etc/sysctl editor in yast or with regard to the runlevels init.d , but not being aware of it. Console...That is what is most problematic - I can not even log in into the rescue console or any other console (CTRL-ALT-F1/F2), i can just watch the system starting up and hanging exactly after server 389 is reached... The script was just a small bash script with two lines like this exec=/usr/bin/unison -batch Thanks for help! Benjamin. Gesendet: Mittwoch, 23. April 2014 um 08:26 Uhr Von: "Carl Hartung" <opensuse@cehartung.com> An: opensuse@opensuse.org Betreff: Re: [opensuse] System not starting! Hi Benjamin, Questions interspersed... On Wed, 23 Apr 2014 09:40:05 +0200 Benjamin Draxlbauer wrote:
Hi everyone! I have a serious problem...Since yesterday my system hangs up
Please describe 'system' ~ architecture, desktop environment, versions and any special graphics card (nVidia, etc.) or other relevant hardware (e.g. RAID)
will start up and does not enter... Actually booting works and i can also see the start screen, but not the screen when the modules and kde is loaded. This is even the same problem with the recovery mode.
I'm interpreting this to mean the usual graphical log-in greeter does not appear. Is this correct? Please confirm you're able to log into a console.
I took a look inside zypper log if something has been changed - via a life usb system- but nothing which should concern the system. I also took a look at /var/log/messages but also there seems to be no entry with regard to the problem.
What might be the problem is that i was trying to get a small script working which should sync some folders...
If it's really a. small script (only several lines long,) share it here (obfuscate any sensitive details) and please explain, briefly but precisely, what you intend the script to do.
i placed this in /etc/init.d and made it executeable and made symbolic links to this script in rc0.d and rc6.d. That is all. I already deleted the files, but still the same problem...
my system hangs up at the point directly after the server directory 389 is reached and is marked with the green OK in the startup screen...Unfortunately I also do not know more... Thanks for help - Benjamin!
Thanks & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 23 Apr 2014 10:58:59 +0200 Benjamin Draxlbauer wrote:
Hi! System Opensuse 13.1 Kernel 3.11 Kde Desktop graphics nvidia optimus running with bumblebee.
Actually i do not think, that it is a graphic issue, insofar as nothing has changed in the last few days and the splash screen with the opensuse chameleon and the flower is showing up, so the system is loading some stuff but hangs up somewhere ...but i might be worng on this ...
I meant, that the system is hanging just before the second start screen comes, where there is the box with the filesystem, network kde etc. Actually i do think that i might have changed some stuff in /etc/sysctl editor in yast or with regard to the runlevels init.d , but not being aware of it.
Console...That is what is most problematic - I can not even log in into the rescue console or any other console (CTRL-ALT-F1/F2), i can just watch the system starting up and hanging exactly after server 389 is reached...
The script was just a small bash script with two lines like this
exec=/usr/bin/unison -batch
Thanks for help! Benjamin.
Hi Benjamin, Thank you for clarifying your environment. Okay, you were attempting to invoke unison (presumably to synchronize something, somewhere) but '-batch' is obfuscating important details. We need to know precisely the exact commands and arguments that were invoked, whether directly or by inclusion through '-batch'. regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I called the file "Sync" and put it in init.d with the following content: #!/bin/sh exec=/usr/bin/unison myprofile -batch exec=/usr/bin/unison myprofile2 -batch That is all i put into the script and rendered it executeable with chmod -x After that i built the symlinks to rc.0 and rc.6. That is all i did there. Gesendet: Mittwoch, 23. April 2014 um 11:30 Uhr Von: "Carl Hartung" <opensuse@cehartung.com> An: opensuse@opensuse.org Betreff: Re: [opensuse] System not starting! On Wed, 23 Apr 2014 10:58:59 +0200 Benjamin Draxlbauer wrote:
Hi! System Opensuse 13.1 Kernel 3.11 Kde Desktop graphics nvidia optimus running with bumblebee.
Actually i do not think, that it is a graphic issue, insofar as nothing has changed in the last few days and the splash screen with the opensuse chameleon and the flower is showing up, so the system is loading some stuff but hangs up somewhere ...but i might be worng on this ...
I meant, that the system is hanging just before the second start screen comes, where there is the box with the filesystem, network kde etc. Actually i do think that i might have changed some stuff in /etc/sysctl editor in yast or with regard to the runlevels init.d , but not being aware of it.
Console...That is what is most problematic - I can not even log in into the rescue console or any other console (CTRL-ALT-F1/F2), i can just watch the system starting up and hanging exactly after server 389 is reached...
The script was just a small bash script with two lines like this
exec=/usr/bin/unison -batch
Thanks for help! Benjamin.
Hi Benjamin, Thank you for clarifying your environment. Okay, you were attempting to invoke unison (presumably to synchronize something, somewhere) but '-batch' is obfuscating important details. We need to know precisely the exact commands and arguments that were invoked, whether directly or by inclusion through '-batch'. regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 23 Apr 2014 11:36:23 +0200 Benjamin Draxlbauer wrote:
I called the file "Sync" and put it in init.d with the following content: #!/bin/sh
exec=/usr/bin/unison myprofile -batch exec=/usr/bin/unison myprofile2 -batch That is all i put into the script and rendered it executeable with chmod -x After that i built the symlinks to rc.0 and rc.6. That is all i did there.
'myprofile' and 'myprofile2' only have meaning to you. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Yes - they are just the profiles of unison, that the program knows which folders to sync... Gesendet: Mittwoch, 23. April 2014 um 11:44 Uhr Von: "Carl Hartung" <opensuse@cehartung.com> An: opensuse@opensuse.org Betreff: Re: [opensuse] System not starting! On Wed, 23 Apr 2014 11:36:23 +0200 Benjamin Draxlbauer wrote:
I called the file "Sync" and put it in init.d with the following content: #!/bin/sh
exec=/usr/bin/unison myprofile -batch exec=/usr/bin/unison myprofile2 -batch That is all i put into the script and rendered it executeable with chmod -x After that i built the symlinks to rc.0 and rc.6. That is all i did there.
'myprofile' and 'myprofile2' only have meaning to you. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 23 Apr 2014 11:51:32 +0200 Benjamin Draxlbauer wrote:
Yes - they are just the profiles of unison, that the program knows which folders to sync...
I'll attempt to explain further: You injected a custom script into the boot process and it has apparently damaged your system. No one here can guess the locations or kinds of damage without knowing, first, the exact commands and arguments that were executed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-23 11:54, Carl Hartung wrote:
On Wed, 23 Apr 2014 11:51:32 +0200 Benjamin Draxlbauer wrote:
Yes - they are just the profiles of unison, that the program knows which folders to sync...
I'll attempt to explain further: You injected a custom script into the boot process and it has apparently damaged your system. No one here can guess the locations or kinds of damage without knowing, first, the exact commands and arguments that were executed.
cer@Telcontar:~/bin> cat pp #!/bin/sh exec=/usr/bin/unison myprofile -batch cer@Telcontar:~/bin> pp /home/cer/bin/pp: line 3: myprofile: command not found cer@Telcontar:~/bin> Ie, it tries to run "myprofile", not as a parameter to unison. On the other hand, the documentation says: exec [-a NAME] [-cl] [COMMAND] [ARG...] [REDIRECTION...] http://wiki.bash-hackers.org/commands/builtin/exec or man bash: exec [-cl] [-a name] [command [arguments]] If command is specified, it replaces the shell. No new process is created. The arguments become the arguments to command. If the -l option is supplied, the shell places a dash at the beginning of the zeroth argument passed to command. This is what login(1) does. The -c option causes command to be executed with an empty environment. If -a is supplied, the shell passes name as the zeroth argument to the executed command. If command cannot be exe- cuted for some reason, a non-interactive shell exits, unless the shell option execfail is enabled, in which case it returns failure. An interactive shell returns failure if the file cannot be executed. If command is not speci- fied, any redirections take effect in the cur- rent shell, and the return status is 0. If there is a redirection error, the return status is 1. I do not see a reference for the "=" symbol. That would try to assign a variable named "exec", I understand. Or I'm misunderstanding it. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Okay i am not really into writing shell-scripts, actually it was one of my first…So i do not think that there is much understand from your side, maybe I put an something in which just a mistake … ;). I first created the shell script without exec=… at the begining but it did not work…So i thouhgt I maybe have to tell him to execute the programm out of the user binarys… I quite bad in scripting ;) But I did think that this would ruin my system that much… Should make a repair with the opensuse dvd? Best – Benjamin Gesendet: Mittwoch, 23. April 2014 um 12:52 Uhr Von: "Carlos E. R." <robin.listas@telefonica.net> An: opensuse@opensuse.org Betreff: Re: [opensuse] System not starting! On 2014-04-23 11:54, Carl Hartung wrote:
On Wed, 23 Apr 2014 11:51:32 +0200 Benjamin Draxlbauer wrote:
Yes - they are just the profiles of unison, that the program knows which folders to sync...
I'll attempt to explain further: You injected a custom script into the boot process and it has apparently damaged your system. No one here can guess the locations or kinds of damage without knowing, first, the exact commands and arguments that were executed.
cer@Telcontar:~/bin> cat pp #!/bin/sh exec=/usr/bin/unison myprofile -batch cer@Telcontar:~/bin> pp /home/cer/bin/pp: line 3: myprofile: command not found cer@Telcontar:~/bin> Ie, it tries to run "myprofile", not as a parameter to unison. On the other hand, the documentation says: exec [-a NAME] [-cl] [COMMAND] [ARG...] [REDIRECTION...] http://wiki.bash-hackers.org/commands/builtin/exec or man bash: exec [-cl] [-a name] [command [arguments]] If command is specified, it replaces the shell. No new process is created. The arguments become the arguments to command. If the -l option is supplied, the shell places a dash at the beginning of the zeroth argument passed to command. This is what login(1) does. The -c option causes command to be executed with an empty environment. If -a is supplied, the shell passes name as the zeroth argument to the executed command. If command cannot be exe- cuted for some reason, a non-interactive shell exits, unless the shell option execfail is enabled, in which case it returns failure. An interactive shell returns failure if the file cannot be executed. If command is not speci- fied, any redirections take effect in the cur- rent shell, and the return status is 0. If there is a redirection error, the return status is 1. I do not see a reference for the "=" symbol. That would try to assign a variable named "exec", I understand. Or I'm misunderstanding it. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-23 13:01, Benjamin Draxlbauer wrote:
Okay i am not really into writing shell-scripts, actually it was one of my first…So i do not think that there is much understand from your side, maybe I put an something in which just a mistake … ;). I first created the shell script without exec=… at the begining but it did not work…So i thouhgt I maybe have to tell him to execute the programm out of the user binarys…
I quite bad in scripting ;) But I did think that this would ruin my system that much…
The script itself should not have done much damage. Trying to place it on the init folder like that, perhaps. Or the combination of both things. Then it might be something else totally unrelated.
Should make a repair with the opensuse dvd?
Just remove the script and links for the moment using any live system you prefer. And boot in level 3 with full messages. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Benjamin Draxlbauer wrote:
Okay i am not really into writing shell-scripts, actually it was one of my first…So i do not think that there is much understand from your side, maybe I put an something in which just a mistake … ;). I first created the shell script without exec=… at the begining but it did not work…So i thouhgt I maybe have to tell him to execute the programm out of the user binarys…
You didn't test it, and you put it into the boot up directories? Ready! Fire! AIM! I've been writing Unix /LInux shell scripts for 30 years, and administrating Unix / Linux computers for 20 years, and I would never do such a thing, no matter how simple it is.
I quite bad in scripting ;) But I did think that this would ruin my system that much…
You're BAD at shell scripting, and you DIDN'T TEST it before putting it into your boot up directories? Man, that's just begging for trouble. And you got it. Consider this a lesson.
Should make a repair with the opensuse dvd?
Best – Benjamin
Gesendet: Mittwoch, 23. April 2014 um 12:52 Uhr Von: "Carlos E. R." <robin.listas@telefonica.net> An: opensuse@opensuse.org Betreff: Re: [opensuse] System not starting! On 2014-04-23 11:54, Carl Hartung wrote:
On Wed, 23 Apr 2014 11:51:32 +0200 Benjamin Draxlbauer wrote:
Yes - they are just the profiles of unison, that the program knows which folders to sync...
I'll attempt to explain further: You injected a custom script into the boot process and it has apparently damaged your system. No one here can guess the locations or kinds of damage without knowing, first, the exact commands and arguments that were executed.
cer@Telcontar:~/bin> cat pp #!/bin/sh
exec=/usr/bin/unison myprofile -batch cer@Telcontar:~/bin> pp /home/cer/bin/pp: line 3: myprofile: command not found cer@Telcontar:~/bin>
Ie, it tries to run "myprofile", not as a parameter to unison.
On the other hand, the documentation says:
exec [-a NAME] [-cl] [COMMAND] [ARG...] [REDIRECTION...] http://wiki.bash-hackers.org/commands/builtin/exec
or man bash:
exec [-cl] [-a name] [command [arguments]] If command is specified, it replaces the shell. No new process is created. The arguments become the arguments to command. If the -l option is supplied, the shell places a dash at the beginning of the zeroth argument passed to command. This is what login(1) does. The -c option causes command to be executed with an empty environment. If -a is supplied, the shell passes name as the zeroth argument to the executed command. If command cannot be exe- cuted for some reason, a non-interactive shell exits, unless the shell option execfail is enabled, in which case it returns failure. An interactive shell returns failure if the file cannot be executed. If command is not speci- fied, any redirections take effect in the cur- rent shell, and the return status is 0. If there is a redirection error, the return status is 1.
I do not see a reference for the "=" symbol. That would try to assign a variable named "exec", I understand.
Or I'm misunderstanding it.
-- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
#!/bin/sh
exec=/usr/bin/unison myprofile -batch
As a shell script I too read that as Set the environment variable named 'exec' to the value '/usr/bin/unison' and execute the program 'myprofile' Which is unlikely to be what was intended. As Benjamin said
I quite bad in scripting
Yes but that's well documented in the manuals on shell scripting. There are few if any reasons to use the shell 'exec' functions in normal programming. Not least of all that it doesn't return control in the same way as simply running what would be the argument to 'exec'.
But I did think that this would ruin my system that much…
Oh? Why ever not? You created a script that interfered with the booting of the system and as you admit you are ignorant of some essential basics of shell programming. I realise that some people here defend sysvinit on the basis that its all about shell script and they are 'more intelligible' and shell programming is easy to understand. But honestly, the way systemd works I think that it would not have hung the system. The real problem with sysvinit is that it is sequential, it relies on each script behaving well and completing before going on to the next one. By comparison, there is less to a systemd unit file and if the syntax is wrong then its discarded. By comparison a unit file for this might read [Unit] Description=Unison to synchronise [Service] ExecStart=/usr/bin/unison /path/to/myprofile -batch [Install] WantedBy=multi-user.target which is a simple 'copy+edit' of an existing unit file such as the one for CUPS. I know from my own experience that an error in a unit file just gets it rejected. If Benjamin had been using a systemd approach rather than a sysvinit approach then he might not have achieved what he wanted right away, I certainly didn't when trying this the first few times (despite what John says, I'm not perfect) but it didn't hang or crash my system and the error messages were useful enough that I could rapidly converge on a correction. To my mind, a system that is so fragile that a simple syntax error in a script -- which is essentially what the "=" instead of a ' ' amounts to -- is worrisome. -- E pluribus unum. (Out of many, one.) - Motto for the Seal of the United States. Adopted 20 June 1782, recommended by John Adams, Benjamin Franklin and Thomas Jefferson, 10 Aug. 1776, and proposed by Swiss artist Pierre Eugene du SimitiËre. It had originally appeared on the title page of the Gentleman's Journal (Jan. 1692). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Thanks Anton for the clarification with regard to scripting ;) If i find a linux club around i will try to update my scripting abilities but at the moment i need a way to start my system! I am still quite unsure if an upgrade via the installation medium (live usb stick) is not to brutal for me, because still i do not want to reset my whole system at this point (it took me a long time to set it up in the way i have it now ;) ) Is there a way to reinstall only the basic system settings and leaving all the other stuff (like installed packages and all my profiles and individualized stuff) untouched? Like a "system-repair" or to set back the system? Best Benjamin Gesendet: Mittwoch, 23. April 2014 um 14:39 Uhr Von: "Anton Aylward" <opensuse@antonaylward.com> An: opensuse@opensuse.org Betreff: Re: [opensuse] System not starting!
#!/bin/sh
exec=/usr/bin/unison myprofile -batch
As a shell script I too read that as Set the environment variable named 'exec' to the value '/usr/bin/unison' and execute the program 'myprofile' Which is unlikely to be what was intended. As Benjamin said
I quite bad in scripting
Yes but that's well documented in the manuals on shell scripting. There are few if any reasons to use the shell 'exec' functions in normal programming. Not least of all that it doesn't return control in the same way as simply running what would be the argument to 'exec'.
But I did think that this would ruin my system that much…
Oh? Why ever not? You created a script that interfered with the booting of the system and as you admit you are ignorant of some essential basics of shell programming. I realise that some people here defend sysvinit on the basis that its all about shell script and they are 'more intelligible' and shell programming is easy to understand. But honestly, the way systemd works I think that it would not have hung the system. The real problem with sysvinit is that it is sequential, it relies on each script behaving well and completing before going on to the next one. By comparison, there is less to a systemd unit file and if the syntax is wrong then its discarded. By comparison a unit file for this might read [Unit] Description=Unison to synchronise [Service] ExecStart=/usr/bin/unison /path/to/myprofile -batch [Install] WantedBy=multi-user.target which is a simple 'copy+edit' of an existing unit file such as the one for CUPS. I know from my own experience that an error in a unit file just gets it rejected. If Benjamin had been using a systemd approach rather than a sysvinit approach then he might not have achieved what he wanted right away, I certainly didn't when trying this the first few times (despite what John says, I'm not perfect) but it didn't hang or crash my system and the error messages were useful enough that I could rapidly converge on a correction. To my mind, a system that is so fragile that a simple syntax error in a script -- which is essentially what the "=" instead of a ' ' amounts to -- is worrisome. -- E pluribus unum. (Out of many, one.) - Motto for the Seal of the United States. Adopted 20 June 1782, recommended by John Adams, Benjamin Franklin and Thomas Jefferson, 10 Aug. 1776, and proposed by Swiss artist Pierre Eugene du SimitiËre. It had originally appeared on the title page of the Gentleman's Journal (Jan. 1692). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/23/2014 08:59 AM, Benjamin Draxlbauer wrote:
Thanks Anton for the clarification with regard to scripting ;) If i find a linux club around i will try to update my scripting abilities but at the moment i need a way to start my system! I am still quite unsure if an upgrade via the installation medium (live usb stick) is not to brutal for me, because still i do not want to reset my whole system at this point (it took me a long time to set it up in the way i have it now ;) ) Is there a way to reinstall only the basic system settings and leaving all the other stuff (like installed packages and all my profiles and individualized stuff) untouched? Like a "system-repair" or to set back the system?
Benjamin: I subscribe to the list. There is no reason to cc me when you reply to the list and many consider it impolite. At the very least its redundant and can be confusing when figuring out which message to reply to :-) Best not to fall into the habit. I occasionally hose my system. Despite what John says, I make many mistakes. People who are wiling to do that have to live with such. The Rescue option on the distribution DVD is a godsend[1], boot from it, then chroot and you are in your basic system as if you had booted there and can clean up. I'm uncertain about the wording of you question, but one spin I can put on it the answer is YES. Or rather YES-BUT. The BUT is that you need to have /home on a separate partition. All the user-specific stuff lives there, so when you do a reinstall you tell the installer not to format that partition but to treat it as /home in the new installation. The 'whole disk as one partition' is a MS-DOS/MS-Windows habit that is quite disjoint from UNIX/Linux practices[2]. Having a separate 'home' partition so that user setting survive upgrades and re-installations is normal practice. If you don't do it, then you'll have to find some way to back up your settings. Nothing in this thread so far meads me to believe that your problem with the startup script could not be fixed by using the Rescue facility. However that is predicated on your skills and understanding being up to it, and your confusion over shell programming and few other items make me wonder if a wipe/reformat and a re-installation might not be simplest. That way we can be more sure of a solid baseline and you can be sure of what you install. I would not add things like LDAP before you have an adequate understanding of how to configure things so as not to hose your system. Unless, that is, you are setting out to learn by repeated installation. In which case you better keep extensive and detailed notes, as the tedium of the re-installation often causes personal forgetfulness. The 'leaving all the installed stuff' is not really an option. The best you might hope for is, in Repair/chroot mode, to use zypper to reinstall various packages, but you will need to now which ones. The 'it took a long time to set it up the way it is now' raises a few ironic laughs, doesn't it? In reality, all the key system config lives under /etc. Well, OK there may be a few maverick subsystems that fail to follow that convention, but I can't think of any at the moment, not any I use but YMMV. In the past I've reconstructed systems by copying from a backup of /etc. be careful with that, though, it may be that you are copying back your errors, so don't copy back wholesale. Check what the differences are between the re-installed system config and your copy and make sure what you are copying back is something you understand and want. [1] I use the term 'godsend' in the vernacular and not literally and mean no insult to any Atheists on the list by implying that the use of openSuse Rescue requires belief in a deity. [2] Though I wonder if large scale adoption of BtrFS might change this. -- Be extremely subtle, even to the point of formlessness. Be extremely mysterious, even to the point of soundlessness. Thereby you can be the director of the opponent's fate. Sun-tzu, The Art of War. Emptiness and Fullness -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Okay thanks everyone for offering me help! I apologize for my bad behaviour with regard to the script and messing around in the root folder ;) Again I have successfully hosed my system, but it is running again after a reinstallation with formatting my root partition – heavenly sent [1] I use two partition one with the / and one with the /home and so the feast is nearly set. It is always astonishing how effective and fast it is to install a shot-dead linux system (was not the first time!)…Today reminded me a little bit of my fedora-days 4 years ago… Anyway – Carpe Diem – and cheers to you Linux-Heads! [1] Also please don´t take this literally – its use is restricted to metaphorical meaning only and has nothing to do with an old mans habitat or the "invisible hand" and as such it should not be understood as a provokation of Atheists and Anti-Capitalists. Gesendet: Mittwoch, 23. April 2014 um 16:09 Uhr Von: "Anton Aylward" <opensuse@antonaylward.com> An: opensuse@opensuse.org Betreff: Re: [opensuse] System not starting! On 04/23/2014 08:59 AM, Benjamin Draxlbauer wrote:
Thanks Anton for the clarification with regard to scripting ;) If i find a linux club around i will try to update my scripting abilities but at the moment i need a way to start my system! I am still quite unsure if an upgrade via the installation medium (live usb stick) is not to brutal for me, because still i do not want to reset my whole system at this point (it took me a long time to set it up in the way i have it now ;) ) Is there a way to reinstall only the basic system settings and leaving all the other stuff (like installed packages and all my profiles and individualized stuff) untouched? Like a "system-repair" or to set back the system?
Benjamin: I subscribe to the list. There is no reason to cc me when you reply to the list and many consider it impolite. At the very least its redundant and can be confusing when figuring out which message to reply to :-) Best not to fall into the habit. I occasionally hose my system. Despite what John says, I make many mistakes. People who are wiling to do that have to live with such. The Rescue option on the distribution DVD is a godsend[1], boot from it, then chroot and you are in your basic system as if you had booted there and can clean up. I'm uncertain about the wording of you question, but one spin I can put on it the answer is YES. Or rather YES-BUT. The BUT is that you need to have /home on a separate partition. All the user-specific stuff lives there, so when you do a reinstall you tell the installer not to format that partition but to treat it as /home in the new installation. The 'whole disk as one partition' is a MS-DOS/MS-Windows habit that is quite disjoint from UNIX/Linux practices[2]. Having a separate 'home' partition so that user setting survive upgrades and re-installations is normal practice. If you don't do it, then you'll have to find some way to back up your settings. Nothing in this thread so far meads me to believe that your problem with the startup script could not be fixed by using the Rescue facility. However that is predicated on your skills and understanding being up to it, and your confusion over shell programming and few other items make me wonder if a wipe/reformat and a re-installation might not be simplest. That way we can be more sure of a solid baseline and you can be sure of what you install. I would not add things like LDAP before you have an adequate understanding of how to configure things so as not to hose your system. Unless, that is, you are setting out to learn by repeated installation. In which case you better keep extensive and detailed notes, as the tedium of the re-installation often causes personal forgetfulness. The 'leaving all the installed stuff' is not really an option. The best you might hope for is, in Repair/chroot mode, to use zypper to reinstall various packages, but you will need to now which ones. The 'it took a long time to set it up the way it is now' raises a few ironic laughs, doesn't it? In reality, all the key system config lives under /etc. Well, OK there may be a few maverick subsystems that fail to follow that convention, but I can't think of any at the moment, not any I use but YMMV. In the past I've reconstructed systems by copying from a backup of /etc. be careful with that, though, it may be that you are copying back your errors, so don't copy back wholesale. Check what the differences are between the re-installed system config and your copy and make sure what you are copying back is something you understand and want. [1] I use the term 'godsend' in the vernacular and not literally and mean no insult to any Atheists on the list by implying that the use of openSuse Rescue requires belief in a deity. [2] Though I wonder if large scale adoption of BtrFS might change this. -- Be extremely subtle, even to the point of formlessness. Be extremely mysterious, even to the point of soundlessness. Thereby you can be the director of the opponent's fate. Sun-tzu, The Art of War. Emptiness and Fullness -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-23 17:42, Benjamin Draxlbauer wrote:
Okay thanks everyone for offering me help! I apologize for my bad behaviour with regard to the script and messing around in the root folder ;) Again I have successfully hosed my system, but it is running again after a reinstallation with formatting my root partition – heavenly sent [1] I use two partition one with the / and one with the /home and so the feast is nearly set. It is always astonishing how effective and fast it is to install a shot-dead linux system (was not the first time!)…Today reminded me a little bit of my fedora-days 4 years ago…
Happy you solved your problem! :-)) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2014-04-23 16:09, Anton Aylward wrote:
On 04/23/2014 08:59 AM, Benjamin Draxlbauer wrote:
The 'leaving all the installed stuff' is not really an option. The best you might hope for is, in Repair/chroot mode, to use zypper to reinstall various packages, but you will need to now which ones. The 'it took a long time to set it up the way it is now' raises a few ironic laughs, doesn't it?
Yes, one has to re-install several times at some point in order to learn how to do do things. We all did at some point, or else we had someone looking just over our shoulders to take over.
In reality, all the key system config lives under /etc. Well, OK there may be a few maverick subsystems that fail to follow that convention, but I can't think of any at the moment, not any I use but YMMV. In the past I've reconstructed systems by copying from a backup of /etc.
Yes, but... databases use to live somewhere under /var. Same for email service, fax, and few others. Logs may be important. Directory /srv is where apache data lives, or ftp... There may be others. Tinyftp, if I got the name right, wanted to use a directory directly on the root. Sometimes keeping just home intact doesn't save your day ;-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Le 23/04/2014 20:07, Carlos E. R. a écrit :
Yes, one has to re-install several times at some point in order to learn how to do do things. We all did at some point, or else we had someone looking just over our shoulders to take over.
yes, and I even wrote down my experience here http://dodin.info/wiki/index.php?n=Doc.OpenSUSE-small-ThirdEdition (and by the way began an article for the monthly news about this) but from an "amateur" point of view (that is someone with no university cursus on the subject), there is always something to learn
Yes, but... databases use to live somewhere under /var. Same for email service, fax, and few others. Logs may be important. Directory /srv is where apache data lives, or ftp... There may be others. Tinyftp, if I got the name right, wanted to use a directory directly on the root.
Sometimes keeping just home intact doesn't save your day ;-)
exactly. All and everything should be saved in the same place, yet to be found :-( but right now there is no way to backup totally a server (that can't be stopped) I wonder if the new btrfs will allow this, with a snapshot system resembling the one of virtualbox? but this is an other story (and preferably an other thread) jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 2014-04-23 16:09, Anton Aylward wrote:
On 04/23/2014 08:59 AM, Benjamin Draxlbauer wrote:
The 'leaving all the installed stuff' is not really an option. The best you might hope for is, in Repair/chroot mode, to use zypper to reinstall various packages, but you will need to now which ones. The 'it took a long time to set it up the way it is now' raises a few ironic laughs, doesn't it?
Yes, one has to re-install several times at some point in order to learn how to do do things. We all did at some point, or else we had someone looking just over our shoulders to take over.
In reality, all the key system config lives under /etc. Well, OK there may be a few maverick subsystems that fail to follow that convention, but I can't think of any at the moment, not any I use but YMMV. In the past I've reconstructed systems by copying from a backup of /etc.
Yes, but... databases use to live somewhere under /var. Same for email service, fax, and few others. Logs may be important. Directory /srv is where apache data lives, or ftp... There may be others. Tinyftp, if I got the name right, wanted to use a directory directly on the root.
Sometimes keeping just home intact doesn't save your day ;-)
Which is why my system looks like this: linux-4o6w:~ # df -h | grep -v tmpfs /dev/sda1 979M 85M 828M 10% /boot /dev/sda2 75G 20G 56G 27% /opt /dev/sda5 165G 21G 136G 14% / /dev/sda6 20G 81M 20G 1% /tmp /dev/sda8 20G 2.0G 19G 10% /srv /dev/sda9 200G 5.7G 195G 3% /var /dev/sda10 434G 361G 51G 88% /scratch2 /dev/sdb5 150G 95G 56G 64% /local /dev/sdb6 350G 167G 184G 48% /scratch1 /dev/sdb7 340G 159G 182G 47% /home /dev/sr0 4.2G 4.2G 0 100% /media/openSUSE-13.1-DVD-i5860091 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/23/2014 02:07 PM, Carlos E. R. wrote:
On 2014-04-23 16:09, Anton Aylward wrote:
On 04/23/2014 08:59 AM, Benjamin Draxlbauer wrote:
The 'leaving all the installed stuff' is not really an option. The best you might hope for is, in Repair/chroot mode, to use zypper to reinstall various packages, but you will need to now which ones. The 'it took a long time to set it up the way it is now' raises a few ironic laughs, doesn't it?
Yes, one has to re-install several times at some point in order to learn how to do do things. We all did at some point, or else we had someone looking just over our shoulders to take over.
Install-wipe-install-wipe-install-wipe. At least with LVM parts of that got a lot easier, one reason for the cycle, determining how small a partition could be and still fit the system in so as to maximise the data partition, back in the SCO UNIX days of 10G drives, no longer applied.
In reality, all the key system config lives under /etc. Well, OK there may be a few maverick subsystems that fail to follow that convention, but I can't think of any at the moment, not any I use but YMMV. In the past I've reconstructed systems by copying from a backup of /etc.
Yes, but... databases use to live somewhere under /var.
So they did, but I said that config lives under /etc.
Same for email service, fax, and few others. Logs may be important.
One a new install?
Directory /srv is where apache data lives, or ftp... There may be others.
Yes, but that's data. In my opinion /srv should be on its won partition just like /home, and should survive re-installation just the same way /home does. YMMV however.
Tinyftp, if I got the name right, wanted to use a directory directly on the root.
I think you mean that while its necessary its not always sufficient. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Anton Aylward -
Benjamin Draxlbauer -
Carl Hartung -
Carlos E. R. -
Dirk Gently -
jdd