And also, I need to be able to access the server.properties files (or whatever its called now) because i need to be able to control some specific configurations.
Are we able to delete any of the 3 worlds that we can create?
Over the past few days I've created my most recent project: build-your-own MineOS.
build-your-own MineOS is a entirely different project which does not attempt to replace MineOS/+. Instead, byo MineOS is an educational tool which aims to teach server admins about what components MineOS uses, walks you through how to properly add and configure each, and help you get a fully comprehensive understanding of how each mechanic makes for the best possible server.
If you ever felt like MineOS/+ needed a boatload more customization than microcore offers, and you're willing to learn how to get it set up, byo MineOS is for you!
byo MineOS holds to many ideals of the original MineOS in that it aims to be slim and functional. byo MineOS honors this by having only a 53 MB footprint and giving you the instructions and flexibility to add on any services you find necessary, from lighttpd, PHP, MySQL, and more--
Built from the CRUX Linux distro, byo MineOS will work on any hardware Linux has support for. So come take a look at byo MineOS:
I have spent the better part of today trying to work through your byo MineOS guide and I keep running in to a problem at the point where you restart the system and boot from the OS for the first time. Every time I try and boot from the hard drive I get a no bootable media found error. Not sure what the problem is.
I have spent the better part of today trying to work through your byo MineOS guide and I keep running in to a problem at the point where you restart the system and boot from the OS for the first time. Every time I try and boot from the hard drive I get a no bootable media found error. Not sure what the problem is.
Based on that error, assuming you had gone through all other steps tells me that you may have missed the fdisk step of 'creating a bootable flag' for that partition.
To put your back right where you left off, you can boot back from the ISO, type in 'CRUX'
fdisk /dev/sda
a
1
(and then check your work with p, and ensure the asterisk is there--or check first to see if its there before changes.)
w (to exit)
unmount cd and reboot.
The only other place is if you didn't run 'lilo' after copying bzImage and System.map from the kernel steps. Follow the steps on my troubleshooting page if thats the case.
Let me know if either of these are it!
Well I did find that the sda1 partition was not flagged as bootable, but setting that and rebuilding the kernel and moving it back to the boot partition and rerunning lilo, did not fix the error. I am wondering if there is something I need to do differently since I am trying to build this in side of a virtual box.
As it stands now the virtual system has the virtual HDD installed Primary Master IDE interface but I have also tried it on the SATA and SCSI interface with the same results. Not sure what the problem is, it just looks like it's not seeing a bootable device with a valid image.
Well I did find that the sda1 partition was not flagged as bootable, but setting that and rebuilding the kernel and moving it back to the boot partition and rerunning lilo, did not fix the error. I am wondering if there is something I need to do differently since I am trying to build this in side of a virtual box.
As it stands now the virtual system has the virtual HDD installed Primary Master IDE interface but I have also tried it on the SATA and SCSI interface with the same results. Not sure what the problem is, it just looks like it's not seeing a bootable device with a valid image.
I would recommend using only the SATA interface--which is the default Virtualbox HDD interface; I can't really see any benefit to IDE here, and it also requires much changes to the instructions provided. Whereas the instructions show /dev/sda and /dev/sda1--yours would be /dev/hda and /dev/hda1. This would need to be reflected in /etc/lilo.conf before running it.
Finally, if you have used the two solutions in the troubleshooting page, it could simply mean LILO was never successfully installed (perhaps from the above explanation). When you run LILO, what output do you get? Simply put, if it doesnt look similar to this, then LILO was never installed due to an incorrect lilo.conf setup.
Oh, and I guess another way might be if you do not have virtualbox set to boot off the HD. In Virtualbox settings, look at your VM settings, System Tab: "Boot order"--ensure "hard disk" is checked.
Curious if anyone knows why this is happening. I followed the guide on the mineos page, but when I go ahead and shut down the mineos linux system and go to restart it later...there is no more world one when I go to start it on the admin web page.
I can, however, restore it and then it is found.
So right now I've been saving and restoring each time :l
By definition, a RAMDISK, just like any ram is lost upon restart. Ramdisks are optional, and you elected to use it during the install, but it is not necessary if the restore is inconvenient.
On a side note, MineOS CRUX addresses all the inconveniences of my now-undeveloped MineOS (microcore), by taking care of all theses steps for you.
I highly suggest you have a look, as it has countless advantages over my previous (microcore) model, including crontabs manageable from the new web-ui, as well as RAMDISK use with automated restores so even after a reboot, your server will automatically come back up.
Does the cromtab show up in game (Saving world, save complete) when the scheduled time hits, or does it save it all on the back end.
The ingame spam has nothing to do with crontabs or MineOS, but rather Minecraft. Anytime any method wants to backup a Minecraft world, it SHOULD ABSOLUTELY tell Minecraft to commit all chunks to disk, otherwise the backup is ...ineffective. Anytime a backup/archive occurs in MineOS, it does these actions--and as an OP (and only an OP) will you be exposed to the 'saving world to disk...save complete' "spam".
This is unavoidable spam as an admin, and would occur on any distro.
When i click start server in the webUI it says the server was started. When i reload the server is down. Is this because of 1.8 (i can't really see any reason 1.8 should be a blockade for MineOS)
Also could you please make support for running on bare Mac machines? By that I mean make it compatible with EFI boot :smile.gif: (right now it won't show up after installation)
The ingame spam has nothing to do with crontabs or MineOS, but rather Minecraft. Anytime any method wants to backup a Minecraft world, it SHOULD ABSOLUTELY tell Minecraft to commit all chunks to disk, otherwise the backup is ...ineffective. Anytime a backup/archive occurs in MineOS, it does these actions--and as an OP (and only an OP) will you be exposed to the 'saving world to disk...save complete' "spam".
This is unavoidable spam as an admin, and would occur on any distro.
This could be removed by changing some lines of code. I might do so :tongue.gif:
When i click start server in the webUI it says the server was started. When i reload the server is down. Is this because of 1.8 (i can't really see any reason 1.8 should be a blockade for MineOS)
Also could you please make support for running on bare Mac machines? By that I mean make it compatible with EFI boot :smile.gif: (right now it won't show up after installation)
I don't develop the Microcore-based MineOS anymore, now that MineOS CRUX is my main project. I have no plans for *this* distro to have any updates, so EFI boot is not an option. If desired, I can look into this for CRUX.
This could be removed by changing some lines of code. I might do so :tongue.gif:
Such changes are not MineOS-based, so unless the code you're changing is at the java-level/minecraft, I don't see how an OS can suppress notifications that the server itself generates when running 'save-all'.
Hexparrot: Thanks for your answer. I did mean the CRUX version :smile.gif: I did also find the bug, MineOS CRUX cannot handle spaces in the server name.
Also please try to look at the EFI boot for CRUX.
When i said "I might do so" I meant i would maybe make a modification to the needed class files and publish it. Also I would in that case be really happy if you masde it an option for MineOS, but that was not what i tried to say :tongue.gif:.
Then there was my attempt to give you two suggestion:
1. Support for www.luaserver.org and support for jar file mods like modloadermp and those (that would require a unzip zip thingy and file moving) :smile.gif:
Summary report on recent experiences with MineCRUX.
History:
I gave up on MineCraft serving after a plethora of updates made it exhausting trying to keep up, especially as I used bukkit.
The new MineCRUX settings that allow me to choose updates with a higher resolution sold me on trying again.
First of all, it is simple to install on bare-metal (without other OS).
The new CRUX package management system is smooth and with Will's scripts, the addons were idiot-proof.
However, as a home-user running a four person LAN server for my family, I didn't want to lose other OSes from the server computer. So I pursued a triple-boot option looking to end with Grub2 as the boot-manager rather than the less user-friendly and older LILO.
Three semi-negative notes:
1) The Web-UI always listed one person connected to any started server even without players logged on. I assume this was the Web-UI?
2) The console's log output for a server showed illegible characters for the "unknown" user ID. It'd be much better if it identified the Web-UI as that connection.
3) The Web-UI's connection took one of the server-property's permitted connections. Server managers should account for this when limiting the number of connection for a server.
Critical recommendation for success:
Before beginning install, use a more user-friendly partition manager, like GParted within Ubuntu or even a bootable rescue-type iso like Rescatux.
Resize and partition your target drive to provide space for MineCRUX as primary ReiserFS and primary linux swap.
Then do the MineCRUX install skipping the partition manager step and the "Make sda1 into ReiserFS" step.
Hardware:
Laptop x86 dual-core 1.5 GHz chips
Two 150 GB hard drives
2 GB RAM
Other OSes:
Vista & desktop Ubuntu
Challenges:
Compared to triple-boot install of the previous version of MineOS, the new partition manager is less easy to understand. It provides a plethora of file-system choices that don't match what MineCRUX wants and wouldn't let me make the choices I needed.
Running as RAM-disk did not work with very large world files like the Skylands v1.3 I wanted...I kept getting errors when transferring files to the server world, possibly due to out of space errors (over 200 MB attempted to copy). I had to reinstall MineCRUX to remove RAM option, not knowing how to change the filesystem without reinstall.
BIG BIG WARNING for MultiOS systems: Be extremely careful of the next step after running the partition manager where the install script asks it should make sda1 into ReiserFS. I hit OK before realizing sda1 is where my original WinXP OS was, toasting everything on it.
I had to reinstall the Win OS, using Vista this time...not so bad after I've been using Win7 elsewhere.
MineCRUX didn't play well with other partitions, possibly because of the partition manager's capabilities.
I solved the problem by partitioning and formatting the target drive before installing MineCRUX and not using MineCRUX's partition manager at all.
My installation steps:
1) Install any Windows OSes or begin with one. They don't play well with anyone else and apparently, with my skill level, need to be in the first partition. For me, a WinOS was on the first drive, sda.
2) Use GParted or other user-friendly linux-based partition manager to prepare the target drive and partition for MineCRUX (primary ReiserFS, primary linux swap) and your usual Linux OS (primary EXT4...later made logical by Ubuntu install). Be sure to note the ID for the MineCRUX partition. These all went into the second drive, sdb.
3) Install MineCRUX, making sure of the target partitions (for me sdb1 and sdb2). Skip the partition manager and the "Make sda1 ReiserFS" step.
4) Install Ubuntu using choice of "installing alongside other Linux OS". It will install Grub2 which should ID Windows and MineOS as boot options.
5) Re-boot, selecting MineCRUX to be sure Grub2 works it properly.
6) Boot into Ubuntu and modify the Grub2 options to list MineOS as default choice (this was easier than I thought it would be after letting the Ubuntu install do the hard work of identifying the correct boot parameters).
7) Re-boot without selecting an OS to make sure MineCRUX boots as default.
8) Make sure the MineCRUX is connected to the internet, update the MineOS scripts and "ports" (the CRUX package management system), and continue through the MineCRUX post-installation steps.
In the end, I have a triple-boot MineCRUX, Vista, and Ubuntu machine.
On a delightful note, the voice-chat addon, umurmur, works nicely.
I am slightly concerned about how the MineCRUX scripts operate in that they reach out to other websites to download and install software to the server. If the target website gets hacked, what bad might happen and how likely is it such a thing could occur?
It'd be nice to see the MineCRUX install script:
1) Play nicer with other OSes
2) Automatically ID the correct target partition to make into ReiserFS instead of sda1, or provide better guidance.
3) Use something like Ubuntu's Grub2 "other operating system ID" capabilities for the boot loader.
If I install the pigmap add-on, how would I replace the C10t output with the pigmap output?
On a similar note, but beyond the scope of MineCRUX, it'd be even nicer if I could replace the mapping with the output of the bukkit plugin DynMap.
It'd be really sweet if a script were available to install a web-UI for managing the murmur voice-chat server for user authorizations, maximum bytes/sec, etc. There are linux packages out there, but I am not adept enough to install them.
BTW: If you want to run multiple worlds, I recommend using the bukkit plugin "Multiverse". Then you only need to run one server, sending users to particular worlds using permissions while letting them move between them if you so choose. You can have Multiverse unload worlds that are not used to conserve server resources.
Summary report on recent experiences with MineCRUX.
History:
I gave up on MineCraft serving after a plethora of updates made it exhausting trying to keep up, especially as I used bukkit.
The new MineCRUX settings that allow me to choose updates with a higher resolution sold me on trying again.
First of all, it is simple to install on bare-metal (without other OS).
The new CRUX package management system is smooth and with Will's scripts, the addons were idiot-proof.
However, as a home-user running a four person LAN server for my family, I didn't want to lose other OSes from the server computer. So I pursued a triple-boot option looking to end with Grub2 as the boot-manager rather than the less user-friendly and older LILO.
Three semi-negative notes:
1) The Web-UI always listed one person connected to any started server even without players logged on. I assume this was the Web-UI?
2) The console's log output for a server showed illegible characters for the "unknown" user ID. It'd be much better if it identified the Web-UI as that connection.
3) The Web-UI's connection took one of the server-property's permitted connections. Server managers should account for this when limiting the number of connection for a server.
Critical recommendation for success:
Before beginning install, use a more user-friendly partition manager, like GParted within Ubuntu or even a bootable rescue-type iso like Rescatux.
Resize and partition your target drive to provide space for MineCRUX as primary ReiserFS and primary linux swap.
Then do the MineCRUX install skipping the partition manager step and the "Make sda1 into ReiserFS" step.
Hardware:
Laptop x86 dual-core 1.5 GHz chips
Two 150 GB hard drives
2 GB RAM
Other OSes:
Vista & desktop Ubuntu
Challenges:
Compared to triple-boot install of the previous version of MineOS, the new partition manager is less easy to understand. It provides a plethora of file-system choices that don't match what MineCRUX wants and wouldn't let me make the choices I needed.
Running as RAM-disk did not work with very large world files like the Skylands v1.3 I wanted...I kept getting errors when transferring files to the server world, possibly due to out of space errors (over 200 MB attempted to copy). I had to reinstall MineCRUX to remove RAM option, not knowing how to change the filesystem without reinstall.
BIG BIG WARNING for MultiOS systems: Be extremely careful of the next step after running the partition manager where the install script asks it should make sda1 into ReiserFS. I hit OK before realizing sda1 is where my original WinXP OS was, toasting everything on it.
I had to reinstall the Win OS, using Vista this time...not so bad after I've been using Win7 elsewhere.
MineCRUX didn't play well with other partitions, possibly because of the partition manager's capabilities.
I solved the problem by partitioning and formatting the target drive before installing MineCRUX and not using MineCRUX's partition manager at all.
My installation steps:
1) Install any Windows OSes or begin with one. They don't play well with anyone else and apparently, with my skill level, need to be in the first partition. For me, a WinOS was on the first drive, sda.
2) Use GParted or other user-friendly linux-based partition manager to prepare the target drive and partition for MineCRUX (primary ReiserFS, primary linux swap) and your usual Linux OS (primary EXT4...later made logical by Ubuntu install). Be sure to note the ID for the MineCRUX partition. These all went into the second drive, sdb.
3) Install MineCRUX, making sure of the target partitions (for me sdb1 and sdb2). Skip the partition manager and the "Make sda1 ReiserFS" step.
4) Install Ubuntu using choice of "installing alongside other Linux OS". It will install Grub2 which should ID Windows and MineOS as boot options.
5) Re-boot, selecting MineCRUX to be sure Grub2 works it properly.
6) Boot into Ubuntu and modify the Grub2 options to list MineOS as default choice (this was easier than I thought it would be after letting the Ubuntu install do the hard work of identifying the correct boot parameters).
7) Re-boot without selecting an OS to make sure MineCRUX boots as default.
8) Make sure the MineCRUX is connected to the internet, update the MineOS scripts and "ports" (the CRUX package management system), and continue through the MineCRUX post-installation steps.
In the end, I have a triple-boot MineCRUX, Vista, and Ubuntu machine.
On a delightful note, the voice-chat addon, umurmur, works nicely.
I am slightly concerned about how the MineCRUX scripts operate in that they reach out to other websites to download and install software to the server. If the target website gets hacked, what bad might happen and how likely is it such a thing could occur?
It'd be nice to see the MineCRUX install script:
1) Play nicer with other OSes
2) Automatically ID the correct target partition to make into ReiserFS instead of sda1, or provide better guidance.
3) Use something like Ubuntu's Grub2 "other operating system ID" capabilities for the boot loader.
If I install the pigmap add-on, how would I replace the C10t output with the pigmap output?
On a similar note, but beyond the scope of MineCRUX, it'd be even nicer if I could replace the mapping with the output of the bukkit plugin DynMap.
It'd be really sweet if a script were available to install a web-UI for managing the murmur voice-chat server for user authorizations, maximum bytes/sec, etc. There are linux packages out there, but I am not adept enough to install them.
BTW: If you want to run multiple worlds, I recommend using the bukkit plugin "Multiverse". Then you only need to run one server, sending users to particular worlds using permissions while letting them move between them if you so choose. You can have Multiverse unload worlds that are not used to conserve server resources.
I can't thank you enough for this utterly thorough evaluation of how MineOS works for you. For organizations sake, I'll be transplanting my reply in the CRUX forum (so as to allow potential CRUX users to see it more readily alongside its own thread)
Are we able to delete any of the 3 worlds that we can create?
Over the past few days I've created my most recent project: build-your-own MineOS.
build-your-own MineOS is a entirely different project which does not attempt to replace MineOS/+. Instead, byo MineOS is an educational tool which aims to teach server admins about what components MineOS uses, walks you through how to properly add and configure each, and help you get a fully comprehensive understanding of how each mechanic makes for the best possible server.
If you ever felt like MineOS/+ needed a boatload more customization than microcore offers, and you're willing to learn how to get it set up, byo MineOS is for you!
byo MineOS holds to many ideals of the original MineOS in that it aims to be slim and functional. byo MineOS honors this by having only a 53 MB footprint and giving you the instructions and flexibility to add on any services you find necessary, from lighttpd, PHP, MySQL, and more--
Built from the CRUX Linux distro, byo MineOS will work on any hardware Linux has support for. So come take a look at byo MineOS:
http://minecraft.codeemo.com/buildmineos/
Based on that error, assuming you had gone through all other steps tells me that you may have missed the fdisk step of 'creating a bootable flag' for that partition.
fdisk step 3 -> option a, partition 1
To put your back right where you left off, you can boot back from the ISO, type in 'CRUX'
fdisk /dev/sda
a
1
(and then check your work with p, and ensure the asterisk is there--or check first to see if its there before changes.)
w (to exit)
unmount cd and reboot.
The only other place is if you didn't run 'lilo' after copying bzImage and System.map from the kernel steps. Follow the steps on my troubleshooting page if thats the case.
Let me know if either of these are it!
As it stands now the virtual system has the virtual HDD installed Primary Master IDE interface but I have also tried it on the SATA and SCSI interface with the same results. Not sure what the problem is, it just looks like it's not seeing a bootable device with a valid image.
I would recommend using only the SATA interface--which is the default Virtualbox HDD interface; I can't really see any benefit to IDE here, and it also requires much changes to the instructions provided. Whereas the instructions show /dev/sda and /dev/sda1--yours would be /dev/hda and /dev/hda1. This would need to be reflected in /etc/lilo.conf before running it.
Finally, if you have used the two solutions in the troubleshooting page, it could simply mean LILO was never successfully installed (perhaps from the above explanation). When you run LILO, what output do you get? Simply put, if it doesnt look similar to this, then LILO was never installed due to an incorrect lilo.conf setup.
lilo config and proper install result
Oh, and I guess another way might be if you do not have virtualbox set to boot off the HD. In Virtualbox settings, look at your VM settings, System Tab: "Boot order"--ensure "hard disk" is checked.
MineOS (as listed in this thread is no longer being updated).
Its being superceded by MineOS CRUX (2), which does support canarymod.
minecraft.codeemo.com/mineos2
I can, however, restore it and then it is found.
So right now I've been saving and restoring each time :l
How awkward.
Does the cromtab show up in game (Saving world, save complete) when the scheduled time hits, or does it save it all on the back end.
By definition, a RAMDISK, just like any ram is lost upon restart. Ramdisks are optional, and you elected to use it during the install, but it is not necessary if the restore is inconvenient.
On a side note, MineOS CRUX addresses all the inconveniences of my now-undeveloped MineOS (microcore), by taking care of all theses steps for you.
I highly suggest you have a look, as it has countless advantages over my previous (microcore) model, including crontabs manageable from the new web-ui, as well as RAMDISK use with automated restores so even after a reboot, your server will automatically come back up.
Drop a line by my forums http://minecraft.codeemo.com/community/ or send me an email/pm if you have any questions.
The ingame spam has nothing to do with crontabs or MineOS, but rather Minecraft. Anytime any method wants to backup a Minecraft world, it SHOULD ABSOLUTELY tell Minecraft to commit all chunks to disk, otherwise the backup is ...ineffective. Anytime a backup/archive occurs in MineOS, it does these actions--and as an OP (and only an OP) will you be exposed to the 'saving world to disk...save complete' "spam".
This is unavoidable spam as an admin, and would occur on any distro.
Also could you please make support for running on bare Mac machines? By that I mean make it compatible with EFI boot :smile.gif: (right now it won't show up after installation)
This could be removed by changing some lines of code. I might do so :tongue.gif:
1) www.luaserver.org
2) Modloadermp, minecraft forge and mods like that (you know the mods you put into the jar file :tongue.gif:)
BTW: Server wich has space in their name doesn't work :sad.gif:
I don't develop the Microcore-based MineOS anymore, now that MineOS CRUX is my main project. I have no plans for *this* distro to have any updates, so EFI boot is not an option. If desired, I can look into this for CRUX.
Such changes are not MineOS-based, so unless the code you're changing is at the java-level/minecraft, I don't see how an OS can suppress notifications that the server itself generates when running 'save-all'.
Also please try to look at the EFI boot for CRUX.
When i said "I might do so" I meant i would maybe make a modification to the needed class files and publish it. Also I would in that case be really happy if you masde it an option for MineOS, but that was not what i tried to say :tongue.gif:.
Then there was my attempt to give you two suggestion:
1. Support for www.luaserver.org and support for jar file mods like modloadermp and those (that would require a unzip zip thingy and file moving) :smile.gif:
2. Some way of deleting the server from the webUI
Also thx for making MineOS. It's NICE!
History:
I gave up on MineCraft serving after a plethora of updates made it exhausting trying to keep up, especially as I used bukkit.
The new MineCRUX settings that allow me to choose updates with a higher resolution sold me on trying again.
First of all, it is simple to install on bare-metal (without other OS).
The new CRUX package management system is smooth and with Will's scripts, the addons were idiot-proof.
However, as a home-user running a four person LAN server for my family, I didn't want to lose other OSes from the server computer. So I pursued a triple-boot option looking to end with Grub2 as the boot-manager rather than the less user-friendly and older LILO.
Three semi-negative notes:
1) The Web-UI always listed one person connected to any started server even without players logged on. I assume this was the Web-UI?
2) The console's log output for a server showed illegible characters for the "unknown" user ID. It'd be much better if it identified the Web-UI as that connection.
3) The Web-UI's connection took one of the server-property's permitted connections. Server managers should account for this when limiting the number of connection for a server.
Critical recommendation for success:
Before beginning install, use a more user-friendly partition manager, like GParted within Ubuntu or even a bootable rescue-type iso like Rescatux.
Resize and partition your target drive to provide space for MineCRUX as primary ReiserFS and primary linux swap.
Then do the MineCRUX install skipping the partition manager step and the "Make sda1 into ReiserFS" step.
Hardware:
Laptop x86 dual-core 1.5 GHz chips
Two 150 GB hard drives
2 GB RAM
Other OSes:
Vista & desktop Ubuntu
Challenges:
Compared to triple-boot install of the previous version of MineOS, the new partition manager is less easy to understand. It provides a plethora of file-system choices that don't match what MineCRUX wants and wouldn't let me make the choices I needed.
Running as RAM-disk did not work with very large world files like the Skylands v1.3 I wanted...I kept getting errors when transferring files to the server world, possibly due to out of space errors (over 200 MB attempted to copy). I had to reinstall MineCRUX to remove RAM option, not knowing how to change the filesystem without reinstall.
BIG BIG WARNING for MultiOS systems: Be extremely careful of the next step after running the partition manager where the install script asks it should make sda1 into ReiserFS. I hit OK before realizing sda1 is where my original WinXP OS was, toasting everything on it.
I had to reinstall the Win OS, using Vista this time...not so bad after I've been using Win7 elsewhere.
MineCRUX didn't play well with other partitions, possibly because of the partition manager's capabilities.
I solved the problem by partitioning and formatting the target drive before installing MineCRUX and not using MineCRUX's partition manager at all.
My installation steps:
1) Install any Windows OSes or begin with one. They don't play well with anyone else and apparently, with my skill level, need to be in the first partition. For me, a WinOS was on the first drive, sda.
2) Use GParted or other user-friendly linux-based partition manager to prepare the target drive and partition for MineCRUX (primary ReiserFS, primary linux swap) and your usual Linux OS (primary EXT4...later made logical by Ubuntu install). Be sure to note the ID for the MineCRUX partition. These all went into the second drive, sdb.
3) Install MineCRUX, making sure of the target partitions (for me sdb1 and sdb2). Skip the partition manager and the "Make sda1 ReiserFS" step.
4) Install Ubuntu using choice of "installing alongside other Linux OS". It will install Grub2 which should ID Windows and MineOS as boot options.
5) Re-boot, selecting MineCRUX to be sure Grub2 works it properly.
6) Boot into Ubuntu and modify the Grub2 options to list MineOS as default choice (this was easier than I thought it would be after letting the Ubuntu install do the hard work of identifying the correct boot parameters).
7) Re-boot without selecting an OS to make sure MineCRUX boots as default.
8) Make sure the MineCRUX is connected to the internet, update the MineOS scripts and "ports" (the CRUX package management system), and continue through the MineCRUX post-installation steps.
In the end, I have a triple-boot MineCRUX, Vista, and Ubuntu machine.
On a delightful note, the voice-chat addon, umurmur, works nicely.
I am slightly concerned about how the MineCRUX scripts operate in that they reach out to other websites to download and install software to the server. If the target website gets hacked, what bad might happen and how likely is it such a thing could occur?
It'd be nice to see the MineCRUX install script:
1) Play nicer with other OSes
2) Automatically ID the correct target partition to make into ReiserFS instead of sda1, or provide better guidance.
3) Use something like Ubuntu's Grub2 "other operating system ID" capabilities for the boot loader.
If I install the pigmap add-on, how would I replace the C10t output with the pigmap output?
On a similar note, but beyond the scope of MineCRUX, it'd be even nicer if I could replace the mapping with the output of the bukkit plugin DynMap.
It'd be really sweet if a script were available to install a web-UI for managing the murmur voice-chat server for user authorizations, maximum bytes/sec, etc. There are linux packages out there, but I am not adept enough to install them.
BTW: If you want to run multiple worlds, I recommend using the bukkit plugin "Multiverse". Then you only need to run one server, sending users to particular worlds using permissions while letting them move between them if you so choose. You can have Multiverse unload worlds that are not used to conserve server resources.
I can't thank you enough for this utterly thorough evaluation of how MineOS works for you. For organizations sake, I'll be transplanting my reply in the CRUX forum (so as to allow potential CRUX users to see it more readily alongside its own thread)
http://www.minecraftforum.net/topic/509740-mineos-crux-the-most-simple-way-to-host-minecraft/page__p__6721213#entry6721213