Fx.

the last few posts got real weird aside from whether you think its "a dick move" i think a few people on here misunderstand GPL open source + reverse engineering: (from wikipedia) Binary software[edit] This process is sometimes termed Reverse Code Engineering, or RCE.[9] As an example, decompilation of binaries for the Java platform can be accomplished using Jad. One famous case of reverse engineering was the first non-IBM implementation of the PC BIOS which launched the historic IBM PC compatible industry that has been the overwhelmingly dominant computer hardware platform for many years. Reverse engineering of software is protected in the U.S. by the fair use exception in copyright law.[10] The Samba software, which allows systems that are not running Microsoft Windows systems to share files with systems that are, is a classic example of software reverse engineering,[11] since the Samba project had to reverse-engineer unpublished information about how Windows file sharing worked, so that non-Windows computers could emulate it. The Wine project does the same thing for the Windows API, and OpenOffice.org is one party doing this for the Microsoft Office file formats. The ReactOS project is even more ambitious in its goals, as it strives to provide binary (ABI and API) compatibility with the current Windows OSes of the NT branch, allowing software and drivers written for Windows to run on a clean-room reverse-engineered GPL free software or open-source counterpart. WindowsSCOPE allows for reverse-engineering the full contents of a Windows system's live memory including a binary-level, graphical reverse engineering of all running processes.

me waiting for angry responses:

(please quote, makes thread far less confusing)

if tom/mods didn't want the information out there as grumpy says it'd be wiped and he'd be gone censorship on forums is bad (unless its illegal information) i think people see where you're coming from lionel but i think you just need to chill edit: and to be honest, unless specified surely emails with information that doesn't fall into corporate espionage isn't subject to any sort of NDA...

"loading initial ramdisk" i had some problems in here before, options were as below to fix: (if using traditional kernel build in arch) (in-case someone else is searching) https://www.archlinux.org/news/users-of-unofficial-kernels-must-enable-devtmpfs-support/ - These options are required: CONFIG_DEVTMPFS=y CONFIG_HOTPLUG=y CONFIG_INOTIFY_USER=y CONFIG_NET=y CONFIG_PROC_FS=y CONFIG_SIGNALFD=y CONFIG_SYSFS=y CONFIG_SYSFS_DEPRECATED*=n CONFIG_UEVENT_HELPER_PATH="" - These options might be needed: CONFIG_BLK_DEV_BSG=y (SCSI devices) CONFIG_TMPFS_POSIX_ACL=y (user ACLs for device nodes) (rebuilding now....) *crosses fingers* edit: nope not that ;( editedit: i need to learn kernel patches and do it properly ;( editeditedit: its not a 64/32bit thing...

