Reply
Thread Tools
Posts: 915 | Thanked: 3,209 times | Joined on Jan 2011 @ Germany
#3241
Just a request, not a demand:
If you create images based on mine, could you please NOT put "sulu" in the file name?

I've had some requests for help with "my" images, but since I usually don't try other images I don't really know what's going on there.
If YOU create an image, then it is YOU who deserves the credit (and needs to take the blame ). So people should first turn to you if they need help.
I'll happily help out if I can, but I don't like to stand in the first line in these cases.

Thanks!
 

The Following 8 Users Say Thank You to sulu For This Useful Post:
Posts: 368 | Thanked: 975 times | Joined on Aug 2013
#3242
I certainly don't think I contributed enough to call it mine, but it is fine by me to rename it. I haven't seen any posts about problems or questions about the image. I can only assume it is working without issues then...

Will remove the mediafire link this weekend so there is only one 'official' link to the file from qole.
 

The Following 6 Users Say Thank You to t-b For This Useful Post:
Posts: 4 | Thanked: 8 times | Joined on Jan 2015 @ Ukraine
#3243
What is the passwords for user and root in debian_jessie2sulu_armhf.img?
 
Posts: 915 | Thanked: 3,209 times | Joined on Jan 2011 @ Germany
#3244
Originally Posted by baranovskiykonstantin View Post
What is the passwords for user and root in debian_jessie2sulu_armhf.img?
If t-b didn't change the passwords, then they should be "user" and "root".
 

The Following User Says Thank You to sulu For This Useful Post:
Posts: 4 | Thanked: 8 times | Joined on Jan 2015 @ Ukraine
#3245
Originally Posted by sulu View Post
If t-b didn't change the passwords, then they should be "user" and "root".
I tried to use them. They are not correct.
 
Posts: 368 | Thanked: 975 times | Joined on Aug 2013
#3246
As far as I know I haven't changed any passwords - because I didn't need them. I used debian chroot for root access (no pw needed) and also user can be accessed without pw.

Can't test right now due to a recent re-install.
 

The Following User Says Thank You to t-b For This Useful Post:
Posts: 4 | Thanked: 8 times | Joined on Jan 2015 @ Ukraine
#3247
It happens when I use terminal from lxde session. When debian chroot are used password not needed, it is true.

P.S.

Ok,user just not setup. Password must be set with
Code:
$ sudo passwd user
from debian chroot and to add it to sudoers with
Code:
$ sudo visudo

Last edited by baranovskiykonstantin; 2016-10-06 at 03:52.
 

The Following User Says Thank You to baranovskiykonstantin For This Useful Post:
Posts: 175 | Thanked: 210 times | Joined on Mar 2013
#3248
Hello,

First of all I would like to say thanks for the images and the effort put in this.

I have a little problem coming from my side and I would need a little bit of help.

I already used Easy Debian on my previous N900 without any real issue, but today I tried to set it up on my second N900 on which I have made some significant changes.
So I will detail here the changes I made on my second N900 (and are related somehow to Easy Debian) and the error message I get when I try to launch an image.

First the error is :

Code:
~ $ debbie
Starting Debian shell...
Chroot dir specified: /.debian
No image file or partition specified.
ls: /home/user/MyDocs/debian*.img*: No such file or directory
/.debian has a qmount already!
/media/mmc1/debian_jessie2sulu_armhf.img already mounted on /.debian...
Everything set up, running chroot...
chroot: can't execute 'su': Exec format error
So apparently a problem with su.

The changes I've made to the second N900 (basically I wanted for the root password to be required for becoming root) :

Code:
/etc/sudoers.d/01sudo
user ALL = PASSWD: /usr/sbin/gainroot

/home/user/.profile
alias su='root'
I also had to change /etc/sudoers.d/chroot.sudoers from
Code:
Defaults env_keep+=GTK_MODULES
user ALL = NOPASSWD: ALL
to

Code:
Defaults env_keep+=GTK_MODULES
user ALL = NOPASSWD: /sbin/debian
so that the root password is required when using su (or root) command, but even without changing the chroot.sudoers file it still gives the error.

How can I correct this without giving away the security put in place (root password required to become root)?
Should I put something else in /etc/sudoers.d/chroot.sudoers?
 
Posts: 368 | Thanked: 975 times | Joined on Aug 2013
#3249
Originally Posted by Malakai View Post
I already used Easy Debian on my previous N900 without any real issue, but today I tried to set it up on my second N900 on which I have made some significant changes.
So I will detail here the changes I made on my second N900 (and are related somehow to Easy Debian) and the error message I get when I try to launch an image.

First the error is :

Code:
chroot: can't execute 'su': Exec format error
I've got the same error after installing a back-up image (created with BackupMenu) on a 2nd N900 I am using.
Everything works fine except Easy Debian. Not sure if it is a "su problem", the "Exec format error" part of the error seems to point to a kernel incompatibility.

Haven't had a lot of time to investigate the problem and interested in a solution as well.
 
Posts: 915 | Thanked: 3,209 times | Joined on Jan 2011 @ Germany
#3250
Are your N900s running kernel power? The armhf images need it.
 

The Following 3 Users Say Thank You to sulu For This Useful Post:
Reply

Tags
beta, debian, easy debian, extras-devel, fremantle, i <3 qole, squeeze

Thread Tools

 
Forum Jump


All times are GMT. The time now is 07:27.