I've seen the last days that we have new hardware versions here in our wiki and forum. I believe that we will get new visitors to this site. Persons who have never seen (or heard about) an old MBWE (with blue rings). And I'm not sure that they/we will have a chance to differentiate between the versions.

So I propose that we make it clear for which version a tutorial is approved. There will be tutorials which match for the orginal version (blue rings) and the new version (silver) and others will only match for one of these two versions.

A header like the following example would be very helpful in future.

This header can be enhanced to further systems, like the WD ShareSpace.

What do you think about this?

And btw. we need a clear name for the old and the new MBWE. Any idea's?

Best regards,
JpgOrganizer

MBWE II, 2x 500 GB
Firmware 01.01.18
Raid 1
Hacks: SSH, spindown

is it only with my account or every body has this behaviour?
Thx for your help,

I also would like to :
- put a comment for each link
- put a pictogram that would describe the easyness of applying the Hack ( 1->5 ?)
- put a pictogram that would say "Safe Hack" or "Risky Hack for newbies"

regards,

- we do not know why it is interesting to apply this hack
- the hack crashes samba and the standard web interface !

==> if nobody react to this post, i will delete the link from the Hack and tutorial page.

Regards,

 # /etc/inittab # # Copyright (C) 2001 Erik Andersen <andersen@codepoet.org> # # Note: BusyBox init doesn't support runlevels. The runlevels field is # completely ignored by BusyBox init. If you want runlevels, use # sysvinit. # # Format for each entry: <id>:<runlevels>:<action>:<process> # # id == tty to run on, or empty for /dev/console # runlevels == ignored # action == one of sysinit, respawn, askfirst, wait, and once # process == program to run # Startup the system ::sysinit:/bin/mount /proc ::sysinit:/bin/mount -a ::sysinit:/bin/mount -o remount,rw,noatime / ::sysinit:/bin/ln -s /proc/mounts /etc/mtab ::sysinit:/sbin/swapon -a # Set ownership and GUID/SUID on /shares/internal so with modified kernel # it forces ownership on files created on internal shares to be taken from # the parent directory. Need to do for internal, as the GUID/SUID state # isn't propagated from /shares because md4 is mounted over /shares/internal ::sysinit:/bin/chown www-data:www-data /shares/internal ::sysinit:/bin/chmod 6755 /shares/internal # Have to set ownership and GUID/SUID on /shares/external as Buildroot # device_table.txt appears not to be able to correctly set ownership and # permissions on directories ::sysinit:/bin/chown www-data:www-data /shares/external ::sysinit:/bin/chmod 6755 /shares/external # Set PUBLIC share directory owner as www-data and set SUID/GUID ::sysinit:/bin/chown www-data:www-data /shares/internal/PUBLIC ::sysinit:/bin/chmod ug+s /shares/internal/PUBLIC # Update ownership and modes for cups and samba ::sysinit:/bin/chgrp sys /var/spool/cups ::sysinit:/bin/chmod g+rws /var/spool/cups ::sysinit:/bin/chmod 1777 /var/spool/samba ::sysinit:/bin/chgrp users /var/spool/samba # Give lighttpd ownership of it's log directory ::sysinit:/bin/chown -R www-data:www-data /var/log/lighttpd # Give the WebUI ownership of /etc/smb.conf ::sysinit:/bin/chown -R www-data:www-data /etc/smb.conf # Load kernel modules # WDC ::sysinit:/usr/local/wdc/load-wdc-leds ::sysinit:/sbin/modprobe wdc-fan # RTC ::sysinit:/sbin/modprobe m41t00 ::sysinit:/sbin/modprobe i2c-oxnas-bitbash # USB ::sysinit:/sbin/modprobe ehci-oxnas ::sysinit:/sbin/modprobe usb-storage # Code Page for VFAT ::sysinit:/sbin/modprobe nls_cp437 # Power Button ::sysinit:/bin/sh /etc/init.d/load_power_button_module.sh # Mount the USB filesystem ::sysinit:/bin/mount -t usbfs usbfs /proc/bus/usb # Run any rc scripts ::sysinit:/etc/init.d/rcS # Set up a couple of getty's #tty1::respawn:/sbin/getty 38400 tty1 #tty2::respawn:/sbin/getty 38400 tty2 # Put a getty on the serial port ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 #ttyS1::respawn:/sbin/getty -L ttyS1 115200 vt100 #ttyS2::respawn:/sbin/getty -L ttyS2 115200 vt100 # Logging junk ::sysinit:/bin/touch /var/log/messages ::respawn:/sbin/syslogd -n -m 0 ::respawn:/sbin/klogd -n #tty3::respawn:/usr/bin/tail -f /var/log/messages # Stuff to do for the 3-finger salute ::ctrlaltdel:/sbin/reboot # Stuff to do before rebooting # tidy up using start scripts. ::shutdown:/etc/init.d/rcK # make sure everything else stops. ::shutdown:/bin/sync ::shutdown:/usr/bin/killall klogd ::shutdown:/usr/bin/killall syslogd ::shutdown:/sbin/swapoff -a ::shutdown:/bin/umount -a -r 

