OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Cardfs Or Altboot? What?
brickhead20
post Jun 30 2006, 02:00 PM
Post #1





Group: Members
Posts: 2
Joined: 30-June 06
Member No.: 10,287



OK this all did made sense. Now it isn't so clear sad.gif

Ok, am I supposed to use CardFS or altboot to move my files from RAM to SD? My aim is to use my SL-5500 as a webserver running apache-PHP. All seemed OK and simple, but I seem to be getting a lot of problems. Also I find after a hard reset in both running hentges ROMs, and normal OZ ROMs moved to the SD card full, the wireless fails after a reset, though it works on fresh clean installs.

Basically, what am I supposed to use, and why?

Whats the difference between CardFS and altboot?

Thanks for any help smile.gif

Rich
Go to the top of the page
 
+Quote Post
Ferret-Simpson
post Jul 4 2006, 01:17 PM
Post #2





Group: Members
Posts: 573
Joined: 8-June 05
Member No.: 7,295



Please help this guy, it took me bloomin' AGES to get him to buy a Z!

And I STILL say use the iPaq as a server.
Go to the top of the page
 
+Quote Post
CoreDump
post Jul 4 2006, 08:41 PM
Post #3





Group: Members
Posts: 715
Joined: 25-July 04
From: .de
Member No.: 4,094



QUOTE(brickhead20 @ Jul 1 2006, 12:00 AM)
OK this all did made sense. Now it isn't so clear sad.gif

Ok, am I supposed to use CardFS or altboot to move my files from RAM to SD?


s/RAM/flash

CardFS is not a full / on SD/CF but only a pre-compiled package selection which is installed / extracted onto SD / CF. It's basically the same as if you were to install packages to SD yourself using the package manager.

Altboot on the other hand may create a bootable installation on SD / CF / whatever from a tar.gz rootfs tarball. Its primary purpose is to "boot" your Z from something other than flash.

QUOTE
My aim is to use my SL-5500 as a webserver running apache-PHP. All seemed OK and simple, but I seem to be getting a lot of problems. Also I find after a hard reset in both running hentges ROMs, and normal OZ ROMs moved to the SD card full, the wireless fails after a reset, though it works on fresh clean installs.


"wireless fails" is not a useful problem description, now is it? smile.gif

QUOTE
Basically, what am I supposed to use, and why?

Whats the difference between CardFS and altboot?


See above.
Go to the top of the page
 
+Quote Post
brickhead20
post Jul 5 2006, 01:01 PM
Post #4





Group: Members
Posts: 2
Joined: 30-June 06
Member No.: 10,287



Thankyou! Yeah that makes some sense now, sorry, I tried comparing the two and couldn't see the exact difference.

The wireless seems to be sorted by reconfiguring it from fresh every time I use hard reset, though I'm not sure why it does it, at least I know how to fix it.

Well, Ferret, frig you. You got me confused with this in the first place!
Go to the top of the page
 
+Quote Post
spanky
post Jul 6 2006, 01:40 AM
Post #5





Group: Members
Posts: 10
Joined: 5-July 06
Member No.: 10,325



