Active Topics

 


Reply
Thread Tools
Posts: 1,808 | Thanked: 4,272 times | Joined on Feb 2011 @ Germany
#31
Originally Posted by pali View Post
If you want still use udev, then you must have / and /usr on same partition.

So rather prepare system image for SD card, not for internal n900 nand.
The question is whether it makes sense at all to use udev for a fixed-hardware device like the N900.

In the old days I actively refused to install udev on my PCs (but I also refused to update to kernel 2 because I hated modules . I don't know how dependant Maemo/Debian is on udev though, so if it has to stay there, so be it.

But I honestly cannot believe that udev doesn't allow a separate /usr partition. That's like so, how can I say, anti-Unix.
 

The Following 7 Users Say Thank You to reinob For This Useful Post:
Posts: 1,225 | Thanked: 1,905 times | Joined on Feb 2011 @ Quezon City, Philippines
#32
FWIW, it's possible to separate /usr on a udev system.
(IIRC, there is a warning added that will simply complain about it.)

The downside is that you'll have to use the /sbin/preinit kludge to set up the mountpoints before you run /sbin/init.
(This is the method a certain Lennart suggested on his original article about systemd.)

Whether such a kludge would be supported by the Maemo developer community is up for (heated) debate.

IMO, stuff / and everything else except for MyDocs into mmcblk0p2, and disregard the OneNAND space. It's tiny, even for a base Debian install. (or turn it into a big RescueOS, that's another idea)
__________________
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.
 
Posts: 2,154 | Thanked: 8,464 times | Joined on May 2010
#33
Originally Posted by reinob View Post
But I honestly cannot believe that udev doesn't allow a separate /usr partition. That's like so, how can I say, anti-Unix.
So look at how Lennart Poettering crippled udev and how he writing programs/daemons. He does not care about unix standards and other unix systems (bsd, ...).

Really now when udev is part of systemd, /usr and / must be on same partition (or /usr must be mounted before starting udev). But in systemd mount process is done after starting udev which creating files in /dev (also device for /usr).

And now all linux distributions (except small epsilon) depends on udev...
 

The Following 6 Users Say Thank You to pali For This Useful Post:
Posts: 839 | Thanked: 3,386 times | Joined on Mar 2009
#34
I started own thread about libc: http://talk.maemo.org/showthread.php?p=1329134

I have postponed optification issue, maybe it is worth of own thread.

-----
I reread what I know about gcc-4.7 and thumb, and realized that gcc-4.7 is not producing thumb-code as default, so there are no reason to use gcc-4.2 (unless some specific package is really needing it).


I have started to build packages from squeeze, ready packages goes to my repository (link in first post). There are not many for the device.

I have learned that Debian is not ready for fully built from scratch, e.g. there are circular build-dependencies, read more: http://wiki.debian.org/DebianBootstrap

So some packages can't be built with sbdmock, but they need to tuned and compiled manually, without some of the dependencies. Typically documenting tools cause harm as they are used by many package, but compiling them need other packages.

----
Some details for sbdmock
*create own local repository containing e.g. newer dpkg-dev and other libraries.
Creating local repository:
Code:
sudo apt-get install dpkg-dev
mkdir -p /tmp/ownrepo
cp *.deb /tmp/ownrepo
cd /tmp/ownrepo 
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz
And row to the /etc/apt/sources.list (or sbdmock-conf)
Code:
deb file:/tmp/ownrepo ./
And then use apt-get source PACKAGE_NAME

*there are packages that are not listed in debian/control, but still needed to build package, e.g. man-db, fakeroot and (working) gettext. Unpack them to the rootstrap-file.

Code:
#unpack rootstrap
tar zxf maemo-sdk-rootstrap_5.0_armel.tgz
#unpack needed packages
ar x /tmp/man-db.deb
tar xf data.tar.gz
#pack rootstrap again
tar czf maemo-sdk-rootstrap_5.0_armel.tgz bin  boot  cdrom  etc  floppy  home  initrd  lib    media  mnt  opt  proc  root  sbin  srv  sys  tmp  usr  var .dev
*Downloading squeeze source packages.
On host, disable other deb-src on /etc/apt/sources.list and use only:
Code:
deb-src http://ftp.fi.debian.org/debian squeeze main
(use server near to you).

----
Not using wheezy, is because it needs newer debhelper and debhelper comes from scratchbox (devkits: debian-squeeze). Current situation of scratchbox is not good (e.g. check: scratchbox.org hint:dead).

--------
[EDIT there was false information before]
I separated Maemo5 open packages, there are 199 packages which is also in Debian Squeeze. And 1188 packages only for Maemo. This does not count renamed packages:
http://paste.ubuntu.com/5617449/
[/EDIT]