Note: this file does not include a line to start sshd at init.

Program: program-name
Program path: path-to-program
Config File: path-to-conf-file

 conf file here 

Possible alternate configurations:

 alternate conf-1 

 alternate conf-2 

We could also do it for init scripts and the like.

I just wondering if you/we could post all the default config file to every program thats need a config file?
So if somebody manage to fu*k up there config, this site have a default one?

-Stark

Seems to be broken :
wget http://www.mybookwe.com/file/memoire.sh no longerworks…

==> I propose to replace the link to the Mycheck project that is an excellent monitoring tool for the Mybook.

http://mybookworld.wikidot.com/mycheck-temp-mem-cpu-monitoring

Another point : do you know why the Sudo - Fix It is usefull?
It is stated that it breaks some standard feature…. Should'nt we remove this link from the Hack and Tutorial Main page?

At end, a good idea would be to propose an "Official" way of disabling Mionet in the Hack and TutorialMain page . This would prevent some newbies to brick their box…
I do not have rights to modify the Hack and tutorial Main page , so i cannot do the changes myself on the links…

Or maybe copy that section off into a new separate page.

We should remove the link, can anyone do that change?

If some people need to have the procedure for installing php, they can find it at the end of "web server" tutorial.

Either way I don't think the "Click here to…" would always work. We cannot guarantee the LAN IP. It is better to have clear written instructions that are easy to follow and explain exactly what is going on.

Maybe we should replicate Martin's instructions on this site so people don't have click out to an external site to get ssh. If someone could contact him and ask permission as well as provide the appropriate attribution. It's not like he would lose out on any adsense, so he might give us the go ahead.

I do agree that the SSH hack here: http://www.mybook-linux.co.nr/sshaccess.html should also be inserted into the first steps page, would one of you like to do it?

this forum is the only resource and that brings a responsibility greater than just being a place for experienced users to impress each other. help us dummies learn how to contribute. and if someone cut and pastes a command and doesn't go on to learn anything else, so what?

If people just type (or cut and paste) all the commands that are given in a tutorial, there's still a chance they will get curious and find out what they're actually doing. If you're not willing to learn some basic linux-administrator commands, you're in the wrong place.

There are a hundred ways to get one thing done… please, don't turn "hacking WD Mybook" into something else..

Hacks and Tutorials
Getting In

- Martin Hinner Page
- SSH linux

SSH Linux is more safe for anybody, why do'nt we change the order so that the SSH linux would be the preferred method ?
and explain the differences between the 2 methods.
(I would recommand not to use Martin Hinner's method…)

Most of people having ssh access tried the Martin Hinner….

We Could have a separate "Troubleshooting" forum where people can request some Help.
"Troubleshooting On basics usage and standard tutorials"
"Troubleshooting On installing something that is not described in a tutorial"

We Could have a "Hacking Project" part , where contributors would explain their project and work with the help of other members

We could have a "Validated Procedures" part (the current Tutorial main page), where projects that are known to be fully working, and are fully, step by step explained can be added.

would it be also possible to have some automatic configuration links using the same principle as the SSH access :
"Click this url and your Mybook will be optware enabled"
"Click this url and your Mybook will be configured with a Web server"
"Click this url and your Mybook will be configured with transmission…"
"Click this url and your Mybook will be configured with a NewsReader…"
"Click this url and your Mybook will be configured with Mycheck 1B3…"
(with the mention at your own risks)…

as i understand, it is just a question of making robust installation scripts and hosting this script on a php server?
This could prevent some newbies to do some errors when trying to apply some of the proposed hackings…

Perhaps we should have a section for discussions about MyBook.

• Forum
  • Optware
  • (Remote) access (ftp,telnet,ssh, samba & other things)
  • Torrenting
  • installing and configuring other programs
  • modifying the WD linux installation (fw upgrade , kernel modules ..)
  • installing other OS on mybook (debian & etc.)
• Talk about the site
  • discussion about the wiki & forums

as you can see this is very basic and i could use better titles. All suggestions welcome!