and also can i put in a request for no more threads to be deleted? ;( hate loosing the place in conversation due to missing content

slapt-get works ...techncially

Made some patch files that edited the Kbuild and Makefile so I could compile unRAID and keep /dev/mapper, LVM support, etc. nice nice, able to point me in a good doc direction for that ? (or post the patchfiles ?) while i'm pretty good technically kernel patches and programming are not my area so the higher level docs went over my head edit: always just made the changes i wanted manually, havent delved into a "ABS type" kernel compiliation before

you can add and expand the array but (as far as i know) theres no easy way to remove drives as the data is striped (i assume you're doing the zfs equiv of raid5/6/10 - RaidZ rather than mirrored zpool) with ZFS your pool size is set for life when it is built. It can't be expanded in the same way that unraid can. Expansion = copy all data off pool, delete pool, create new larger / smaller pool, copy back all yo shit. Raid 5/6 with an lvm on top is a different story though and knocks the pants off unraid for performance and raid6 gives dual parity. However, all drives must be spinning due to the striping. HTH aah fair enough, always figured ZFS had the same "re-stripe" options as raid5/6 usually does with Arch and using the ABS system, how'd you manage the md driver patches? copy + paste seems to create errors in the makepkg component of ABS :>

you can add and expand the array but (as far as i know) theres no easy way to remove drives as the data is striped (i assume you're doing the zfs equiv of raid5/6/10 - RaidZ rather than mirrored zpool) "if installing under vmware add BusLogic to modules" note in the installer... testing

Did you add the filesystems you use and the kernel driver to the ramfs (using mkinitcpio.conf file)? might not have, was weird that it just hangs at that (for 8hours+ left it overnight) rather than giving any error, used same FS as the default kernel which still worked edit: maybe i was using MBR rather than GPT, grub2 definitely reads like it prefers GPT followed directions for both ABS and "traditional" from archsite.. as said now that i've poked around a bit in arch might work if i try again

Grub (packaged with Arch and other Distros) looks for the kernel a certain way. Did you install the os-prober package? It might have better success but I wouldn't count on it. Otherwise, use ABS and edit the PKGBUILD when you compile the Kernel in Arch. It will create it the way grub wants it. Syslinux is "dumb" and doesn't assume anything and you have more "control" over it. Probably why you were successful. i did not, yeah i tried the ABS method aswell, same issue.. when was messing around with archgrub2 i tried both ext2 and ext4 (both of which were compiled hard into the kernel)

yeah had it mounted as /flash then symlinked config to /boot/config (as mentioned in one of the older guides, probably unneeded but was getting late at night :>) well its not raid5, its jbod with parity + fuse, i only use it for media storage so its fine and i like the idea that if the machine + some disks die i have full copies of the data on the other disks (and "best" option i've found for this, i dont like flexraid) i just want the option to run up some LabVM's on there whenever i want to test something (and to move sickbeard etc off my xbmc machine) mainly running as unraid for media storage with drives spundown but with a nice ZFS array raid5 for my vms/datastore is my final goal which is why i've kept an eye on this and i like where xen/kvm is going with GPU passthrough, vmware definately slack with that (and i get why, never going to use that on an enterprise server) nice, will look further into it, after getting "lost" in the bootloader issues and compiling again and again to try track the issue i was over arch, need to take a breather then have another go worst case use lilo i guess (or track down why workstation hates archgrub - as slackgrub worked fine) my final goal used to be esxi with all this shit passed through but as you say each free version of esxi gets "meh'er" and i prefer not to passthrough, more complexity for no gain if you can get it all going in the native OS

Debian (Not really viable due to lack of systemd) seems you CAN run systemd on debian, looks pretty hairy/gross though ;(

longer form version: grub gets to "loading initial ram-disk" when using custom kernel, even when i use the exact kernel version that unraid uses and copy the .config from unraid then change nothing (both with and without the md files) edit: didnt play around too heavily though, using vmware workstation 10.1 with "other linux 3.x 64bit kernel" option, maybe there's something in there grub2 doesnt like yeah got it all mostly going in the end althoughhhh you cant symlink to fat32 and syslinux only works ON fat32 so while grub is optional syslinux cant be used for that (when i manually created the boot/config folder and tried to open the webgui i got errors about being unable to read/create super.dat so couldnt actually save device assignments, stopped looking into it after that, couldnt be bothered digging into permissions and traces for that, killed the VM and will have another go perhaps with lilo this time) edit: had done fullslackware64 before and did it again but i just dont like arch or slackware... so gonna have some goes at the other distros see what i like best :> im usually a debian guy but centos/opensuse looks like fun, used suse a few years back and liked the idea... editedit: was using arch64 fyi editediteditedit: (my brain is disjointed) always fighting the urge to go lfs/gentoo for super anal minimalistic vs actually picking something easy/simple to update/replace editediteditediteditediteditediteditediteditediteditediteditedit: once i figured out to use syslinux i managed it in newer kernels etc so there's something weird there

yeah i found that and it didnt fix the problem, also updated grub2 manually thats about the update script not working not even about the issue i had ;( edit: the links you gave me arent even the same error report that i had...

might look further into opensuse, looks easier and i am pretty fickle in my time

There is a bug in grub2 which will be fixed in the new release on the 1st. There are probably 10 posts about the grub error and how to fix it. Next time search or PM one of the many people here who are using Arch. It will save you a lot of time and when it's a 2 second fix. searched for the error i was getting, found thousands of results about all sorts of things - About 49,800 results (0.28 seconds) , i was googling and searching arch's forums rather than searching directly here though and nah i think next time i'll still have a go at getting it going myself before looking into things too heavily i'm weird like that edit: just searched here for ramdisk, nothing recent or about grub2 editedit: so whats the fix ?

seems its grub2 i'm not smart enough for, yay for syslinux

time to try this again now that i've seen arch

is a nice idea, have made one of slack before but never really investigated this going deep for it been playing with archunraid recently.... either i'm not smart enough for arch or for grub2, keep getting stuck at "loading initial ram-disk" for my custom kernel, even when i use the unraid version and copy the .config then change nothing bleh~