Jump to content

unruh

Members
  • Content Count

    21
  • Joined

  • Last visited

Community Reputation

0 Neutral

About unruh

  • Rank
    New Here
  1. I would suggest that --root=/union be made the default for all cases. This is to try to idiotproof it since if that default is wrong in the case of an installed system, /union almost certainly will not exist and an error message will be gtenerated letting the preson know of the bad (in his case) default. On the web page, a line like Note that --root-/union must be used for creating a new liveCD from a live installation. As it is the only line where --root=/union is mentioned looks just like an example, rather than a crucial necessity, espeicially as most people have no idea what it means. Thanks
  2. And now trying that CD, I find that the links are there but they point for example bin-> /union/bin. Note that initial / on the union directory. Of course /union does not exist. It is /initrd/loopfs/union. I think that /usr/share/mklinecd./rc.sysinit should just assume that the base in /initrd/loopfs/union, and NOT /initrd/looprs, and get rid of those silly links. Ah, of course. You have set up the new union file system on /union, and have set up all of the usual / directories to point to /union. But that means when the squashfs file system is set up, it uses that same structure, and all of the links point to /union. This means thay they become defunct when the / filesystem is mounted on /initrd/loop. Ie, either those links have to be made so that they point to union in a relative manner, or the rc.sysinit has to be redesgned so that it refers to /initrd/loopfs/union. There is also the danger of a successively receeding set of directories as people make more and more children. Ie, this filesystem will now be mounted on /union, so you will have /union/union and so on with deeper and deeper sets of links. Anyway, that gives me a cheap out. I can just make all those links be relative instead of absolute, and at least my upgraded system should worll. All this was so I could test out some laptops to see if they would run linux. Yee gads, my stubborness gets me in trouble at times. And now I found that I should have used the --root=/union flag in mklivecd all along. Perhaps that should be made the default. Oh well. What a way to waste a day. thanks again for making this available. Despite the long learning curve, it is a very very useful piece of software.
  3. Just made a new image, and looking in livecd.sqfs, all of the directories are actually links inot union. Ie, there should be alink from /initrd/loopfs/lib to /initrd/loopfs/union/lib, but it sems that all of those links have disappeared. (Why was it set up that way?)
  4. OK, it just booted from the cdrom, but lets loook. Making extra nodes: OK Loading basid cdrom modules for Kernel 2.6 OK Starting USB support OK Probing USB devices OK Starting udevstart OK Searchinf for the loop image /dev/hdc DISK mounted OK Loading compressed loop module Loaded Mounting loop image on /initrd/loopfs OK --Exiting LINUXRC--------------- ---MKLIVECD RC.SYSINIT______________ /etc/rc.d/rc.sysinit:/etc/rc.d/rc.sysinit:548: /initrd/loopfs/bin/sed: not found /etc/rc.d/rc.sysinit:/etc/rc.d/rc.sysinit:548: /initrd/loopfs/bin/cat: no found setting up UNIONFS find:/initrd/loopfs/lib/modules/2.6.17-14mdv/kernel: no such file or directory BusyBox v1.1.2 (2006.12.14-05:46+0000) multi-call binary Useage: cp [ OPTION] .... SOURCE DEST insmod: can't read 'unionfs.ko': No such file of directory Failed to load unionfs module Loading /initrd/bin/ash Now, that sure looks like it cannot find union.fs Using ash I find that /initrd/loopfs has in it changes swap union Under union there are bin lib etc poweroff sbin var boot home opt root usr Ie, it seems that while it is looking in /initrd/loopfs/lib/.... the files are actually in /initrd/loopfs/union/lib...... When I installed the new kernel, I simply installed it using rpm. I have no idea where that "union" came from.
  5. PS: I made the new livecd with the command mklivecd --kernel=2.6.17-14mdv --tmp=/mnt/hda8/cd /dev/sda2/live14.iso after I had installed the new kernel and had installed the new madwifi modules and new alsa modules.
  6. OK, I am trying to set up a new kernel livecd. And it is a mess. I have set up a new kernel 2.6.17-14mdv with new alsa and madwifi. But the new live cd is failing because it cannot find unionfs. Now Mandriva 2.6.17-14mdv HAS unionfs (in /lib/modules/2.6.17-14mdv/kernel/fs/unionfs/unionfs.ko.gz) but apparently the script does not find it. Also since the unionfs is crucial to the operation of the livecd, as is squashfs, the script creating initrd should surely check to make sure that they are actually there. Making a livecd takes about an hour. and finding that at the end of thetime the created cd is totally uselss is frustrating. How do I make sure that unionfs and squashfs actually make it into initrd? And if from ash I try to insmod /initrd/loopfs/union/lib/moduels/2.6.17-14mdv/kernel/fs/unionfs/unionfs.ko.gz it tells me that it is an invalid module format (I assume it is because it is gzipped).
  7. Not clear what you mean by "not cleanly unmounted" The system itself is not on any disk. If you have other partitions from real disks mounted you could just unmount them all. and then just switch off the machine. There is nothing that can be harmed is there? Eg, on the default for i in /mnt/* do umount $i done should do it. Then just switch off.
  8. You do not need to install toronto. If you have the toronto iso on your system ( let me assume youcalled it Toronto.iso) you just need to do the following as root mkdir /mnt/toront mount Toronto.iso /mnt/toronto -o loop mkdir /mnt/toront-files mount /mnt/toronto/livecd.sqfs /mnt/toronto-files -o loop -t squashfs Now you will have the full set of files from the livecd under /mnt/toronto-files You will be able to copy the relevant files from the appropriate place under /mnt/toronto-files If you mount the CD onto /mnt/cdrom, then again you can loop mount the livecd.sqfs as above and get the files.
  9. But you do not know what you had then and furthermore, when you ask for help you give contradictory answers. That makes it very very hard to help you. Your /home directoy contains 2.5G of stuff. That is a HUGE home directly. What I would guess is that when you erased stuff, it ended up in your unemptied wastebacket in /home/midwavex/tmp. However to see what is going on we need to see what the size of the directories are in your home directory. du --max-depth=1 /home/mindwavex will tell you what the size is of each of the subdirectories. Find the big ones. Erase what should not be there. Get your home directory down to a few MB, not GB. Also what is the output of df?
  10. 2.6.17 is what Mandriva uses in 2007.1 They have no newer kernel. And apparently the 2.6.21 kernel used in cooker has changed too many things to be useable with MCNLine, as above. I am sure not going to go through a later kernel and fill in all of the approx 2000 almost incomprehensibel options. I have better things to do with 5 hours of my time. If you have some useful suggestions as to how I can make a kernel that the mac80211 module can be compiled on and that will work with MCNLive I would love to hear them.
  11. As a followup-- the reason I want the 2.6.21 or 22 kernels is because I vaguely remember reading that the iwl wireless drivers and the mac80211 subsystem required the new kernels. Do you know if that is true, or can they be compiled for the 2.6.17 kernel and work? Thanks
  12. Not sure what you mean. Do you mean that the ide drivers are now placed as modules, rather than compiled into the kernel, and that this causes problems? Also not sure why the more recent kernels would break other stuff. Has the kernel really changed that drastically with the 2.6.2x versions/
  13. Mandrake users rpm, which has some nice featers. for example, if the program that that icon is running is /usr/bin/donaldduck (right clock on the icon, select properties and application, and look for the file name it runs) then rpm -qf /usr/bin/donaldduck will tell youwhich package it was installed from. Then just do urpme dduck ( or whatever that package name was.) Now if it tells you that it needs to uninstall 20 other packages which depend on this one, you might want to think again about uninstalling it. No idea what you mean by orphaned. If you use rpm, and make sure that you uninstall using rpm or urpm, then you will not have orphaned files. You could remove all of kde and install some lightweight X windows manager instead.
  14. And because of that every manufacturer believes that they can tweak their system. They will change the drivers and include them in thier Windows which comes with the machine, and make it work. But it makes the linux driver writers lives hell. Uh, if there is a glimmer of hope, you need to know what you did to get that glimmer. The computer cannot remember unless the info is put into the appropriate file. In your case probably /etc/modprobe.conf IF the command iwlist s gives you output from some wireless access point, then your driver is working. It is not a wireless problem ( probably) It is a configuration problem Does the command ifconfig list eth1 as a device? Does iwconfig list eth1? If they do then as root run ifup eth1 Does it say it is asking for and address via dhcp?
  15. That is really huge. You need to figure out what part of that you really need. du --max-depth=1 /home/midwavex would help show where all that stuff is being stored. Note that you may have a bunch of junk in /home/mindwavex/tmp Also do du -s /*
×
×
  • Create New...