Last edited by AapoRantalainen; 2013-03-15 at 19:24.
 

The Following 19 Users Say Thank You to AapoRantalainen For This Useful Post:
Posts: 1,203 | Thanked: 3,027 times | Joined on Dec 2010
#35
Originally Posted by AapoRantalainen View Post
I reread what I know about gcc-4.7 and thumb, and realized that gcc-4.7 is not producing thumb-code as default, so there are no reason to use gcc-4.2 (unless some specific package is really needing it).
Off topic, but this information may be useful for the Alopex guys as they're targeting thumb only at the moment because of reliance of its' gcc version.

With regards to circular dependencies, this is the same sort of issue I was facing when trying to build Debian from scratch a few years back, dropping i386 support in favour of a pure i686 build instead of only certain packages. I just had some time to kill whilst playing about IIRC I had built a toolchain using a mix of LFS and Debian patches with its own version feature stripped version of apt and dpkg. This way I could use dpkg-buildpackage to build the debs of the system but install them using a different root. I think I hit an issue when rebuilding apt or dpkg because of a dependency on po4a (again...IIRC) but it needed dpkg to be built with certain features enabled, which couldn't be done without po4a built.

Glad they now make this clearer on the wiki.
 

The Following 8 Users Say Thank You to Android_808 For This Useful Post:
Posts: 249 | Thanked: 277 times | Joined on May 2010 @ Brighton, UK
#36
Just wanted to chip in...you're doing what I've wanted to do for the last couple of years, but life's been conspiring against me for awhile now. Well done though...and I look forward to contributing to your project in the future
 

The Following 5 Users Say Thank You to mr_jrt For This Useful Post:
Posts: 3,328 | Thanked: 4,476 times | Joined on May 2011 @ Poland
#37
Originally Posted by bennypr0fane View Post
stupid layman question:
why do you think going straight for Wheezy is not an option?
Or maybe ubuntu oneiric?

There are many patches in the Maemo (or even Harmattan) gitorious repos. And sometimes originally nokia-binaries (was an occurence in Harmattan) get open-sourced in gitorious. E.g. libbme got open sourced but w/o packaging...

Maybe we can pull the Nokia packages from Harmattan if possible?
__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here

Last edited by marmistrz; 2013-03-21 at 10:30.
 

The Following User Says Thank You to marmistrz For This Useful Post:
Sohil876's Avatar
Posts: 130 | Thanked: 132 times | Joined on Jan 2013 @ India
#38
Originally Posted by marmistrz View Post
Or maybe ubuntu oneiric?

There are many patches in the Maemo (or even Harmattan) gitorious repos. And sometimes originally nokia-binaries (was an occurence in Harmattan) get open-sourced in gitorious. E.g. libbme got open sourced but w/o packaging...

Maybe we can pull the Nokia packages from Harmattan if possible?
I think basing on debian is better, i really dont like the way ubuntu is going, plus there is no gain in rebasing maemo on ubuntu over debian is there?
 

The Following 6 Users Say Thank You to Sohil876 For This Useful Post:
Posts: 839 | Thanked: 3,386 times | Joined on Mar 2009
#39
Now I have more than 300 packages on my own repository (check opening post). Most of them are Debian-squeeze packages compiled with (Maemo's) gcc-4.7.2. Not much of them are meant to be installed to the device, but they are helpers for SDK.


There are couple of packages fetched straight from debian armel. (Because they had circular dependency loops, or some other critical compiling issue)

And couple of packages comes (sources) from Ubuntu Precise (if debian's version has something weird, e.g. gzip depends mingw or I know that I want newer version just now, e.g. cmake).

I have installed almost every package to scratchbox but it is possible that there are still non-installable packages (and there are also packages conflicting each other, which is typical on every debian-based system).

-------
Technical details: If you install (let say) perl to scratchbox, you need to disable scratchbox's perl. Some packages can be disabled just dropping them out of devkit-list, some needs more force (sudo rm /scratchbox/tools/bin/gzip).

And same way there are now debhelper8 which can replace scratchbox's older debhelper (so wheezy/sid is just around the corner).
 

The Following 16 Users Say Thank You to AapoRantalainen For This Useful Post:
Posts: 3,328 | Thanked: 4,476 times | Joined on May 2011 @ Poland
#40
What about upgrading the whole scratchbox as a next step? Current Fremantle qemu is a little buggy (Harmattan target fails to work with it, in Fremantle target lupdate segfaults, and so on)

Plus if we add newer versions to "our" scratchbox we may not need to have all these SBOX_REDIRECT_IGNORE
__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here
 

The Following 5 Users Say Thank You to marmistrz For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 22:16.