Hi,
Hi,
I forgot to mention something in the last mail. After giving # chown -R <username>: / cd'd to / and then gave an ls, I saw that only the permissions of /dev and /bin were changed to the <username>. Therefore,
I again gave # chown -R root:/ and then realised that it would change the permissions of /home, etc and then I again Ctrl-C'd.
Wow, another good one. Simply tell yourself that it will be a good learning experience. (^-^) Just in case you get any other rash urges to exercise commands like that in a
panic: DON'T exit a root shell when you have just done something likely to crash the system. I usually think I don't panic, but I did. Got to improve. Next time if I do something dumb, I will not panic (at least try not to).
Both /etc and /sbin are root:root set to (user:group)
In that case you should be able to use the rescue cd to boot up, chroot to your original system and then use passwd to give root a password. I did use the rescue CD. I don't understand this chroot thing. Can you elaborate on that a bit.
PS: if you still feel adventurous and decide to experiment with files like passwd manually, you might want to make a BACKUP of it first! Ya I did make a backup. But then I think the harm has already been done to the files before I made a backup.
Regards, Chaitanya. ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
Hi all, I've been tinkering around with Suse 9.3 for a few days, and I'm really impressed overall. I'd like to understand YAST a bit more (do gconf and YAST get along?), implement apt-get, recompile the kernel (to address the 4 k stack limitation), and, finally, improve or customize the Gnome desktop. I've used Red Hat and then Fedora for some time, but I'm on the verge of switching to Suse because it appears that Novell is really interested in delivering a solid product rather than using it as an experimental launching pad for another product. When I began using Suse 9.3, I was a little disappointed by Suse's implementation of Gnome. It "appears" that much effort has gone into KDE (and it shows), but less into Gnome. I have nothing against KDE, but I prefer Gnome. In fact, I have had four different machines running both KDE and Gnome, and I've always found KDE to be a little bit faster. One of the great things about Linux is that you can choose a number of desktops and Window Managers. As it stands, though, Gnome is better suited for me. Anyway, back to the point of this email. I obviously can customize my Gnome desktop, but before I continue to do so, I'd like to hear from other Suse Gnome users out there who can give me their impressions about working with Gnome in Suse? I'd be interested in hearing any perspectives about Gnome/Suse that you may have. Thanks, Paul Hoy
On Sat, 30 Jul 2005 17:58:36 -0400 Paul Hoy <paul.hoy@mac.com> wrote:
Anyway, back to the point of this email. I obviously can customize my Gnome desktop, but before I continue to do so, I'd like to hear from other Suse Gnome users out there who can give me their impressions about working with Gnome in Suse? I'd be interested in hearing any perspectives about Gnome/Suse that you may have.
I have an emotional reaction to KDE - sounds like a "Kulture" that does not appeal to me - so put me in the Gnome camp. But I consider myself a newbie with regard to Linux - and my greatest concern is whether "Gnome in SuSE" is the same as "Gnome", or not. Just about all the documentation I find is about "Gnome", yet it seems to me that "Gnome in SuSE" puts stuff in directories different from "Gnome". Under SuSE 9.2 I used Gnome throughout. I somehow managed to lose access to the Gnome icons (i.e., images) on my desktop, but was able to continue to use the desktop items by clicking on the text in those entries. So put me down as a happy "Gnome in SuSE" user (though there were facilities in KDE that were missing in Gnome - for instance, graphic adjustment of the gamma value for my display). Under SuSE 9.3 I'm not happy. Where I did an "install from scratch" of 9.3, Gnome works (though sometimes it disappears from the login screen options). But on the Linux system I use the most, I had (deliberately) done an "upgrade" from SuSE 9.2 to Suse 9.3. On that system, Gnome complains "undefined symbol" and does not run. Being a newbie, I have not the slightest idea why. I've done a lot of searching, but have not found anything that would let me solve what is going wrong. [Initially, there was no specific apt 'Gnome component' depository supported by SuSE for 9.3 - only for earlier SuSE versions. I see that recently such a depository has been provided for 9.3 as well.] My opinion of Gnome for SuSE 9.3 - if you know enough to be able to overcome obstacles by yourself, then go for it. mikus
I've been tinkering around with Suse 9.3 for a few days, and I'm really impressed overall. I'd like to understand YAST a bit more (do gconf and YAST get along?),
Well, YaST is your system config tool, and GConf handles personal GNOME settings, it's like asking what the result of the last New York Yankees vs Manchester United match was.
implement apt-get,
ftp://ftp.gwdg.de/pub/linux/suse/apt/SuSE/9.3-i386/RPMS.suser-rbos/
improve or customize the Gnome desktop.
GNOME is 9.3 pretty well rocks hard, I think the quality of SuSE's GNOME install this time around is borne out by the small number of packages I've had to replace - the only replacement rather than new package or upgrade is gnome-session, and that was to sort out the braindead hard-coding of starting suseplugger and susewatcher at login.
Novell is really interested in delivering a solid product rather than using it as an experimental launching pad for another product.
Well, I'm currently downloading SuSE's 2.11.x packages, and prior to that I had no problem in building the latest GARNOME release, which is pretty forward looking. But, you talk as if being stable and solid is a bad thing. I bet that the packagers of these packages will have been as rigorous about them as any other, even though they are stated to be beta code.
When I began using Suse 9.3, I was a little disappointed by Suse's implementation of Gnome. It "appears" that much effort has gone into KDE (and it shows), but less into Gnome.
If you knew the sheer number of SuSE-specific patches, you wouldn't say that. Also, there's a very good reason why the default Panel configuration (for example) broadly matches the default GNOME one, and that's that the GNOME team have got it right.
Anyway, back to the point of this email. I obviously can customize my Gnome desktop, but before I continue to do so, I'd like to hear from other Suse Gnome users out there who can give me their impressions about working with Gnome in Suse? I'd be interested in hearing any perspectives about Gnome/Suse that you may have.
Find out what the community at large thinks on a number of issues, as well as finding handy links to things you might find helpful at http://planetsuse.org James, your friendly neighbourhood SuSE-GNOME hero. -- James Ogley james@usr-local-bin.org GNOME for SuSE: http://usr-local-bin.org/rpms Make Poverty History: http://makepovertyhistory.org
James Ogley wrote:
I've been tinkering around with Suse 9.3 for a few days, and I'm really impressed overall. I'd like to understand YAST a bit more (do gconf and YAST get along?),
Well, YaST is your system config tool, and GConf handles personal GNOME settings, it's like asking what the result of the last New York Yankees vs Manchester United match was.
implement apt-get,
ftp://ftp.gwdg.de/pub/linux/suse/apt/SuSE/9.3-i386/RPMS.suser-rbos/
improve or customize the Gnome desktop.
GNOME is 9.3 pretty well rocks hard, I think the quality of SuSE's GNOME install this time around is borne out by the small number of packages I've had to replace - the only replacement rather than new package or upgrade is gnome-session, and that was to sort out the braindead hard-coding of starting suseplugger and susewatcher at login.
Novell is really interested in delivering a solid product rather than using it as an experimental launching pad for another product.
Well, I'm currently downloading SuSE's 2.11.x packages, and prior to that I had no problem in building the latest GARNOME release, which is pretty forward looking. But, you talk as if being stable and solid is a bad thing. I bet that the packagers of these packages will have been as rigorous about them as any other, even though they are stated to be beta code.
When I began using Suse 9.3, I was a little disappointed by Suse's implementation of Gnome. It "appears" that much effort has gone into KDE (and it shows), but less into Gnome.
If you knew the sheer number of SuSE-specific patches, you wouldn't say that. Also, there's a very good reason why the default Panel configuration (for example) broadly matches the default GNOME one, and that's that the GNOME team have got it right.
Anyway, back to the point of this email. I obviously can customize my Gnome desktop, but before I continue to do so, I'd like to hear from other Suse Gnome users out there who can give me their impressions about working with Gnome in Suse? I'd be interested in hearing any perspectives about Gnome/Suse that you may have.
Find out what the community at large thinks on a number of issues, as well as finding handy links to things you might find helpful at http://planetsuse.org
James, your friendly neighbourhood SuSE-GNOME hero.
James, perhaps you can enlighten me, but here are some problems I've noted with GNOME and I'm not alone. You see the latest versiom of a Gnome app, it calls for a number of co-reqs/pre-reqs. You try to install the pre-reqs, it calls recursively for others, you finally get them all installed and you break other apps. Your new app (many many ages ago - gnomemeeting and gimp) doesn't work correctly or fails to start. I don't know if this is a thing of the past as recent versions of gimp have not needed any other upgrades. I tried building garnome for about a year, gave up about a year ago, never got a successful build. Do you have to perform major surgery when some new apps appear or is it more predictable now? Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Chaitanya Krishna A wrote:
Just in case you get any other rash urges to exercise commands like that in a panic: DON'T exit a root shell when you have just done something likely to crash the system.
I usually think I don't panic, but I did. Got to improve. Next time if I do something dumb, I will not panic (at least try not to).
Just remind yourself in future specifically to NEVER EVER exit a root shell after some desastrous action. Believe me, sooner or later you WILL have opportunity to use that advice. Use another terminal or ssh to verify that you have indeed rectified your mistake and can login as root.
In that case you should be able to use the rescue cd to boot up, chroot to your original system and then use passwd to give root a password.
I did use the rescue CD. I don't understand this chroot thing. Can you elaborate on that a bit.
When you boot the rescue CD the root volume "/" used is from the cd. So any action you try to execute on /etc or /sbin will be executed on the cd files. The command chroot mounts another volume as the root volume. In this case you need to know which device on your hdd is the root volume, something like /dev/hda2 or /dev/sda3. So, you boot the rescue CD and thus you are root. Then you execute "chroot /dev/sd2" (or whatever YOUR root device is). Afterwards you have a running root shell and your normal filesystem is mounted. Then you should be able to run any root command you need.
PS: if you still feel adventurous and decide to experiment with files like passwd manually, you might want to make a BACKUP of it first!
Ya I did make a backup. But then I think the harm has already been done to the files before I made a backup.
If you have only changed the file permissions then the damage is not really significant. Many years ago I remember that I accidentally gzipped all the files in the /etc directory and I also panicked. Fortunately it was a test system with nothing installed yet. Sandy -- List replies only please! Please address PMs to: news-reply (@) japantest (.) homelinux (.) com
On Sat, 30 Jul 2005 14:14:50 -0700 (PDT) Chaitanya Krishna A <icymist82@yahoo.com> wrote: > I did use the rescue CD. I don't understand this chroot thing. Can you > elaborate on that a bit. chroot(1) allows you to run a shell with a different root file system. When you boot the rescue system, your root file system is in a ramdisk. But if you need to reset your root password, what you do is: 1. Mount the root file system from your normal boot HD: mount /dev/hda1 /mnt 2. make that the new root file system: chroot /mnt You will now be in a shell where it thinks that /mnt is the root file system instead of the ramdisk / 3. Run the appropriate commands such as passwd(1). 4. Exit chroot like you would exit any other shell. If I remember in your case, you messed up either permissions or ownership. You do not necessarily need to use chroot for that. All the executable files in bin, /usr/bin, /sbin should be owned by root. But there are some exceptions for group. (from /sbin) -rwxr-sr-x 1 root shadow 6808 2005-03-21 10:53 unix2_chkpwd -rwxr-sr-x 1 root shadow 37483 2005-03-19 14:22 unix_chkpwd -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
participants (7)
-
Chaitanya Krishna A -
James Ogley -
Jerry Feldman -
mikus＠bga.com -
Paul Hoy -
Sandy Drobic -
Sid Boyce