[opensuse] Opensuse taken over by Microsoft?
Hello, since I updated my 10.3 to the latest kernel there are nothing but problems. The behaviour of my labtop reminds me of the terrible times when I had to suffer from Win98, although at the moment I wished I had such a great and stable stystem like Win98 compared to that junk now "running" here. I cannot shutdown, logging out as a user takes ages, after logging out /home partition is still in use, now seamonkey blocked and I cannot kill the process, not even as root. I logged out as user, tried to kill that process as root, logged in as user again, the process is still here: seamonkey cannot start anymore. So if this is what opensuse is now, then my time with opensuse will end the very first moment I am at home and able to install another system. I wouldn't even care what system - *any* crap would be far better than what I actually have here! Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 26 June 2008, Daniel Bauer wrote:
Hello,
since I updated my 10.3 to the latest kernel there are nothing but problems. The behaviour of my labtop reminds me of the terrible times when I had to suffer from Win98, although at the moment I wished I had such a great and stable stystem like Win98 compared to that junk now "running" here.
I cannot shutdown, logging out as a user takes ages, after logging out /home partition is still in use, now seamonkey blocked and I cannot kill the process, not even as root.
I logged out as user, tried to kill that process as root, logged in as user again, the process is still here: seamonkey cannot start anymore.
So if this is what opensuse is now, then my time with opensuse will end the very first moment I am at home and able to install another system. I wouldn't even care what system - *any* crap would be far better than what I actually have here!
Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/
Unkillable processes means that the filesystem is most likely the culprit. Do you use reiserfs? Check this https://bugzilla.novell.com/show_bug.cgi?id=389656 and this https://bugzilla.novell.com/show_bug.cgi?id=378095. I would advise switching to another filesystem, as 10.3 shipped with serious reiserfs problems as well. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2008-06-26 at 11:20 +0300, auxsvr@gmail.com wrote:
Unkillable processes means that the filesystem is most likely the culprit. Do you use reiserfs? Check this https://bugzilla.novell.com/show_bug.cgi?id=389656 and this https://bugzilla.novell.com/show_bug.cgi?id=378095. I would advise switching to another filesystem, as 10.3 shipped with serious reiserfs problems as well.
What about 11.0 is Reiser fixed. I use in my /home directory from 10.0. I would hate to loose it all because of some newly introduced bug. CWSIV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carl Spitzer
On Thu, 2008-06-26 at 11:20 +0300, auxsvr@gmail.com wrote:
Unkillable processes means that the filesystem is most likely the culprit. Do you use reiserfs? Check this https://bugzilla.novell.com/show_bug.cgi?id=389656 and this https://bugzilla.novell.com/show_bug.cgi?id=378095. I would advise switching to another filesystem, as 10.3 shipped with serious reiserfs problems as well.
What about 11.0 is Reiser fixed. I use in my /home directory from 10.0. I would hate to loose it all because of some newly introduced bug.
See: http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.0, it mentions: "System freeze with reiserfs and beagle. (Bug #389656). Workaround: do not install beagle. " Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Thursday 26 June 2008 03:20, auxsvr@gmail.com wrote:
I would advise switching to another filesystem, as 10.3 shipped with serious reiserfs problems as well. What serious isssues... reiserfs working fine here.....
-- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Daniel Bauer
Hello,
since I updated my 10.3 to the latest kernel there are nothing but problems.
What exactly do you mean with latest kernel? Did you update - as auxsvr mentioned - to openSUSE 11.0 or did you install the latest 10.3 security update to 2.6.22.18-0.2? I assume you mean the 10.3 update to 2.6.22.
The behaviour of my labtop reminds me of the terrible times when I had to suffer from Win98, although at the moment I wished I had such a great and stable stystem like Win98 compared to that junk now "running" here.
I cannot shutdown, logging out as a user takes ages, after logging out /home partition is still in use, now seamonkey blocked and I cannot kill the process, not even as root.
This could indicate hardware problems. Please run dmesg and see whether you see anything strange there. If you really suspect the kernel, please install the previous kernel (you can get it from the update repositories) and see whether it helps. And if it does, I suggest to open a bugreport against 10.3 in our bugzilla following the suggestions on bugs.opensuse.org for kernel reports.
I logged out as user, tried to kill that process as root, logged in as user again, the process is still here: seamonkey cannot start anymore.
So if this is what opensuse is now, then my time with opensuse will end the very first moment I am at home and able to install another system. I wouldn't even care what system - *any* crap would be far better than what I actually have here!
Btw. if you like to get a polemic answer, you can start with polemic rhetoric - but if you like to have real help, I suggest to do it with less polemic ;) Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Daniel Bauer
writes: Hello,
since I updated my 10.3 to the latest kernel there are nothing but
On Thursday 26 June 2008 10:32:06, Andreas Jaeger wrote: problems.
What exactly do you mean with latest kernel? Did you update - as auxsvr mentioned - to openSUSE 11.0
no
or did you install the latest 10.3 security update to 2.6.22.18-0.2?
Yes, using OpenSuse updater.
I assume you mean the 10.3 update to 2.6.22.
The behaviour of my labtop reminds me of the terrible times when I had to suffer from Win98, although at the moment I wished I had such a great and stable stystem like Win98 compared to that junk now "running" here.
I cannot shutdown, logging out as a user takes ages, after logging out /home partition is still in use, now seamonkey blocked and I cannot kill the process, not even as root.
This could indicate hardware problems. Please run dmesg and see whether you see anything strange there.
I attach dmesg output.
If you really suspect the kernel, please install the previous kernel (you can get it from the update repositories) and see whether it helps.
I am a bit afraid of this, because the update also installed some new modules. I guess with my knowledge I might even worsen the problems.
And if it does, I suggest to open a bugreport against 10.3 in our bugzilla following the suggestions on bugs.opensuse.org for kernel reports.
I opened a report here: https://bugzilla.novell.com/show_bug.cgi?id=403134 Of course it can be that there is another problem causing all that, then it just fell together with the kernel update. Before the laptop worked absolutely perfect. Well, besides of the problems with KNetworkManager...
Btw. if you like to get a polemic answer, you can start with polemic rhetoric
you are right, of course. It's just that I am abroad and a working computer is essential for me. And I just lost the chance to convince an Internet-Café to change from win to Linux and - and - and... So my nerves are somehow stressed.
- but if you like to have real help, I suggest to do it with less polemic ;)
Andreas
Ok, I'll try ;-) I am now going to try a reiserfs check, in the hope that I will not completely ruin my system... Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/
Daniel Bauer
[...] I opened a report here: https://bugzilla.novell.com/show_bug.cgi?id=403134
Good - I commented on it and moved it forward. The dmesg output missed the interesting parts.
Of course it can be that there is another problem causing all that, then it just fell together with the kernel update. Before the laptop worked absolutely perfect. Well, besides of the problems with KNetworkManager...
Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Thursday 26 June 2008 12:15:47, Andreas Jaeger wrote:
Daniel Bauer
writes: [...] I opened a report here: https://bugzilla.novell.com/show_bug.cgi?id=403134
Good - I commented on it and moved it forward. The dmesg output missed the interesting parts.
So how can I deliver the "interesting parts"? I just entered "dmesg >& dmesg.txt" (as user daniel) Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Daniel Bauer
On Thursday 26 June 2008 12:15:47, Andreas Jaeger wrote:
Daniel Bauer
writes: [...] I opened a report here: https://bugzilla.novell.com/show_bug.cgi?id=403134
Good - I commented on it and moved it forward. The dmesg output missed the interesting parts.
So how can I deliver the "interesting parts"? I just entered "dmesg >& dmesg.txt" (as user daniel)
Sorry, I was too brief: The dmesg output in your email missed the interesting parts but the bugzilla attachment contained it. Bugzilla has a proposed solution for the sound driver oops - please followup there, Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Thu, Jun 26, 2008 at 5:13 AM, Daniel Bauer
Daniel Bauer
writes: Hello,
since I updated my 10.3 to the latest kernel there are nothing but
On Thursday 26 June 2008 10:32:06, Andreas Jaeger wrote: problems.
What exactly do you mean with latest kernel? Did you update - as auxsvr mentioned - to openSUSE 11.0
no
or did you install the latest 10.3 security update to 2.6.22.18-0.2?
Yes, using OpenSuse updater.
I assume you mean the 10.3 update to 2.6.22.
The behaviour of my labtop reminds me of the terrible times when I had to suffer from Win98, although at the moment I wished I had such a great and stable stystem like Win98 compared to that junk now "running" here.
I cannot shutdown, logging out as a user takes ages, after logging out /home partition is still in use, now seamonkey blocked and I cannot kill the process, not even as root.
This could indicate hardware problems. Please run dmesg and see whether you see anything strange there.
I attach dmesg output.
If you really suspect the kernel, please install the previous kernel (you can get it from the update repositories) and see whether it helps.
I am a bit afraid of this, because the update also installed some new modules. I guess with my knowledge I might even worsen the problems.
And if it does, I suggest to open a bugreport against 10.3 in our bugzilla following the suggestions on bugs.opensuse.org for kernel reports.
I opened a report here: https://bugzilla.novell.com/show_bug.cgi?id=403134
Of course it can be that there is another problem causing all that, then it just fell together with the kernel update. Before the laptop worked absolutely perfect. Well, besides of the problems with KNetworkManager...
Btw. if you like to get a polemic answer, you can start with polemic rhetoric
you are right, of course. It's just that I am abroad and a working computer is essential for me. And I just lost the chance to convince an Internet-Café to change from win to Linux and - and - and... So my nerves are somehow stressed.
- but if you like to have real help, I suggest to do it with less polemic ;)
Andreas
Ok, I'll try ;-)
I am now going to try a reiserfs check, in the hope that I will not completely ruin my system...
Daniel
-- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/
From my experience it seems best to avoid reiserfs and use ext3 instead. On one machine I had to deal with reiserfs was even losing files, so I think it's best to just not use - unless there is a very compeling reason to decide otherwise.
Boris. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Jun 26, 2008 at 9:23 AM, Boris Epstein
From my experience it seems best to avoid reiserfs and use ext3 instead. On one machine I had to deal with reiserfs was even losing files, so I think it's best to just not use - unless there is a very compeling reason to decide otherwise.
Strange. I've been using reiserfs since SuSE 7.3(at least). Never had a bit of trouble, and it's always benchmarked faster than ext3 on my systems(for whrn I actually decided to check into it). BTW, PLEASE prune your quotes. Is it really neccessary to quote all that? We do have people on dial up, and even on broadband, that was way too much to delete to write this message. Thanx On Thu, Jun 26, 2008, Andreas Jaeger wrote:
See: http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.0, it mentions:
"System freeze with reiserfs and beagle. (Bug #389656). Workaround: do not install beagle. "
Just one more reason not to install beagle. If a program can screw up a file system, then that program has a lot of problems. And, people shouldn't complain about resier if it was beagle's fault. Reiser has been a life saver on my machines for over 7 years. It's a shame v4 got derailed because of Hans's problems -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Larry Stotler wrote:
On Thu, Jun 26, 2008 at 9:23 AM, Boris Epstein
wrote:> From my experience it seems best to avoid reiserfs and use ext3 instead. On one machine I had to deal with reiserfs was even losing files, so I think it's best to just not use - unless there is a very compeling reason to decide otherwise.
Strange. I've been using reiserfs since SuSE 7.3(at least). Never had a bit of trouble, and it's always benchmarked faster than ext3 on my systems(for whrn I actually decided to check into it).
BTW, PLEASE prune your quotes. Is it really neccessary to quote all that? We do have people on dial up, and even on broadband, that was way too much to delete to write this message. Thanx
On Thu, Jun 26, 2008, Andreas Jaeger wrote:
See: http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.0, it mentions:
"System freeze with reiserfs and beagle. (Bug #389656). Workaround: do not install beagle. "
Just one more reason not to install beagle. If a program can screw up a file system, then that program has a lot of problems. And, people shouldn't complain about resier if it was beagle's fault. Reiser has been a life saver on my machines for over 7 years. It's a shame v4 got derailed because of Hans's problems
Quoting your complete message above. Practice what you preach. But you know, yourself and other Mail List Sheriffs's like Pat Shanahan should consider what you are really whingeing about when you keep trying to enforce your ideas on other people in this and other lists. You are telling Boris to prune his message because you are not really so much worried about those members of this list who are using dial-up but you are worried about - note! - "way too much to delete to write this message."! Woohoo! "Too much to delete to write this message." Oh gosh. Life's a real bich, ain't it? But let's not stop here. The message Boris sent is 7K big. Your message is 5K big. Even if one was on dial-up, how much of a difference have YOU made to someone on dial-up by posting a message which is only 2K smaller than the person you are berating for posting an unpruned message of 7K? Oh, a simple question: why didn't you prune your message? I think I'll have to bring this matter to the attention of our resident List Patrolman, Patrick - but he's probably already composing a "fire and brimstone" missive to you about this. BTW, you addressed your message to some 3 addresses. Now, all people in this mail list get whatever message is posted in this list so if you are SO much concerned about people on dial-up, and anyone of the people you also sent a copy of this msg to may very well be on dial-up would now have received 2 copies of the same message - ie 10K instead of only 5K, why have you done this? Fix your mailer so that you only send the ONE message as a reply - to this list only. Ciao. -- It's not possible to operate honestly using a basis of dishonesty. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Jun 27, 2008 at 9:06 AM, Basil Chupin
Quoting your complete message above. Practice what you preach. But you know, yourself and other Mail List Sheriffs's like Pat Shanahan should consider what you are really whingeing about when you keep trying to enforce your ideas on other people in this and other lists.
Whoa. I asked him to prune his quote for 2 reasons: 1. It was excessive 2. It makes editing it much more difficult because it was excessive. I'm not a "sheriff". It's up to all of us to encourage better list editing for everyone's benefit. From the tome of your message to me, you would have been much more ignorant towards him. How is that better?
You are telling Boris to prune his message because you are not really so much worried about those members of this list who are using dial-up but you are worried about - note! - "way too much to delete to write this message."! Woohoo! "Too much to delete to write this message." Oh gosh. Life's a real bich, ain't it?
1. I didn't TELL him anything. I asked. 2. It makes it harder for the next person to post, which is why I said that.
But let's not stop here. The message Boris sent is 7K big. Your message is 5K big. Even if one was on dial-up, how much of a difference have YOU made to someone on dial-up by posting a message which is only 2K smaller than the person you are berating for posting an unpruned message of 7K?
And, when you have 20 people quoting excessively, that adds up. So, after 20 replies, and what, 100 different messages a day on this list, that adds up.
Oh, a simple question: why didn't you prune your message?
I did. I also consolidated and replied to 2 posters at once. I left the "relevant" portions intact.
BTW, you addressed your message to some 3 addresses. Now, all people in this mail list get whatever message is posted in this list so if you are SO much concerned about people on dial-up, and anyone of the people you also sent a copy of this msg to may very well be on dial-up would now have received 2 copies of the same message - ie 10K instead of only 5K, why have you done this?
Yeah, that was a mistake on my part. I didn't realize that until I had already hit send. I guess we can't all be perfect like you.
Fix your mailer so that you only send the ONE message as a reply - to this list only.
I don't do a default because I do need to cc: others when I redirect messages to proper lists(you know like opensuse-ppc and opensuse-factory) to help people get help. Thanx for taking a friendly "please editing your quotes" and turning it into a useless rant. It's no wonder we can't stay on topic on these lists, with all this constant bickering about little stuff. Or bickering about someone else asking something simple.
It's not possible to operate honestly using a basis of dishonesty.
Try practicing what you preach. I made a request and thanked him afterwards. You are making demands. Thanks for being on the moral high road. Talk about being a hippocrite. You rant and then you demand. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
torsdagen den 26 juni 2008 skrev Daniel Bauer:
Hello,
since I updated my 10.3 to the latest kernel there are nothing but problems. The behaviour of my labtop reminds me of the terrible times when I had to suffer from Win98, although at the moment I wished I had such a great and stable stystem like Win98 compared to that junk now "running" here.
I cannot shutdown, logging out as a user takes ages, after logging out /home partition is still in use, now seamonkey blocked and I cannot kill the process, not even as root.
I logged out as user, tried to kill that process as root, logged in as user again, the process is still here: seamonkey cannot start anymore.
So if this is what opensuse is now, then my time with opensuse will end the very first moment I am at home and able to install another system. I wouldn't even care what system - *any* crap would be far better than what I actually have here!
Daniel --
I just finished upgrading from 10.3 to 11.0 on two desktops and one laptop. The desktops presented no problems. The laptop, however, was quite problematic. Like you said, everything was sluggish, lock-ups, etc etc. I found the culprit was the NetworkManager daemon which consumed all processor capacity. Killing it made everything OK, except I now had to manually configure network connections, which isn't acceptable on a laptop which you carry around. Digging deeper I found /var/log/messages was filled with logs about nm-system-settings daemon continously restarting, then crashing with the error "Invalid or missig ssid". I managed to get NetworkManager running by removing ifcfg-suse from the plugins in /etc/nm-system-settings.conf. No idea why that helped, but now I am able to connect to both wired and wireless via knetworkmanager, AND the laptop is snappy as ever. /Lennart -- !++ ! Lennart Börjeson, Cinnober Financial Technology AB ! Kungsgatan 36, S-111 35 STOCKHOLM ! Sverige/Sweden/Schweden/Suède ! phone:+46-8-50304717 gsm:+46-70-3394717 fax:+46-8-50304701 !-- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I found the culprit was the NetworkManager daemon which consumed all processor capacity. Killing it made everything OK, except I now had to manually configure network connections, which isn't acceptable on a laptop which you carry around.
Digging deeper I found /var/log/messages was filled with logs about nm-system-settings daemon continously restarting, then crashing with the error "Invalid or missig ssid".
I managed to get NetworkManager running by removing ifcfg-suse from the plugins in /etc/nm-system-settings.conf. No idea why that helped, but now I am able to connect to both wired and wireless via knetworkmanager, AND the laptop is snappy as ever.
/Lennart
Nice work and thanks for the heads up. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Lennart Börjeson wrote:
torsdagen den 26 juni 2008 skrev Daniel Bauer:
Hello,
since I updated my 10.3 to the latest kernel there are nothing but problems.
[pruned]
I just finished upgrading from 10.3 to 11.0 on two desktops and one laptop.
[pruned] The most misunderstood and misused terms in these lists are the terms "update/d" and "upgrade/d". Oxford Dictinionary: "Update" - bring up to date. "Upgrade" - raise in rank etc. I am sure that Daniel is telling us that he UPDATED to a new kernel in his 10.3 openSUSE, while Lennart is talking about UPGRADING to v11.0 of openSUSE. To me these are 2 different things, and problems encountered in one are not necessarily the same as in the other. Am I wrong? Ciao. -- It's not possible to operate honestly using a basis of dishonesty. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
torsdagen den 26 juni 2008 skrev Basil Chupin:
Lennart Börjeson wrote:
torsdagen den 26 juni 2008 skrev Daniel Bauer: I am sure that Daniel is telling us that he UPDATED to a new kernel in his 10.3 openSUSE, while Lennart is talking about UPGRADING to v11.0 of openSUSE.
To me these are 2 different things, and problems encountered in one are not necessarily the same as in the other.
Am I wrong?
You are right, mea culpa. Can only hope my information was helpful for some other guy. /Lennart -- !++ ! Lennart Börjeson, Cinnober Financial Technology AB ! Kungsgatan 36, S-111 35 STOCKHOLM ! Sverige/Sweden/Schweden/Suède ! phone:+46-8-50304717 gsm:+46-70-3394717 fax:+46-8-50304701 !-- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Daniel Bauer wrote:
Hello,
hello, First of all, beginning a post insulting the people you ask help from is not a good idea...
since I updated my 10.3 to the latest kernel there are nothing but problems.
but is this related at all with the update? I just had similar problem with a test 11 install, only to discover the hard drive was filled by an enormous error messages file... (9Gb!) When Linux get short of space, it behave very erraticly. I had even problems removing the file: I could reove, but had to reboot to have the space really freed. so, in your place, I should begin by using "df -h" and "du -h" to see what happen, and this in a true terminal (better then do init 1) if you don't find anything, look at the /tmp directory size, then /var/log/message jdd -- Jean-Daniel Dodin Président du CULTe www.culte.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
jdd sur free wrote:
Daniel Bauer wrote:
Hello,
hello, First of all, beginning a post insulting the people you ask help from is not a good idea...
since I updated my 10.3 to the latest kernel there are nothing but problems.
but is this related at all with the update?
I just had similar problem with a test 11 install, only to discover the hard drive was filled by an enormous error messages file... (9Gb!)
When Linux get short of space, it behave very erraticly. I had even problems removing the file: I could reove, but had to reboot to have the space really freed.
You don't need to reboot to free the space, you just have to close all open file handles on the deleted file. It's standard unix behavior that you can delete a file and it disappears from directory listings, but it's not really deleted if any process has the file open. When there are no open file handles left, the file is deleted. By rebooting, you killed any processes that had that file open, and so the space was freed. That's sort of like killing a fly with a nuclear bomb, since you could have done the same thing with an fuser command rather than rebooting. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
J Sloan wrote:
By rebooting, you killed any processes that had that file open, and so the space was freed. That's sort of like killing a fly with a nuclear bomb, since you could have done the same thing with an fuser command rather than rebooting.
no, because with this file on the computer was almost unusable (100% home used) given I had nothing working, rebooting was simpler jdd -- Jean-Daniel Dodin Président du CULTe www.culte.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am I dense - or - what has this thread exactly got to do with Microsoft taking over opensuse ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 26 June 2008 22:40:42, Duaine & Laura Hechler wrote:
Am I dense - or - what has this thread exactly got to do with Microsoft taking over opensuse ?
I am the bad guy who started this thread with this provocative subject line a) due to my frustration about the various and very strange behaviour after the kernel update that reminded me on my suffering under Win98 - things I thought were in the past for ever... A non-working computer with strange and unresolvable problems is typical for M$ in my eyes. b) As I got no answer leading to a result in my original thread and my bug report about the shutdown problems I tried with that provocative subject line, because I hoped that such a title has a greater chance to be seen. Althgough my assumption seemed to apply (it took only few hours to solve the problem then) I still apologize for my bad behaviour due to my stressed nerves and my temperament. I hope to better myself in similar situations in future... Well, no guarantee. So I take this occasion to thank again for the received help! Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 26 June 2008 01:09:39 am Daniel Bauer wrote:
Hello,
since I updated my 10.3 to the latest kernel there are nothing but problems.
Daniel: What kernel are you on? I have - according to My Computer - Linux 2.6.22.18-0.2-default i686 on all three of my home systems. -- kai www.filesite.org || www.4thedadz.com || www.perfectreign.com remember - a turn signal is a statement, not a request -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 26 June 2008 15:14:15, Kai Ponte wrote:
On Thursday 26 June 2008 01:09:39 am Daniel Bauer wrote:
Hello,
since I updated my 10.3 to the latest kernel there are nothing but problems.
Daniel:
What kernel are you on?
I have - according to My Computer - Linux 2.6.22.18-0.2-default i686 on all three of my home systems.
I have the same kernel. The shutdown problem was caused by a bug in alsa-driver-unstable-kmp package and is solved now, see my post here: http://lists.opensuse.org/opensuse/2008-06/msg03067.html Obviously with the previous kernel the also-driver-bug didn't bite me... Daniel -- Daniel Bauer photographer Basel Barcelona professional photography: http://www.daniel-bauer.com erotic art photos: http://www.bauer-nudes.com Madagascar special: http://www.fotograf-basel.ch/madagascar/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (14)
-
Andreas Jaeger
-
auxsvr@gmail.com
-
Basil Chupin
-
Boris Epstein
-
Brian K. White
-
Carl Spitzer
-
Daniel Bauer
-
Duaine & Laura Hechler
-
J Sloan
-
jdd sur free
-
Kai Ponte
-
Larry Stotler
-
Lennart Börjeson
-
M Harris