Jump to content

chris:b

Members
  • Posts

    862
  • Joined

  • Last visited

Everything posted by chris:b

  1. No, it is not possible. A normal installation is made for one specific hardware. Only a live system with dynamic hardware detection is _portable_. You can install MCNLive on an external USB drive.
  2. Yes. On a 'live usb' system, you need to type: livecd persist (there is no graphical menu to navigate) You are always able to start without this cheatcode, and without persistent changes, of course. If you want to make it the _default_ boot, you can edit the file: syslinux.cfg on the usb stick, and add:persist to the append line. Or create a new label.
  3. Welcome, when you open a webbrowser on the live system, click on howto and scroll down. You'll find a step-by-step. * First step: create a persistent disk image (it is not a directory, not a partition, it is just a big file), with the included wizard (in the MCNLive menu) * Reboot with the bootcode: livecd persist - or, on Toronto: choose in the start menu the 'persist" option The next time you boot - with persist - you'll see all changes you made.
  4. Has anyone an AOpen mini or a Mac mini, they are not fanless, what about the noise on those? They both can run Linux...
  5. LOL to the "log in as root" stuff. When I say this, I usually put a smiley to it. I believe that linux users should have the freedom to .... In this case, using the mklivecd command -- it is easier for me to find out what is going wrong, when you don't login 'graphically' as root :P Keep us posted, please.
  6. Congrats. Yes, when you make the basic installation, you better do a custom partitioning, with only one / - I thought that I had this tip in the howto. For the custom scripts. All the files you find on Toronto, in the dir: /usr/local/bin ---> you would copy all these files to the same dir /usr/local/bin on your HD installed system. (and you need to install some rpm's to be able to use these scriptys. It is written in the howto) And you need the draklive-install -- also in the howto. :D The menu entries - you need to create manually. btw: I am a pretty normal person, and an average MDV user. If you ever come to Europe and Amsterdam, it would be a pleasure to meet you - you would notice how normal I am. :P (except maybe that I speak 4 languages, but in Europe this is also quite normal).
  7. You are still using the broken/wrong mklivecd scripts, proove: You did not follow these steps, ALL steps: https://mandrivausers.org/index.php?showtopic=42429 In particular these: * Replace all mklivecd scripts, just copy those from Toronto over to your installed system: /usr/sbin/mklivecd /usr/sbin/hwdetect /usr/share/mklivecd/* Ask please if you don't understand what that means, or how to do this. Also: * Don't work graphically logged in as root. Never! Repeat it with me: don't work ... * Clean up the /tmp stuff, clean old iso's * Before you start, run a: df command * Make sure to have enough room, and enough RAM * close all running apps, only a terminal open. * the command to build a livecd is: su mklivecd --verbose nameofthe.iso
  8. SoulSe: time to try MCNLive :D The feature is: you can make in no time your own 'Linux OS' just the way _you_ like it. No matter if you are experienced or not. A pre-installed Gentoo is not bad, I guess. But if you look at the zonbu website, you need to be a very experienced developer to even add a single application. The zonbu is an almost closed system - for an average or even an experienced user. I also got the impression it is not made to easily replace its own pre-installed Linux. I personally would always prefer an open, easy to customize system and open hardware without a suscription.
  9. solarian, try MCNLive, it is MDV 2007.1 Spring without any questions, it will boot right to the desktop. Download MCNLive Toronto ftp://ftp.nluug.nl/pub/os/Linux/distr/man...cnlive/Toronto/ What is it: www.mcnlive.org/index.html. And our forum is here :P https://mandrivausers.org/index.php?showforum=52
  10. Yeah, we could make two versions. Or better: someone could create a version with the closed source nvidia and ati drivers. There are some reasons why I don't do it, though I am aware that this is a showstopper for people who want the 3D desktop with nvidia cards out of the box. * Though I am not against closed stuff in user space/ on user level, for me personally it just does not feel ok to include propr. stuff when it comes to the kernel. * Mandriva One includes these propr. drivers. Result: on a lot of systems people get what they call: a black screen :P On a live system with automatic hardware detection, the xorg drivers are superior. MCNLive in this regard does a better job than One. Living without the 3D desktop is a price some people pay, but at least they get a good working GUI! * Releasing two versions, for me personally, is too time consuming. I am glad when we can get one version working B)
  11. You could install it with 158MB RAM? Wow, I did not know this is possible. You had the swap before you started the install, right? You won't have much luck with the ATI Rage and 3D desktop, I am afraid :P Ok, now make your system faster. Disable all this junk in the KDE taskbar, on the right, in particular the net monitor. First tell him not to start at all, then stop it. This will save you 20 MB RAM. Stop the flag=keyboard layout. If you have enough room on your /, then install the kernel-legacy-2.6.17.13mdv rpm. Reboot into the _new_ kernel, if it works un-install the other one. This will speed up your system :-)
  12. You are using a broken mklivecd version. Please check out these steps carefully: https://mandrivausers.org/index.php?showtopic=42429 And before you start again, clean out the old /tmp stuff - the mklivecd-xxxx directories. And - keep asking. It is not easy to start from scratch. :D
  13. Hi cgherman, and welcome on MUB! The downloaded iso file, as it is! Choose the option 'Burn image' (or whatever it is called in your burning software), point it to this .iso file. The rest is done by your burning program. *After* you burned the iso, you will find files and directories on the burned CD.
  14. I like the anti spam question :D Thx mystified!
  15. Jerome, both systems I linked to, are short in internal memory, for my taste. The norhtec with 128 MB won't be able to run a KDE or Gnome desktop. The linutop with 256 MB will, but too slow. Oh, and you don't need the CF card. They have usb ports :-) A VIA C7 in a mini-ITX chassis looks more promising, but I am not an expert: http://www.jetway-mini-itx.com/jesykiwj7mii2.html And when Adam says MDV is running on a C7 you can be sure :-)
  16. I too am fascinated by these tiny systems :-) http://www.norhtec.com/products/mcjr/mcjr03-lrg.JPG http://www.norhtec.com/products/mcjr/index...ghardware.co.uk Never tried one. They are beyond my budget. Mandriva bought linutop if I am not mistaken: http://blino.org/blog/mandriva/linutop.html If MCNLive would run on these systems depends a bit on how they work. If they work with internal Flash Cards that are seen as /dev/sda devices then it could work out-of-the box. If their flash memory is connected to an internal ide-to-scsi/usb controller, then a small change in the code can make it work. Starting them by booting via an external usb drive/stick works if they have enough RAM (which is not the case with some of these boxes). Some of these boxes need a special/different kernel than MCNLive and some adjustments for a good performance.
  17. Hi Jose, What you see is the background image of the login manager KDM. You can change the image. ALT & F2 : kdesu kwrite Open the file: /usr/share/mdk/dm/mdk-kde.xml change line 5 to: <normal file="/usr/share/mdk/backgrounds/default.png"/> And, depending on the MCNLive version you use, you need to take a look at this file: /etc/kde/kdm/backgrundrc
  18. MCNLive -whatever version- don't include proprietary video drivers by default . But you can install the drivers, running live or after installation. MCC : enable the non-free sources - they are already pre-configured, but disabled. Install the matching nvidia driver. Run 'Configure Video". Restart the xserver.
  19. Thank you vinny :-) MCNLive is designed this way - that you can use it in live mode with all the bells and whistles and features of an installed system. When I have implemented the copy2ram feature we've made a lot of tests - mainly we tried to break the system, but we did not succeed :D But noone tried it two days long! I must say that your system, the Dell notebook with the Intel graphics chip, is an almost perfect box for MCNLive. I have a similiar laptop (a Lenovo with similiar specs, but a Intel wireless chips that works out of the box without ndiswrapper), and all MCNLive versions are being tested first on it. Your question regarding installing to HD. You sure can do it, and it should not be any different, but it will be a little bit slower than with copy2ram, because of the access time of an HD when you load a program. And if you want your laptop's setup untouched, there are several ways to deal with MCNLIve. The first is: running it from an usb stick. Will cost you 10 $ for a 1 GB stick. And load it from the stick with copy2ram. And save the changes on the same stick, all settings and added programs and so on. The second: get some more internal memory, another 512MB. Install the VirtualBox software on your Windows system, and install MCNLive inside a VirtualBox image. It will run at almost native speed. And will behave as any installed system. But without the 3D effects. The third: get an external usb hard disk, a cheap 2.5 one will do. And install it there. In live mode!! On a first partition (FAT32). And the changes also on this disk. The base system only occupies 366 MB, the changes only a few GB. You can use it with or without the copy2ram feature. And the rest of your external disk (> 100 GB) is free for your music and videos and documents.
  20. I don't think that it is bad. :-) It works the same way as if you would use the internal memory on a normal system. The only difference is in the beginning when you start the system with copy2ram, that the _compressed_ big livecd.sqfs (360 MB) is copied once from the CD or the USB stick into RAM, so this part of the memory is occupied. When you start a program, it is loaded _from_ RAM instead from the CD or the usb stick (or from HD when you are running a normal installation.) That makes it lightning fast. The (uncompressed) program is loaded into the free part of the memory, and will stay there. If you load many programs, the memory is freed up dynamically, and/or the swap is used.
  21. For me it means that everything is ok with your /tmp directory. And I am running out of ideas :-( It would be nice though to find out what goes wrong. I bet that you are not the only one. And if we could find out, maybe I can find a way to prevent this from happen or enhance mklivecd to give an error message with some content. I can remember that one of our team member once had this problem, turned out: it was a space issue. But in your case? Looks like we have to wait until the next one with the same issue shows up. Luckily you can specify your personal built directory.
  22. The KDE4 alpha version is on the Mandriva 2007.1 official /contrib mirror. Not in main. A user who has contrib enabled is seeing all these alpha packages. Personally I find it confusing. But I would not want to live without packages from contrib :-) If we get a buggy KDE4 beta (not as default, but as a choice) for 2008 on a standard urpmi source like contrib, I really hope that the packagers make it clear in the title of the package _and_ in the description what it is. I don't understand what Willie means with MCNL, mandrivaclub.nl ? There are no KDE4 packages in the specific MCNL repos.
  23. Are you looking for the command used, I am not sure? Open the home folder is: konqueror /home/username Open the filemanager with the default setting is: konqueror --profile filemanagement You can create personal profiles within konqueror, save them and start konqueror with these profiles. More in a terminal: konqueror --help and: konqueror --profiles
  24. The weird thing is that it seems that the livecd.sqfs compressed image is being created, but Creating compressed image: [100.00% 00:05:25/00:05:29] 5:29 minutes to create a 1,1 GB image? Seems a bit fast to me. Got the impression that it stops after 5 minutes and does not store/save the image. The chmod error is: there is no livecd.sqfs file. And because this happens only if your are using the default /tmp dir, there is something wrong or special with your /tmp dir. Q: is your system installed on one / partition, or do you use some extra partitions? Could you provide the result of: Should like like this:
  25. You final iso is 1,7 GB big? Then your installed system occupies more than 5 GB ( the result of 'df' is ??) For the build process you need a lot of free space, I am not sure how much. At least 2 times the size of the final iso. I never saw this error. Does it say more than that? At which stage of the build process? Would be interesting to find out what is going wrong ... Maybe the /tmp dir has a quota -- I am not sure. PS: just saw that you edited the sub title of this topic. lol, d: - I don't think that you are a clumsy linux user. You are having fun with experimenting and discover all the nice things you can do on a linux system. Building complete live systems is one of the features you can't do with any MS Windows OS (you can build a sort of Live CD, but it has nothing useful included, and the features are VERY limited, and you are not allowed to use it on any computer other than where you built it)
×
×
  • Create New...