I was asking the same questions a couple of days ago, and because of problems with my SD card (1GB sandisk), the decision was made for me. If I ever tried to use AltBoot and boot off the SD, it would give errors with the SD card (don't have the exact text here now, but i think it was saying problems trying to mount it), and then just drop to the console. However there don't appear to be problems with the SD card, as I'm currently running using CardFS. I'm not sure whether the problems that were reported were with the card itself, or with the loop file, but I wasn't sure how to find out, and now that I'm running everything fine with cardFS, I'm not sure I want to try (at least not for a bit). I had a couple of altboot images on the card, and if I tried to use the SD card, it wouldn't even present me with the list of loop files to choose from, it would just give card errors. When I copied the files to a CF card it would present the list to choose from, but when I chose one I got the same errors.

While I now have a better understanding of the difference between altboot and cardFS, I still have a couple of questions.

Are you saying that when altboot is used, the entire OS and packages etc are all run directly from the SD card, but when cardFS is used the OS is running from flash, but the packages are installed and run from the card?

If this is the case, what is the overall difference? From the point of view of performance, stability and ease of upgrade, which is more appropriate to use? I realise different people may have different opinions on this, but that's what I'm curious about - opinions. On the various websites, I could find quite a lot of info about how altboot works, and how cardFS works, but no reasons as to why you'd use one over the other.

Another (slightly) related question. I'm, thinking of repartitioning my SD card to give me some FAT space. Is this as simple as backing up everything on the card, repartitioning and formatting, and then copying everything back, or is there more to it?

Sorry if these are some noob questions, but I just got the Zaurus off e-bay 3 days ago. am loving it now - especially since I got Kopi/Kapi running with pi-sync to my desktop, and my wireless seems to work flawlessly (after installing the prism packages)... now just to get IrDA and bluetooth working with my phone.
Go to the top of the page
 
+Quote Post
CoreDump
post Jul 6 2006, 02:26 AM
Post #6





Group: Members
Posts: 715
Joined: 25-July 04
From: .de
Member No.: 4,094



QUOTE(spanky @ Jul 6 2006, 11:40 AM)
I was asking the same questions a couple of days ago, and because of problems with my SD card (1GB sandisk), the decision was made for me. If I ever tried to use AltBoot and boot off the SD, it would give errors with the SD card (don't have the exact text here now, but i think it was saying problems trying to mount it), and then just drop to the console. However there don't appear to be problems with the SD card, as I'm currently running using CardFS. I'm not sure whether the problems that were reported were with the card itself, or with the loop file, but I wasn't sure how to find out, and now that I'm running everything fine with cardFS, I'm not sure I want to try (at least not for a bit). I had a couple of altboot images on the card, and if I tried to use the SD card, it wouldn't even present me with the list of loop files to choose from, it would just give card errors. When I copied the files to a CF card it would present the list to choose from, but when I chose one I got the same errors.


Impossible to debug w/o exact error messages.

QUOTE
While I now have a better understanding of the difference between altboot and cardFS, I still have a couple of questions.

Are you saying that when altboot is used, the entire OS and packages etc are all run directly from the SD card, but when cardFS is used the OS is running from flash, but the packages are installed and run from the card?


Correct.

QUOTE
If this is the case, what is the overall difference? From the point of view of performance, stability and ease of upgrade, which is more appropriate to use? I realise different people may have different opinions on this, but that's what I'm curious about - opinions. On the various websites, I could find quite a lot of info about how altboot works, and how cardFS works, but no reasons as to why you'd use one over the other.


With cardfs your rootfs is still in flash. All programs installed on SD (by cardfs or manually via package manager) must be linked back to the rootfs with ipkg-link.

In short, ipkg-link is a bloody support nightmare, it's causing lots of wierd problems and is faaaaaar from beeing userfriendly.

On the other hand when you boot off SD or CF (and thereby having SD or CF as your rootfs) ipkg-link is no longer required. All new packages are installed into / directly, no messy linking needed.

The only problem with this method is that many SD cards produce error messages when formatted w/ ext2. Many won't work at all. That is a hardware problem with these cards and can not be worked around.



QUOTE
Another (slightly) related question. I'm, thinking of repartitioning my SD card to give me some FAT space. Is this as simple as backing up everything on the card, repartitioning and formatting, and then copying everything back, or is there more to it?


Nope, symlinks do not work with FAT so cardfs doesn't work either.

QUOTE
Sorry if these are some noob questions, but I just got the Zaurus off e-bay 3 days ago. am loving it now - especially since I got Kopi/Kapi running with pi-sync to my desktop, and my wireless seems to work flawlessly (after installing the prism packages)... now just to get IrDA and bluetooth working with my phone.
*
Go to the top of the page
 
+Quote Post
spanky
post Jul 6 2006, 03:14 AM
Post #7





Group: Members
Posts: 10
Joined: 5-July 06
Member No.: 10,325



QUOTE(CoreDump @ Jul 6 2006, 11:26 AM)
QUOTE
Another (slightly) related question. I'm, thinking of repartitioning my SD card to give me some FAT space. Is this as simple as backing up everything on the card, repartitioning and formatting, and then copying everything back, or is there more to it?


Nope, symlinks do not work with FAT so cardfs doesn't work either.



Sorry, I didn't make myself clear - i'd hope to partition the card into one (or more) ext2 partition, and a bit of FAT space, and tehn copy the cardfs stuff back to an ext2 partition. Would that work? Thanks for your reply. I'll have a closer look at the altboot errors and post back.
Go to the top of the page
 
+Quote Post
Ferret-Simpson
post Jul 6 2006, 04:10 AM
Post #8





Group: Members
Posts: 573
Joined: 8-June 05
Member No.: 7,295



You know, I STILL don't remember this conversation you keep claiming happened DB. . .

At least I bumped your thread for you! XP
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 24th October 2014 - 05:28 PM