SliTaz Forum
You are not logged in.
I have slitaz 3.0 stable, and I have manually installed the system on a hard drive partition because my laptop doesn't have enough RAM to load the filesystem in memory. Everything has worked perfectly fine this way so far with slitaz residing on a hard drive partition, but now, when installing the package slitaz-loram-cdrom, I get the following error message:
Installing slitaz-loram-cdrom...
Removing all tmp files...
patching file /etc/init.d/rcS
patching file /etc/init.d/rcS
patch: hunk #1 FAILED at 76
patch: 1 out of 1 hunk FAILED
I checked, and the two files loram.extract and loram.rootfs were installed just fine
in directory /etc/tazlito, so the only failure was in patching file /etc/init.d/rcS.
So, before proceeding any further, I now need to manually patch file /etc/init.d/rcS ... Can someone
please let me know what to change in that file, so as to be able to do this ASAP? I have read the guide LiveCD_For_Low_RAM and the patch has the purpose of mounting /usr differently....but just could
not find anywhere exactly how to modify that file.
Can someone please help me out on this one?
TIA,
genko
Offline
Contrary to popular belief, posting multiple times about the same problem will not get you help any faster.
Why when you have SliTaz installed on the HDD are you trying to install a package that has on function but to help you make a LiveCD version of loram-cdrom? It serves no purpose other than that.
Also why don't you just download the iso copy of loram-cdrom from http://mirror.slitaz.org/iso/stable/flavors/ ?
Offline
Hi Trixar-za, thank you for your reply.
To answer your questions:
> Contrary to popular belief, posting multiple times about the same problem will not get you help any > faster.
I realized my inquiry has more to do with installation than anything else and after viewing this subforum (I am very new to this site, I just joined a few days ago) I thought this would be the proper place for it. Would you kindly remove my thread from the package forum? I have tried to do that myself but I do not have permission to do that. Thank you.
> Why when you have SliTaz installed on the HDD are you trying to install a package that has on . . > function but to help you make a LiveCD version of loram-cdrom? It serves no purpose other than >that.
This is why: I have downloaded slitaz stable, but when I tried booting it from my laptop I couldn't (my laptop has 96 MB of RAM). Then I read both the Handbook and the Guides and realized that it could be done with the loram-cdrom flavor. So this is what I did: after converting the rootfs.gz filesystem to a hard drive install (so that it could be booted with my low-ram system) I was successful booting slitaz 3.0 on my laptop. Then I added a few packages I needed (iptables, midnight commander, retawq, etc.) and now that my system is configured exactly the way I want it, I would like to do the conversion of it to loram-cdrom.....because I prefer booting from a live cd or frugal install, rather than from a hard drive partition......slitaz works much better that way.
Again, the only reason I installed to hard drive in the first place was to customize the system first for my needs and then convert to loram-cdrom (with compressed, non-writable /usr directory). So, as you can see, I am using it for the purpose it was intended.
> Also why don't you just download the iso copy of loram-cdrom from http://mirror.slitaz.org/iso/stable/flavors/ ?
I didn't know that was available....and now I have a fully customized system the way I needed it that just waits to be converted to loram-cdrom.....and the slitaz-loram-cdrom package was made exactly to do this.
My only question to you is this: why don't you try and help resolve this problem with the slitaz-loram-cdrom package? After all, it was made for this purpose, and it is made available as a slitaz stable package, and I am trying to make it work. Obviously, there is some error with the script trying to patch /etc/init.d/rcS ... and with my asking and bringing this issue up I think I am also helping the project. Instead of antagonizing a genuine request for support that in the end will help correct a bug and make slitaz stable better, as a moderator, why don't you try to help me come up with an answer?
Thank you,
genko
Offline
"...a hard drive partition......slitaz works much better that way."
Are you really sure about that? I have the experience that a hard-drive installation is quicker, and boots quicker. Other opinions around here?
Most likely (I suppose, I do not know) this mistake occurs in case your cdrom-drive is not recognized. This happened to me here.
So please have a look whether in the very moment when the error message occurs you have something in
/home/slitaz/distro/rootcd/boot
- there should be your rootfs.gz. Then check out how big it is. Most likely it is much bigger than the 30 MB original rootfs.gz, from where you started.
Copy the whole content of your orignal cdrom to a directory, say ,,slitaz-loram" and finally substitute the rootfs.gz there with your new one. Then use isomaster to make your own iso from it, burn it to CD.
But again: my experience is opposite, look at the beginning of my post.
Offline
Well, it is indeed quicker but not necessarily better....
You see, booting slitaz on hard drive does not make use of the init script,
and therefore there is no proper mapping, and so forth; udev doesn't come into
play properly at bootup.....
I also like the idea of having a fresh system every time I boot it. For my
needs (and laptop's needs), booting the loram-cdrom way would be best and this
is why I am trying to get it to work. Speed will be alright, as I am using
the squashfs option to compress /usr directory.
I don't think it has to do with the cdrom not being recognized....the whole
filesystem being at the moment on a hard drive partition..... it looks like
the script fails to find what it is looking for at line 76 of /etc/init.d/rcS,
therefore I was trying to understand what needs to be changed in that file
in order to do it myself by hand. But I might very well be wrong about this.
Just to make sure, I'll add the files you suggested in the directory you
suggested to see if that's the case. Right now I do not have a /home/slitaz/distro/rootcd/boot
directory and neither a custom rootfs.gz, but only the rootfs.gz filesystem unpacked to hard drive....and everything has worked perfectly this way so far, except for this instance.
Thanks for your input...I'll try adding the original rootfs.gz to /home/slitaz/distro/rootcd/boot
and even mounting the original cdrom image to /media/cdrom where perhaps slitaz expects to
find it.... I'll report back later on after doing just that....
Offline
@genko
slitaz-loram-cdrom-1.5.tazpkg installs/patch's cleanly here.
The output and a diff between rcS.original and post install patched is here:
http://pastebin.com/MfqB6AAp
Offline
This is what I have just done a few moments ago:
After booting the original slitaz-3.0.iso (stable) downloaded from this site on a high-memory,
fast-CPU PC via cdrom disk, I have tried installing slitaz-loram-cdrom-1.5.tazpkg (freshly downloaded from this site) and I get exactly the same error message as on my laptop with low
ram and slitaz installed on a hard drive partition:
Installation of : slitaz-loram-cdrom-1.5
--------------------------------------------------------------------
Copying slitaz-loram-cdrom-1.5...
Extracting slitaz-loram-cdrom-1.5... 16 blocks
Extracting the pseudo fs... (lzma) 12 blocks
Installing slitaz-loram-cdrom...
Removing all tmp files...
patching file /etc/init.d/rcS
patching file /etc/init.d/rcS
patch: hunk #1 FAILED at 76
patch: 1 out of 1 hunk FAILED
----
'tazlito gen-distro' will create a loram-cdrom flavor
while this package is installed
----
You will build a live CD with /usr mounted read-only.
You can install aufs or funionsfs to have read-write access into /usr with:
# tazpkg get-install aufs
or
# tazpkg get-install funionfs
----------------------------------------------------------------------
slitaz-loram-cdrom (1.5) is installed.
Do you mean to say I should ignore the error lines:
patch: hunk #1 FAILED at 76
patch: 1 out of 1 hunk FAILED
??
Am I missing something here?
Offline
Just use the pre-generated slitaz-loram-cdrom.iso
And just as luck would have it... mirror.slitaz.org is down. So use this link instead:
http://download.tuxfamily.org/slitaz/iso/3.0/flavors/slitaz-3.0-loram-cdrom.iso
Offline
@mojo
I have compared the file http://pastebin.com/MfqB6AAp you linked to to mine (the one with error: "patch: hunk #1 FAILED at 76") and the only code I am missing is this (at the very beginning of the file you have linked to):
+# Build ramdisk if root=/dev/cdrom (from slitaz-loram-cdrom package)
#
+ if [ -L /root ]; then
#
+ mount -t tmpfs ramdisk /tmp
#
+ mkdir -p /tmp/log/lighttpd /tmp/run /tmp/lock
#
+ chown www.www /tmp/log/lighttpd
#
+ fi
Any idea why this is so? Should I go ahead and add this code by hand or leave it as is?
@Trixar_za
Thanks, but I'd rather keep the work I've done so far customizing my slitaz and make this work.
We're almost there, just a matter of knowing if I should go ahead and add the lines of the missing code or not..... It would be very interesting to know why the patch from slitaz-loram-cdrom.tazpkg worked almost all the way except for those few initial lines... Linux can be a great learning experience for those with an inquisitive mind and willing to learn every day something new.
Offline
Just got a message from Pascal...God bless his soul.
There was indeed something wrong with the patch and the patch has now been fixed:
http://hg.slitaz.org/wok-stable/rev/0bab2a6c54c2
It was simply a matter of adding those six missing lines to the script.
Thank you all.
genko
Offline
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.56 MiB (Peak: 1.77 MiB) ]