maemo.org - Talk
Page 74 of 84 « First 647273 74 7576 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)
-   -   Easy Debian Fremantle Beta Testing (https://talk.maemo.org/showthread.php?t=34550)

Estel 2013-06-10 21:41
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by pichlo (Post 1350866)
I have since moved on to a bigger challenge, trying to install and run Debian packages directly without chrooting. I have not had much success yet as per a couple of posts above but now I have a spare device to thrash so I am not giving up yet.
There is a thread somewhere (by AapoRantalainen) about effort to update all Maemo packages to Squeezy, by resolving problems, one at a time, that arise during doing so. Considering where they are after some months (with many people participatingj, I'm not sure if it is doable idea - and it seems like only way to allow you installind *additional* packages from Squeeze. But, do not want to discourage you - you may want to search for that thread and cooperate with them, if you're still wanting to try :)

/Estel

Estel 2013-06-11 11:37
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by resolved, see bottom of post
After some testing, I noticed, that while most programs are working OK ( even heavy ones - GIMP, for example), some essential (roxterm) or important (chromium) are not. Sigh, even some simple things - like network monitor - misbehave.

I'm pretty sure, that copy of image (which I used to extract content into new chroot) was free of such weirdos, so I don't know if something is wrong with my new directory-based chroot (on mmcblk0p2), or if it's unrelated. I tried to reinstall offending programs, but I got info that:

"Value testing is incorrect for APT::Default-release, because such release is not available in sources".

I'm pretty sure, that I have seen such error and fix for it in this thread, but I can't recall nor re-find it, now. It's probably something trivial - any hints?

/Estel

//Edit

Here is content of my apt sources:

Code:
deb http://ftp.pl.debian.org/debian wheezy main
deb http://http.us.debian.org/debian wheezy main
deb http://security.debian.org/ wheezy/updates main
deb http://www.deb-multimedia.org wheezy main
Am I missing something?
Resolved:Problem with apt was caused by spurious entry in /etc/apt/apt.conf. Furthermore, it turned out, that reinstall isn't needed - see:
http://talk.maemo.org/showpost.php?p...postcount=2924

pichlo 2013-06-11 11:53
Re: Easy Debian Fremantle Beta Testing
 
Yes, testing is not applicable to Wheezy. I removed it and after that apt worked fine. I think it was in one of the preferences files that confused apt but I don't remember which one. There aren't that many of them anyway, just have a look around.

You yourself mentioned that Chromium was broken in Wheezy because of some downstream bugs. I don't use Chromium so I never noticed.

Estel 2013-06-11 21:03
Re: Easy Debian Fremantle Beta Testing
 
Thanks, I'll try to find this myself. As for chromium, I'm talking about squeeze one, of course.

// Edit

OK; now I feel ashamed - offending entry about Testing was in /etc/apt/apt.conf. removing file (or it's content) did the trick.

Quote:
Originally Posted by Resolved
Now, something more serious, that seems to be related to moving into directory-based chroot - after most operations, I get this error in terminal:

Code:
Couldn't save journal, openpty() failed (/dev/pts is not mounted?)
I could mount it manually, but I would rather like to find why it isn't prepared as it should at chrooting time. Any ideas?

//Edit 2

Just checked mount:
Code:
mount
none on /dev/pts type devpts (0)
/dev/mmcblk0p2 on /home type ext4 (0)
/dev/mmcblk0p1 on /home/user/MyDocs type vfat (0)
So, wtf?

// Edit 3

Code:
Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[FAIL] Can't start system message bus - /proc is not mounted ... failed!
Something seems to be very wrong with mounts - this one really isn't mounted, as per mount output in edit 2. No idea why, I'll try to investigate.
Resolved:

It turned out, that I had spurious file /var/lock/qmount-complete in my ED backup image (which I used to extract ED from). Normally, this file would be deleted on closing chroot, but due to it's existence (and content, originating from using dedicated partition and mounting it as /.debian), qchroot got confused, and skipped whole part of script, responsible for mounting hardware, dbus, and friends.

In itself, it wouldn't be big deal, as spurious file would get deleted on closing chroot, and new one (with correct content) would be created on new start of ED (i closed and opened it many times). Hoever, here interfered effect of my stupid idea, to unpack ED into /home/.debian, yet, create symlink pointing to it, from /.debian - and use the latter as chroot dir.

Yea, I have no idea what I was thinking yesterday - this was completely unnecessary complication, and only reason for it, was that I was using /.debian as mount point for dedicated partition in past, and had it already in .chroot config file. Instead of just changing it to /home/.debian, I created mess by symlinking :stupid: (which was more work than just fixing it in config, anyway, especially, that I had to put "none" for IMG= in config, no matter what...)

Even leaving my stupid idea aside, it *should* work, and worked for most things, *except* for what it was intended for ;) (Maemo knew about symlink, but ED couldn't from it's chroot jail, so, despite having all things mounted to /.debian/*, /home/.debian couldn't use it), *and* closechroot. Method of unmounting things in the latter isn't bulletproof enough to determine symlinks - it checks /proc/mounts for names containing path to chroot (which was symlink), while /proc/mounts have symlinks targets listed there, not symlinks themselves (obviously).

This left me with whole lotta mess of remaining "ghost mounts". I cleared all of it, got rid of symlink, and voila, everything works. Lesson earned - really think twice, before getting such stupid ideas s symlinking chroot dir :P
---

The plus is that, while searching for case, I went through reading all ED (and, generally, easy-chroot) components - refreshing my idea about what is there, and what isn't. It seems, that my knowledge raised much since last time I've seen them - this time, I wasn't having problems understanding what is going on and why (which explains, how pitifully low my level of understanding was back then, few months ago :P ).

As a result, I fixed some routines that were less-than-bulletproof, some trivialities, and added new functionality here or there (like ability to define custom string of filesystem options in .chroot config file, instead of hard-coding it into easy-chroot's guts, everytime we want to use dedicated partition with some optimized mount-time parameters.

IF autobuilder is going to ever start working again, I'll try packaging it up, and releasing first update to easy-debian main package in a years (wooho!). Of course, my little tweaking is just an addition - mostly, it will contain various bugfixes scattered around this thread (like the ones allowing to seamlessly using directory for chroot, instead of dedicated partition or IMG file.)

/Estel

nokiabot 2013-06-12 16:06
Re: Easy Debian Fremantle Beta Testing
 
How to get gprs working in ed??

Estel 2013-06-12 17:20
Re: Easy Debian Fremantle Beta Testing
 
Have you actually tried before asking this? It works out of the box, as soon as you enable it in Maemo. As long as ED is working as it should.

marmistrz 2013-06-28 16:57
Re: Easy Debian Fremantle Beta Testing
 
Estel & other devs: What about making a minimal image (max 1GB)? It'd contain only the must stuff (apt, lxde) but no gimps & etc. from Deb Squeeze (as it's latest stable on n900)

pichlo 2013-06-28 18:13
Re: Easy Debian Fremantle Beta Testing
 
There is a barebone image (about 50 MB), just search the thread. I would look it up for you but I am typing this from my N900. Starting from that, I installed just Iceweasel and Office and grew to just around 300 MB. In a directory under /home. No extra partitions or whatever. There were some small issues, check a few pages back to see my solutions.

Estel 2013-06-28 23:57
Re: Easy Debian Fremantle Beta Testing
 
I'm using directory-based ED without any problems, but noticed funny glitch. The thing is that, I used to call "debbie exit" from /etc/event.d/ script at boot, just to have ED mounted all the time (and avoid partition mounting delay, when I want to do something in ED quickly). It worked flawlessly.

Now, using directory based ED, it *always* produce borked chroot - everything seems fine, except that no hardware/system is mount/bind. If i close ED and open it again (even via the same 'debbie exit'), it mounts just fine.

Not that it matters anymore, as using directory based chroot, there is 0 (zero) delay in ED startup, even if closed "to bare ground". I'm just curious - I wasn't able to find anything in qchroot scripts, that would explain different behavior when called from event.d, than executed normally. Or, why it acts differently, when using directory, instead of separate partition.

/Estel

pichlo 2013-06-29 08:13
Re: Easy Debian Fremantle Beta Testing
 
My first instinct was timing but since you say it worked then that must be off. Except - your ED directory is somewhere under /home, right? Perhaps you try to automount ED before /home is mounted. It worked when ED was on its own partition because the timing didn't matter. Just a speculation, I'm sure you've considered that already.

I too was considering automounting ED on boot but decided against because of the mess it makes in mass storage mode.

marmistrz 2013-06-29 08:52
Re: Easy Debian Fremantle Beta Testing
 
pichlo: you should gather all the information about directory based chroot in one place - otherwise it'll all become practically lost (when ed thread becomes 350 pages long. A new thread for the tutorial would be the best. I might help with packaging if you decide to push dir ed scripts to devel.

Is the barebone image this one: http://qole.org/files/basic-debian-chroot-fs.tar.bz2 ?

pichlo 2013-06-29 11:37
Re: Easy Debian Fremantle Beta Testing
 
Yup, that's the one. Note that unlike all other images which are literally that, images that you can mount, this one needs unpacking into a prepared space, be it an image, partition or a directory.

My and Estel's experience with directory based ED is summarized in the (currently) last three or four pages. I never thought about creating a new thread for that. It seems appropriate to talk about it here and frankly, I was not expecting much interest from anyone except the die-hard geeks.

marmistrz 2013-06-29 12:39
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by pichlo (Post 1355540)
Yup, that's the one. Note that unlike all other images which are literally that, images that you can mount, this one needs unpacking into a prepared space, be it an image, partition or a directory.

My and Estel's experience with directory based ED is summarized in the (currently) last three or four pages. I never thought about creating a new thread for that. It seems appropriate to talk about it here and frankly, I was not expecting much interest from anyone except the die-hard geeks.
Yeah, but you know, as the thread gets larger it'll all be lost. Or you can just summarize everything in one post and ask qole to put the link in the OP. It'd be nice to post the updated scripts. I can push them to extras-devel.

Estel 2013-06-29 12:59
Re: Easy Debian Fremantle Beta Testing
 
There was a plan to start new thread (as it's not beta, anymore), after releasing fully working Wheezy image. In last few pages, I've also mentioned, that I gathered all fixes to qchroot&friends from last few months, added my minor tweaks (to fix stupid things like mounting Maemo's /home/user, then unmounting it again 0.5 second later), and I'm planning to release updated ED package into repos.

Now, the problem with Wheezy, is that it contains shitload of problems re ARM, that mainstream doesn't seem to be interested in fixing. Particularly, gparted spazms out due to glibc error:
Code:
*** glibc detected *** /usr/sbin/gpartedbin: free(): invalid pointer: 0x40c67514 ***
...which I'm sure isn't gparted problem, as I tested reverting to versions, that were working before (and even older - tested to as old ones as lenny). This imply mentioned glibc problem, which, in turn, may mean that many other programs may not work properly (just no one tested wheezy ED as thoroughly to detect them).

There are also smaller, but irritating things, like GIMP crashing on text input brush, or chromium not working at all (I'm using Squeeze one in Wheezy, as workaround). The latter for sure applies to whole ARM, not only our humble case, and is present+untouched (by mainstream) for AGES.
---

Now, this probably could be work-arounded by doing some strange Squeeze-Wheezy mix (downgrading glibc, altering dependencies, maybe recompiling some things to use older component), but we already had it with lenny/squeeze mix at ED origins, and I'm not going to even come close to trying it, again. Currently, I'm rather considering downgrading to Squeeze as a whole (mainly, due to this glibc problem, other thing are workaroundable by downgrading particular programs)..

/Estel

// Edit

Quote:
Originally Posted by pichlo (Post 1355496)
My first instinct was timing but since you say it worked then that must be off. Except - your ED directory is somewhere under /home, right? Perhaps you try to automount ED before /home is mounted. It worked when ED was on its own partition because the timing didn't matter. Just a speculation, I'm sure you've considered that already.
The thing is, that it's not problem with mounting chroot dir itself. Things that doesn't get mounted are:
Code:
/sys on /home/.debian/sys type bind (bind,rbind)
/var/run/dbus on /home/.debian/var/run/dbus type bind (bind,rbind)
...and other like that, while /home/.debian itself is mounted OK. I've even prepared a dummy script in /etc/event.d/, that displays notification text first (requiring closing it by hitting OK), and invoke 'debbie exit' only afterwards - so, I was able to wait few minutes from device bootup, to filter out timing problems. To no avail - it's acting the same.

What made me curious, is that those things shouldn't behave differently with partition or directory based ED *at all*. It's no a real problem, as I said, just... strange.

BTW, pichlo, I'm pretty sure, that you underestimate impact of your directory-based ED ressurecting :) Many people were using partition-based ED (as opposed to image file-based), for performance reasons. For sure, just like I advocated it in the past, I'm going to do so with directory-based one. There is simply no reason to do separate partition, now* - directory is superior in every way.

*except for fact, that filesystem corruptions caused by N900 unexpected reboots, during ED usage, would result in ED separate partition corruption (most likely) *only*, while having it on /dev/mmcblk0p2 means corrupting home filesystem, *if* corruption happens.

But, in reality, it is not as dangerous as it sounds - in such cases (just like with separate partition for ED), only ED directory entries may get corrupted (in cases, where real Maemo home entries get spoiled too, even separate partition wouldn't help). So, backuping OptFS and restoring it on mkfs'ed p2 (backupmenu way) works 100% reliably (and we need to just nuke chroot dir, and restore it from backup, like with every else normal file/directory).

Benefits due to space-savings clearly outweight it.

/Estel

fw190 2013-06-29 13:18
Re: Easy Debian Fremantle Beta Testing
 
I have a small problem - 3,73GB sd card with one fat and two swap partitions as recomended in flopswap. This gives me 2216mb for ED. Estels image is to big. I have tried to download Sulus image and install open office in it but failed after some error. So I have decided to download the smalles file which marmistrz was talking about. When trying to extract the file to fat32 partition is says the the file system doesn't cover symbolic links. I have tried to use other file systems but no luck. Generally speaking I would need jus ED with open office or libre office. Other programs are not needed and never used. Any hints how to do it? noob hints I mean

Estel 2013-06-29 13:22
Re: Easy Debian Fremantle Beta Testing
 
Sounds like you could:

a) use directory-based ED on your home (best performance)
b) put image under MyDocs, then shrink it by uninstalling what you don't need
c) use 8GB sd cards, they're cheap as ice nowadays (3$ or so on polish wannabe-ebay auction site - heck, I bought mine 32GB Sandisk class 4 for 16$ inc. shipping).

marmistrz 2013-06-29 20:00
Re: Easy Debian Fremantle Beta Testing
 
Is the ED squeeze sources.list somewhat different than for desktop?

pichlo 2013-06-29 20:29
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by Estel (Post 1355565)
Sounds like you could:

a) ...
b) ...
c) ...
d) format your 2216MB partition as ext3.

Estel 2013-06-29 23:08
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by pichlo (Post 1355663)
d) format your 2216MB partition as ext3.
Just for clarification, as he may not get whole idea - then, extract content of image to this partition, and use it as partition-base ED (3GB partition uses space for "free space" too, in reality, it's around 2GB). But, that would make you tight on available space, unless you uninstall unneeded stuff.

If i were You, I would got for a directory-based design, anyway - the faster you switch to a better option, the more performance you get. And if willing to use LibreOffice (I don't recommend depreciated OpenOffice, which is now more corporate than FOSS, in spirit), using image-based ED will hurt your performance a LOT (few people made comparisons, buried somewhere in this thread - differences were more than noticeable).

/Estel

fw190 2013-06-30 07:38
Re: Easy Debian Fremantle Beta Testing
 
As recomended I have formated the parition to ext3. Now I could copy all the files from my pc but trying to start ED gives me "you have no debian.img.ext2 file on your memory card". I have tried to search what does it mean to "use it as partition-base ED" but came out with nothing.

pichlo 2013-06-30 10:39
Re: Easy Debian Fremantle Beta Testing
 
@fw190, you may need to edit /home/user/.chroot (if I got the path right, I don't have ED installed right now to check). The file is well commented so it's easy to figure out what to do.

fw190 2013-06-30 12:03
Re: Easy Debian Fremantle Beta Testing
 
I have found the file:

Code:
# Sample config for chroot

# Device or image containing Debian filesystem.
# Default: first in /home/user/MyDocs/debian*.img*, /media/mmc1/debian*.img*
# Some examples:
#IMGFILE=/home/user/MyDocs/debian-squeeze-m5.img.ext2
#IMGFILE=/media/mmc1/debian-squeeze-m5.img.ext2
#IMGFILE=/dev/mmcblk1p2
#IMGFILE=/dev/mmcblk0p4

# Filesystem used; must always be set when using a partition.
# Default: from extension of IMGFILE, or ext2.
#IMGFS=ext2

# Mount point for Debian.
# Default: /debian
CHROOT=/.debian

# New /tmp dir size for printing / PDF creation
# Default: 6M
#TMPSIZE=6M

# Debian user to drop privileges
# Default: user
#DEBUSER=user
Now how to tweak it to have it working? ;)

As I understand I have to change to ext3 but that is all

pichlo 2013-06-30 15:22
Re: Easy Debian Fremantle Beta Testing
 
Code:
# Sample config for chroot

# Device or image containing Debian filesystem.
# Default: first in /home/user/MyDocs/debian*.img*, /media/mmc1/debian*.img*
# Some examples:
#IMGFILE=/home/user/MyDocs/debian-squeeze-m5.img.ext2
#IMGFILE=/media/mmc1/debian-squeeze-m5.img.ext2
IMGFILE=/dev/mmcblk1p1
#IMGFILE=/dev/mmcblk0p4

# Filesystem used; must always be set when using a partition.
# Default: from extension of IMGFILE, or ext2.
IMGFS=ext3

# Mount point for Debian.
# Default: /debian
CHROOT=/.debian

# New /tmp dir size for printing / PDF creation
# Default: 6M
#TMPSIZE=6M

# Debian user to drop privileges
# Default: user
#DEBUSER=user
Assuming your ext3 partition is mmcblk1p1. Substitute as necessary.

marmistrz 2013-06-30 15:30
Re: Easy Debian Fremantle Beta Testing
 
Posting here the sources.list of Estel's squeeze in case anyone needs it (so that dl of the image isn't necessary)

Code:
# deb http://http.us.debian.org/debian lenny main
deb http://backports.debian.org/debian-backports squeeze-backports main
deb http://ftp.pl.debian.org/debian squeeze main
#deb http://ftp.de.debian.org/debian wheezy main
#deb http://http.us.debian.org/debian squeeze main
#deb http://security.us.debian.org/ lenny/updates main
deb http://security.debian.org/ squeeze/updates main
#deb http://www.debian-multimedia.org lenny main
deb http://www.debian-multimedia.org squeeze main
#deb http://www.debian-multimedia.org sid main
#deb http://http.us.debian.org/debian experimental main
#deb http://packages.tspre.org squeeze main
#deb http://packages.tspre.org sid main
#deb-src http://http.us.debian.org/debian lenny main
#deb-src http://http.us.debian.org/debian squeeze main
#deb-src http://http.us.debian.org/debian sid main
/edit:

@Estel: why did you comment out
Code:
deb http://packages.tspre.org squeeze main
?

/edit2: well, this one is down. As well as debian-multimedia isn't working.

fw190 2013-06-30 17:16
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by pichlo (Post 1355768)
Code:
# Sample config for chroot

# Device or image containing Debian filesystem.
# Default: first in /home/user/MyDocs/debian*.img*, /media/mmc1/debian*.img*
# Some examples:
#IMGFILE=/home/user/MyDocs/debian-squeeze-m5.img.ext2
#IMGFILE=/media/mmc1/debian-squeeze-m5.img.ext2
IMGFILE=/dev/mmcblk1p1
#IMGFILE=/dev/mmcblk0p4

# Filesystem used; must always be set when using a partition.
# Default: from extension of IMGFILE, or ext2.
IMGFS=ext3

# Mount point for Debian.
# Default: /debian
CHROOT=/.debian

# New /tmp dir size for printing / PDF creation
# Default: 6M
#TMPSIZE=6M

# Debian user to drop privileges
# Default: user
#DEBUSER=user
Assuming your ext3 partition is mmcblk1p1. Substitute as necessary.
Here is what I did:
-I have ext3 and two swap on my uSD card
-I have downloaded debian-5-chroot-rootfs.tar.bz2
-extracted it to ext3 partition on my sd card (not to a folder - jus on the card)
-I have put the chroot file as you wrote in the apropriate place

While trying to start lxde with icon in menu nothing happens. This means I did something wrong or missed a step or two.

I can start Debian chroot which gives:
Code:
Chroot dir specified: /.debian
/dev/mmcblk1p1 specified in ~/.chroot
Mounting...
using device: /dev/mmcblk1p1
Using ext3 file system
mounting device: /dev/mmcblk1p1
.
..
...
....
mount: mounting /var/run/pulse on /.debian/var/run/pulse failed: No such file or directory
Everything set up, running chroot...
[root@chroot: /]
Also after inserting the card the cpu is running like mad. Could this be the tracker?

Could someone help?

pichlo 2013-06-30 19:06
Re: Easy Debian Fremantle Beta Testing
 
I'm sorry, fw190, but seriously, what did you expect in 54MB? A golden watch with a water feature? It's a barebone image, meaning you have nothing but the very basic components. Which means basically just the terminal, apt to install additional ppackages and their dependencies (except, IIRC, it was not quite as barebone as I would have liked, ISTR there were some extra packages already included which I had to remove - but I digress).

It looks like your system is running fine. The chroot works and you get a command-line prompt. You drive from there. If you want LXDE, install it. If you want Open/LibreOffice, install it. BTW I suggest starting from editing your /etc/apt/sources.list in your ED root and updating it with current Squeeze (or Wheezy if you feel adventurous) links. I believe the image has not been updated in years and contains some out-of-date hybrid.

I understand that the LXDE or Office icons on the desktop may be a little confusing. That's an unfortunate artifact of ED; Maemo knows nothing about packages you install in ED. So we have to cheat a little and create desktop files manually. Some of them are pre-made for you but it does not mean they point anywhere. For example OpenOffice may need editing to point to LibreOffice or vice versa and you may need to add entries manually for packages that do not have ready-made icons.

fw190 2013-06-30 19:45
Re: Easy Debian Fremantle Beta Testing
 
Hmm maybe I should write it more specific in my post. I have downloaded the 277mb file which after extracting gave more than 800mb and that is why I'm confused that it didn't work with the lxde icon and wrote about it.

pichlo 2013-06-30 20:04
Re: Easy Debian Fremantle Beta Testing
 
Hmm, I have no idea about that one. And I have no way to try out as both my N900s are a bit indisposed right now. Sorry.

Estel 2013-06-30 20:30
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by fw190 (Post 1355786)
Code:
mount: mounting /var/run/pulse on /.debian/var/run/pulse failed: No such file or directory
That one is quite self-explanatory - it seems like you don't have (under Maemo) directory /.debian. Create it.

*If* it still doesn't work after that (and error about /.debian/var/run/pulse not existing still shows up), check, if you have /var/run/pule in the package you've downloaded. If not, there is something wrong with it.

Frankly, I have no clue what this debian-5-chroot-rootfs.tar.bz2 thing is - for sure, ti wasn't created by me. I don't know if you, accidentally, haven't decided to try some qole's unfinished WIP chroot content, not meant for end-users.

You should rather try one of provided images (*.ext3 or *.ext2 files), mount it, and extract it content to your partition.

/Estel

pichlo 2013-06-30 20:35
Re: Easy Debian Fremantle Beta Testing
 
Having gone down the barebone image route myself, I second Estel's suggestion. It is easier to take one of the finished images (Estel's are the best-polished ones) and remove things you don't need. Once done, just copy the content as it is to your target directory or partition. The ready-made images have a lot of the legwork done already, so you don't have to worry about things like key bindings, screen adjustment and what have you.

fw190 2013-06-30 20:56
Re: Easy Debian Fremantle Beta Testing
 
Estel & Pichlo - thank you for your advice. I'm downloading Estel image (which I was using previously with great sucess).

Estel - if I understand it corect I should download the image, put it in MyDocs and then remove unwanted software to shrink it? Should I do it with provided synaptics? Which packages to remove to shrink it to about 2,1GB? Libre and Chromium are must. Gimp would be nice :) If I uninstall the software how to extract everything from the image so I can put it into the partition on sd? Should I do it on my lubuntu with some archive manager?

Estel 2013-06-30 21:57
Re: Easy Debian Fremantle Beta Testing
 
You may install/uninstall using synaptic, aptitude, or apt-get - it doesn't matter, as long as you're doing it from inside ED. As for which packages, I have no idea, as what is "essential" wary from person to person.

As for extracting image after shrinking it - you may do it all from N900. You need to mount it first, then, you may copy it's content (which imply mounting your to-be debian partition, too. Be sure to close ED chroot, first! Then for example, do:

Code:
mkdir /tmp/debian-temp
mount /home/user/MyDocs/your-easy-debian-image-file.ext3 /tmp/debian-temp
mount /dev/mmcblk1p1 /.debian
cp -a /tmp/debian-temp/* /.debian/
#after copying ends
umount /.debian
umount /tmp/debian-temp
#be careful with typos in next command!
rm -r /tmp/debian-temp
Now, you should be able to use ED as normal, thanks to .chroot config file pichlo helped you to prepare. What you got, is essentially partition-based ED. Performance may be hurt a little due to having swap on same physical device as ED, but otherwise, it should work fine.

Remember, than any names I used are just mockup - for /tmp/ directory, you may create it with whichever name you want. /dev/mmcblk1p1 assumes, that it is your ext3 partition on SD card - if not, change it accordingly.

OTOH, if you're gonna tell me that you don't have "your-easy-debian-image-file.ext3" on MyDocs, or that "#after copying ends" command return errors, a bunny will die ;) (excuse poor pun, don't take it to the heart).

/Estel

fw190 2013-07-01 07:01
Re: Easy Debian Fremantle Beta Testing
 
Estel - no bad fealings ;) Will give it a shot.
I thought that ED and swap on SD was a good idea and ti would be faster then on emmc.

marmistrz 2013-07-01 07:03
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by Estel (Post 1355840)
That one is quite self-explanatory - it seems like you don't have (under Maemo) directory /.debian. Create it.

*If* it still doesn't work after that (and error about /.debian/var/run/pulse not existing still shows up), check, if you have /var/run/pule in the package you've downloaded. If not, there is something wrong with it.

Frankly, I have no clue what this debian-5-chroot-rootfs.tar.bz2 thing is - for sure, ti wasn't created by me. I don't know if you, accidentally, haven't decided to try some qole's unfinished WIP chroot content, not meant for end-users.

You should rather try one of provided images (*.ext3 or *.ext2 files), mount it, and extract it content to your partition.

/Estel
It's not the point. In chroot just `mkdir /var/run/pulse`. Does the trick

marmistrz 2013-07-01 11:49
Re: Easy Debian Fremantle Beta Testing
 
Well, I used the barebone image, upgraded to squeeze, installed lxde-core and xserver-xephyr (+gnumeric) and now am trying to fire up lxde.

Changed startlxde1 to startlxde in /usr/bin/debian-lxde

But the display is blank. The log is: http://pastebin.com/G9eVGUr1

Any ideas why it's happening?

/edit: is there any squeeze barebone image? there are some problems like fopen on man-db which should be fixed in newer releases

fw190 2013-07-01 11:55
Re: Easy Debian Fremantle Beta Testing
 
Estel. I ahve tried both as normal user and as root:
Code:
usyBox v1.10.2 (Debian 3:1.10.2.legal-1osso31+0cssu0) built-in shell (ash)
Enter 'help' for a list of built-in commands.

Nokia-N900:~# mount /home/user/MyDocs/debian-m5-estel.img.ext3
mount: can't find /home/user/MyDocs/debian-m5-estel.img.ext3 in /etc/fstab
Nokia-N900:~# /tmp/debian-temp
-sh: /tmp/debian-temp: Permission denied
Nokia-N900:~#

pichlo 2013-07-01 12:04
Re: Easy Debian Fremantle Beta Testing
 
Please read on the mount syntax. Particularly this bit:

(ii) When mounting a file system mentioned in fstab, it suffices to give only the device, or only the mount point.

Your image is not in fstab so you need to specify all operands. Try something like this as root for size:

mount -t ext3 /home/user/MyDocs/debian-m5-estel.img.ext3 /.debian

(Assuming /.debian exists and is where you want the image mounted. You can use any directory but I recommend using an empty directory to avoid issues.)

fw190 2013-07-01 12:46
Re: Easy Debian Fremantle Beta Testing
 
Hmmm I do not know much about commands but correct me if I' wrong:
mkdir /tmp/debian-temp - this makes the folder in tmp just for purpouse of copying
mount /home/user/MyDocs/your-easy-debian-image-file.ext3 - this mounts the image
/tmp/debian-temp - this moves me form / to debian-temp
mount /dev/mmcblk1p1 /.debian - this mounts the sd card
cp -a /tmp/debian-temp/* /.debian/ - this is copying files from temp to sd but what files as no command has copied any files to debian-temp?

saponga 2013-07-01 13:10
Re: Easy Debian Fremantle Beta Testing
 
Quote:
Originally Posted by fw190 (Post 1355974)
Hmmm I do not know much about commands but correct me if I' wrong:

mount /home/user/MyDocs/your-easy-debian-image-file.ext3 - this mounts the image
/tmp/debian-temp - this moves me form / to debian-temp
Nope... It's only one command... same line .:)

fw190 2013-07-01 13:30
Re: Easy Debian Fremantle Beta Testing
 
Dang - I thought that this is a new line - it looked like this in Estels post.
Code:
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso31+0cssu0) built-in shell (ash)
Enter 'help' for a list of built-in commands.

Nokia-N900:~# mount -t ext3 /home/user/MyDocs/debian-m5-estel.img.ext3 /tmp/debian-temp
mount: mounting /dev/loop0 on /tmp/debian-temp failed: Device or resource busy
Nokia-N900:~#


All times are GMT. The time now is 16:39.
Page 74 of 84 « First 647273 74 7576 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8