This forum covers all Gentoo-related software not officially supported by Gentoo. Ebuilds/software posted here might harm the health and stability of your system(s), and are not supported by Gentoo developers. Bugs/errors caused by ebuilds from overlays.gentoo.org are covered by this forum, too.
i'm liking zen-sources. too bad i never had it to use reiser4 from when i do a vanilla install. Too bad ext4 progs doesn't exist yet to use that. Also I haven't really noticed any difference from the normal kernel. except the reiser4 patch.
Eckos wrote:i'm liking zen-sources. too bad i never had it to use reiser4 from when i do a vanilla install. Too bad ext4 progs doesn't exist yet to use that. Also I haven't really noticed any difference from the normal kernel. except the reiser4 patch.
there isnt anything we can do to make it faster really, most patches have to do with hardware support
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.
Eckos wrote:i'm liking zen-sources. too bad i never had it to use reiser4 from when i do a vanilla install. Too bad ext4 progs doesn't exist yet to use that. Also I haven't really noticed any difference from the normal kernel. except the reiser4 patch.
In zen-overlay there is e2fsprogs live ebuild, which supports ext4. Theres even fsck.ext4 and mkfs.ext4 there.
Eckos wrote:i'm liking zen-sources. too bad i never had it to use reiser4 from when i do a vanilla install. Too bad ext4 progs doesn't exist yet to use that. Also I haven't really noticed any difference from the normal kernel. except the reiser4 patch.
there isnt anything we can do to make it faster really, most patches have to do with hardware support
bash-3.1# sensors
Can't access procfs/sysfs file
Kernel interface access error
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
im not playing with genetics till at least June after I get back from Mexico
...and then genetics will have to compete with my thesis work and me programming my new car computer interface
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.
cosmo kernel # git-pull
Auto-merged MAINTAINERS
Auto-merged Makefile
CONFLICT (content): Merge conflict in Makefile
Auto-merged block/blk-core.c
Auto-merged block/blk-settings.c
Auto-merged drivers/acpi/Kconfig
Auto-merged drivers/acpi/Makefile
Auto-merged drivers/char/Kconfig
Auto-merged drivers/misc/Kconfig
Auto-merged drivers/net/wireless/Kconfig
Auto-merged drivers/net/wireless/Makefile
CONFLICT (content): Merge conflict in drivers/net/wireless/Makefile
Auto-merged drivers/net/wireless/atmel.c
Auto-merged drivers/net/wireless/zd1211rw/zd_mac.c
Auto-merged drivers/video/Kconfig
Auto-merged drivers/video/logo/Kconfig
CONFLICT (content): Merge conflict in drivers/video/logo/Kconfig
Auto-merged drivers/video/logo/Makefile
CONFLICT (content): Merge conflict in drivers/video/logo/Makefile
Auto-merged drivers/video/logo/logo.c
CONFLICT (content): Merge conflict in drivers/video/logo/logo.c
Auto-merged fs/btrfs/Makefile
CONFLICT (add/add): Merge conflict in fs/btrfs/Makefile
Auto-merged fs/btrfs/xattr.c
CONFLICT (add/add): Merge conflict in fs/btrfs/xattr.c
Auto-merged include/linux/ide.h
Auto-merged init/Kconfig
CONFLICT (content): Merge conflict in init/Kconfig
Auto-merged mm/filemap.c
Auto-merged net/ieee80211/ieee80211_tx.c
Automatic merge failed; fix conflicts and then commit the result.
Help?!
the server was going slow last night and I didnt want to trash the current master so i moved renamed the master branch for the time being and push a new master which some of you checked before I could push the new master over the old master.....(idk if that made sense to you)
anyway, run"git fetch" to get the latests refs, then "git reset --hard; git clean -f" to make sure you have no cruft left around, then since you cant delete the branch you are currently on run "git branch -M master broken; git checkout -b master origin/master; git branch -D broken"
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.