ArchCK - Current status and initrd/initramfs progress.

iphitus · 2005-12-24 07:18:23

Hey,

The ArchCK front has been quiet for the last month or two, I have taken over the packaging, and have been a bit slower with my releases due to exams and holidays.

I have been maintaining ArchCK, just not releasing as I havn't had sufficient time to test it to my liking.

I have picked up the testing and over the last few days I have been converting ArchCK to the new initrd setup. Those who understand the situation, know that initrd was destined for replacement during the 2.5 series by initramfs, which unfortunately took a little longer to mature.

fbsplash is dependent on initramfs, which is why it doesnt work with the current initrd setup, hence ArchCK's delayed move to initrd.

Instead of moving to the older initrd, I have been working on implementing the initrd work in initramfs, how it should have been. I nearly have this working, so you might get a brand new ArchCK release for Christmas with initrd/initramfs and fbsplash.

iphitus

dtw · 2005-12-24 08:04:09

blimey...nice work, iph. I knew it was worthing passing overto you entirely!

AndyRTR · 2005-12-24 08:06:44

Thanks for all your work. Let´s see if we can port the archck kernel to arch64

iphitus · 2005-12-24 10:26:43

Just to let you know, it's progressing perfectly. I can now boot an initramfs enabled linux kernel using initramfs rather than initrd. Now I just have to add custom dsdt and fbsplash support

edit: fbsplash support added, custom dsdt support added. seem to be working perfectly, but need to compile a kernel to check.

Shofs · 2005-12-25 05:47:25

I would love to see FUSE in the next release too

shbang · 2005-12-25 11:17:55

make menuconfig

File systems ---> Filesystems in userspace support

iphitus · 2005-12-25 12:30:57

I know where it is

I've redone the whole config for this one, and its much improved. Fuse is included.

As for status, its working, there's one or two issues with fbsplash I would like to sort out first however.

shbang · 2005-12-26 14:35:49

Somehow I gnu you knew.

dtw · 2005-12-26 16:00:55

Iph, do my old initscripts still work the same?

paranoos · 2005-12-26 19:30:39

i'm curious, how are you making the initramfs images? are you using the mkinitrd tool? do you have to change the script to add support? or does initramfs read initrd images as well?

in short, how's it all work?

tomk · 2005-12-26 21:10:40

Sounds great - many thanks in advance.

For those of us who roll our own, roughly when can we expect the patchset on your own website?

iphitus · 2005-12-26 22:57:28

I'll upload the patchset today

tomk · 2005-12-26 23:04:46

Excellent. New Year, New Kernel - I like it.

Thanks.

iphitus · 2005-12-26 23:21:51

Ok, the new release is out, and the fbsplash issues are fixed thanks to dibble -- the solution was on the wiki!

dtw · 2005-12-26 23:56:29

Shofs · 2005-12-27 01:21:16

iphitus wrote:

I know where it is
I've redone the whole config for this one, and its much improved. Fuse is included.

Thanks!!!

You might consider including it in the "What;s in it?" list on your site. I think it is a major inclusion to the default config hence , appealing to many people.

Just a thought.

tomk · 2005-12-27 10:02:31

The "What's in it?" list is of the patches included in the patchset i.e. functionality not available in the vanilla kernel. fuse is now part of the vanilla kernel, so that wouldn't be the right place to put it. Right, iph?

It's probably worth mentioning when the package hits [community], though.

Shofs · 2005-12-28 01:44:46

tomk wrote:

The "What's in it?" list is of the patches included in the patchset i.e. functionality not available in the vanilla kernel. fuse is now part of the vanilla kernel, so that wouldn't be the right place to put it. Right, iph?
It's probably worth mentioning when the package hits [community], though.

I see what you mean. Now that it is 'enabled', and by that I mean enabled in the config, telling the community would be worth mentioning. Just a thought I had, afterall recently that would attract me to archck because i wanted a kernel that i didnt have to compile myslef to get the functionality. I think i am making this more confisung so ill stop here. eh.

iphitus · 2005-12-28 03:00:57

