Could wise people prepare here whole list of packages which shouldn't be optified because it will brick the device? It would be appreciated. Yes optyfing packages that nokia wanted to lay on rootfs may seem at least a bit crazy, but there are some reasons for people to want to do it. Since optyfing some of them bricks the device for whatever reason (mostly the technicalies of boot process), it seems scary to optify ones which not brick the device because beeing optified. We shouldn't have to be scary to do things that are safe (the point is the things are safe but we don't know which ones are safe, so it makes us scary to do the thing which are safe but we aren't sure that they are).

Bump.
10 chars

Good evening,
at the end I found the solution...

you have to edit it via VI by changing the sudoers file as with the latest build you cannot use anymore that tool and root is not in the sudoers file.


The steps to do are that:
-) Open the X-Terminal
-) Edit the sudoers file with the command vi /etc/sudoers
-) Add at the end the following line: root ALL = NOPASSWD: ALL

Save and Quit.

To Edit in Vi type the char "i"
When done use the ESC key for the command mode then type :w (ENTER) to save and :q (ENTER) to quit.


That's all :P

What on earth are you talking about? What solution? To what problem? On what device?

If you are talking about Maemo, then all you need to know about the root access has already been described. Install rootsh and type 'sudo gainroot' or just simply 'root' in the terminal. That's it. I've had my N900 for 3 years and have never touched the sudoers file. Ever.

Right. Plus you don't edit /etc/sudoers, you use visudo.
And maemo has the sudoers.d directory even better management of the sudoers file.

Yep,
that post made as much sense as this one.

@reinob
But what 'visudo' are you talking about?
Never used that on N900 (only ubuntu systems ).
And now when I run visudo I get:
visudo: no editor found (editor path=/bin/vi)
but vi is in /usr/bin/vi ?

p.s.: lived well with sudoers.d and update-sudoers

Dear pichio,
it's about that: http://talk.maemo.org/showpost.php?p...2&postcount=15


Regards.

And maybe you read the answers over there?
http://talk.maemo.org/showpost.php?p...2&postcount=16
http://talk.maemo.org/showpost.php?p...6&postcount=17

And yes, he read that as well.

And another one: we are all easy.
--edit: you edited your post (fast enough)

But posting something that nobody can interprete will not receive an answer by anybody. (@pichlo )

So please try to rephrase what all this is about. And we are going to help...

That post is in an entirely different thread. As peterleinchen correctly points out, I have seen it. And the answers. But tell me, will Joe Bloggs who comes to this forum next week and finds your post know which crystal ball to look into to understand what you are on about?

Not to mention that the post you've so proudly linked is just as incoherent and has been given at least two correct answers.

The last few posts (and this one) are well off topic. It looks like sev7en posted in the wrong thread. Can someone with mod privileges tidy this up please?

Try exporting EDITOR=/usr/bin/vi or set it to the editor of your choice.

This probably ought to be fixed in CSSU as the default editor should really point to something that actually exists!

Having said all of that, if I recall correctly, isn't there a Fremantle quirk where /etc/sudoers gets overwritten on every reboot?

...and having said that too , the default editor still ought to be fixed as it's used by many applications, not just visudo.

EDIT: I've just realised that other applications actually correctly invoke /usr/bin/vi as the editor when EDITOR is not set so it looks like this is actually a visudo bug.