Well, the homepage of ArchCK is more for the individual patchset rather than the package, ArchCK is in no way tied down to Arch, despite the name, it's very popular on Gentoo, and other distros.

lilsirecho · 2005-12-29 04:24:07

How is initramfs installed in Lilo in place of initrd?

iphitus · 2005-12-29 06:24:56

Exactly the same way.

lilsirecho · 2005-12-29 14:46:46

Your reply means that the code is:

initrd=/boot/initrd.img.......( no reference to initramfs is included?).

iphitus · 2005-12-29 21:20:08

Yes. To use an initramfs image, you attatch it the same as you would an initrd image, initrd=/path/to/your/initramfs-image.

When I release it, the whole setup will be *entirely* identical to the user, except that they use mkinitramfs instead of mkinitrd. The configuration file is identical in syntax and everything.

lilsirecho · 2005-12-29 21:33:31

The coding for the initrd lilo:

initrd=/boot/initrd.img.... This is in the wiki.....

Your reference is as follows:

initrd=/path/to/your/initramfs-image.

I find the code you show has a dash (-image)

Am I to understand that the correct coding would be:

initrd=/boot/initramfs.img

Please correct me if I am wrong...thanks.

dtw · 2005-12-29 22:38:14

You can call the initrd flyingbananakungfumonkey.rat and put it anywhere you like (* as long as it is available at boot) as long as it it correctly ref'ed in the bootloader

Arch Linux

#1 2005-12-24 07:18:23

ArchCK - Current status and initrd/initramfs progress.

#2 2005-12-24 08:04:09

Re: ArchCK - Current status and initrd/initramfs progress.

#3 2005-12-24 08:06:44

Re: ArchCK - Current status and initrd/initramfs progress.

#4 2005-12-24 10:26:43

Re: ArchCK - Current status and initrd/initramfs progress.

#5 2005-12-25 05:47:25

Re: ArchCK - Current status and initrd/initramfs progress.

#6 2005-12-25 11:17:55

Re: ArchCK - Current status and initrd/initramfs progress.

#7 2005-12-25 12:30:57

Re: ArchCK - Current status and initrd/initramfs progress.

#8 2005-12-26 14:35:49

Re: ArchCK - Current status and initrd/initramfs progress.

#9 2005-12-26 16:00:55

Re: ArchCK - Current status and initrd/initramfs progress.

#10 2005-12-26 19:30:39

Re: ArchCK - Current status and initrd/initramfs progress.

#11 2005-12-26 21:10:40

Re: ArchCK - Current status and initrd/initramfs progress.

#12 2005-12-26 22:57:28

Re: ArchCK - Current status and initrd/initramfs progress.

#13 2005-12-26 23:04:46

Re: ArchCK - Current status and initrd/initramfs progress.

#14 2005-12-26 23:21:51

Re: ArchCK - Current status and initrd/initramfs progress.

#15 2005-12-26 23:56:29

Re: ArchCK - Current status and initrd/initramfs progress.

#16 2005-12-27 01:21:16

Re: ArchCK - Current status and initrd/initramfs progress.

#17 2005-12-27 10:02:31

Re: ArchCK - Current status and initrd/initramfs progress.

#18 2005-12-28 01:44:46

Re: ArchCK - Current status and initrd/initramfs progress.

#19 2005-12-28 03:00:57

Re: ArchCK - Current status and initrd/initramfs progress.

#20 2005-12-29 04:24:07

Re: ArchCK - Current status and initrd/initramfs progress.

#21 2005-12-29 06:24:56

Re: ArchCK - Current status and initrd/initramfs progress.

#22 2005-12-29 14:46:46

Re: ArchCK - Current status and initrd/initramfs progress.

#23 2005-12-29 21:20:08

Re: ArchCK - Current status and initrd/initramfs progress.

#24 2005-12-29 21:33:31

Re: ArchCK - Current status and initrd/initramfs progress.

#25 2005-12-29 22:38:14

Re: ArchCK - Current status and initrd/initramfs progress.

Board footer