Commenti per Steppenwolf http://www.steppen-wolf.eu/blog Home Page Mon, 20 Feb 2012 22:20:02 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Commenti su LaCie 2Big Network hack: telnet, openssh, ntpd, cups and more.. di Sylvain http://www.steppen-wolf.eu/blog/2009/11/18/lacie-2big-network-hack-telnet-openssh-ntpd-cups-and-more/comment-page-2/#comment-2378 Sylvain Mon, 20 Feb 2012 22:20:02 +0000 http://www.steppen-wolf.eu/blog/?p=542#comment-2378 And at least, ssh with my user works at home !! :-) Thank you. And at least, ssh with my user works at home !!
:-)
Thank you.

]]> Commenti su LaCie 2Big Network hack: telnet, openssh, ntpd, cups and more.. di Sylvain http://www.steppen-wolf.eu/blog/2009/11/18/lacie-2big-network-hack-telnet-openssh-ntpd-cups-and-more/comment-page-2/#comment-2377 Sylvain Mon, 20 Feb 2012 22:17:42 +0000 http://www.steppen-wolf.eu/blog/?p=542#comment-2377 Goodnight, Sorry, it was my mistake ! Because tonight I run : ngc -u personal Starting service "personal", hang on.. Service "personal" is now in state: SERVICE_START_RUN User myuser restored Service "personal" is started! So it look like great ! But it strange because when I had reboot (not try wet), It seems to not work. I will test another day. Again, thanks for your time and help. Sylvain Goodnight,
Sorry, it was my mistake ! Because tonight I run : ngc -u personal
Starting service “personal”, hang on..
Service “personal” is now in state: SERVICE_START_RUN
User myuser restored
Service “personal” is started!

So it look like great ! But it strange because when I had reboot (not try wet), It seems to not work. I will test another day.

Again, thanks for your time and help.
Sylvain

]]> Commenti su LaCie 2Big Network hack: telnet, openssh, ntpd, cups and more.. di Steppenwolf http://www.steppen-wolf.eu/blog/2009/11/18/lacie-2big-network-hack-telnet-openssh-ntpd-cups-and-more/comment-page-2/#comment-2375 Steppenwolf Mon, 20 Feb 2012 14:36:26 +0000 http://www.steppen-wolf.eu/blog/?p=542#comment-2375 Actually the file name is "personal.i" with one "n", not "person<strong>n</strong>al.i". So if you called your file "personnal.i" with two "nn" then you must run this command: <code># cd /etc/initng/runlevel/ # echo personnal >> default.runlevel</code> Please check what you entered in the file <code>default.runlevel</code> Also, check that there are no windows carriage return characters (or some other strange character), which are different from those of Linux system. (which is a common mistake, when you do copy and paste from a webpage) Good luck. :-) Actually the file name is “personal.i” with one “n”, not “personnal.i”.
So if you called your file “personnal.i” with two “nn” then you must run this command:
# cd /etc/initng/runlevel/
# echo personnal >> default.runlevel

Please check what you entered in the file default.runlevel
Also, check that there are no windows carriage return characters (or some other strange character),
which are different from those of Linux system.
(which is a common mistake, when you do copy and paste from a webpage)

Good luck. :-)

]]> Commenti su LaCie 2Big Network hack: telnet, openssh, ntpd, cups and more.. di Sylvain http://www.steppen-wolf.eu/blog/2009/11/18/lacie-2big-network-hack-telnet-openssh-ntpd-cups-and-more/comment-page-2/#comment-2368 Sylvain Sun, 19 Feb 2012 22:01:18 +0000 http://www.steppen-wolf.eu/blog/?p=542#comment-2368 Well, I already try with ngc. But with your confirmation, it's seem to be a problem with my personnal.i file. Service "personnal" previously failed (NOT_FOUND), If a do a ls command, I saw the personnal.i file, but with green color. Is it a problem of right on the file ? (modules.i the same) Sylvain Well, I already try with ngc. But with your confirmation, it’s seem to be a problem with my personnal.i file.

Service “personnal” previously failed (NOT_FOUND),

If a do a ls command, I saw the personnal.i file, but with green color. Is it a problem of right on the file ?
(modules.i the same)
Sylvain

]]> Commenti su LaCie 2Big Network hack: telnet, openssh, ntpd, cups and more.. di Steppenwolf http://www.steppen-wolf.eu/blog/2009/11/18/lacie-2big-network-hack-telnet-openssh-ntpd-cups-and-more/comment-page-2/#comment-2367 Steppenwolf Sun, 19 Feb 2012 20:40:41 +0000 http://www.steppen-wolf.eu/blog/?p=542#comment-2367 You have to explicitly add the script to the services that start during the boot of the NAS: go to: <code># cd /etc/initng/runlevel/<code> and type: <code>echo personal >> default.runlevel</code> Yuo can test if the script is working using ngc: <code>ngc -u personal</code> to start the service; <code>ngc -r personal</code> to restart the service; <code>ngc -d personal</code> to stop the service; <code>ngc -s personal</code> to check the status of the service; <code>ngc -z personal</code> to restore service (zap) that has started and it went wrong; <code>ngc -h</code> for the help <code>ngc -H</code> for the extended help <code>ngc -6</code> for system reboot <code>ngc -0</code> for system Power off. (Not to be used. Is preferable to stop the system using the shutdown button) ecc. I added a small paragraph in the article with the output of ngc extended help command. You have to explicitly add the script to the services that start during the boot of the NAS:
go to:
# cd /etc/initng/runlevel/
and type:
echo personal >> default.runlevel
Yuo can test if the script is working using ngc:
ngc -u personal to start the service;
ngc -r personal to restart the service;
ngc -d personal to stop the service;
ngc -s personal to check the status of the service;
ngc -z personal to restore service (zap) that has started and it went wrong;
ngc -h for the help
ngc -H for the extended help
ngc -6 for system reboot
ngc -0 for system Power off. (Not to be used. Is preferable to stop the system using the shutdown button)
ecc.
I added a small paragraph in the article with the output of ngc extended help command.

]]> Commenti su LaCie 2Big Network hack: telnet, openssh, ntpd, cups and more.. di Sylvain http://www.steppen-wolf.eu/blog/2009/11/18/lacie-2big-network-hack-telnet-openssh-ntpd-cups-and-more/comment-page-2/#comment-2366 Sylvain Sun, 19 Feb 2012 19:32:01 +0000 http://www.steppen-wolf.eu/blog/?p=542#comment-2366 Your English is not so bad, even better than me :) I think I do everything right, but it's seems the script 'personal.i' doesn't run, so my user haven't right rules (myuser:x:503:100::/home:/bin/false). Is there any way tu run on demand the script to check if is it ok on file ? Your English is not so bad, even better than me :)

I think I do everything right, but it’s seems the script ‘personal.i’ doesn’t run, so my user haven’t right rules (myuser:x:503:100::/home:/bin/false).
Is there any way tu run on demand the script to check if is it ok on file ?

]]> Commenti su LaCie 2Big Network hack: telnet, openssh, ntpd, cups and more.. di Steppenwolf http://www.steppen-wolf.eu/blog/2009/11/18/lacie-2big-network-hack-telnet-openssh-ntpd-cups-and-more/comment-page-2/#comment-2363 Steppenwolf Sun, 19 Feb 2012 12:51:43 +0000 http://www.steppen-wolf.eu/blog/?p=542#comment-2363 The solution is simple, do not use the root account. You have to create a new user on your NAS from the web interface. In fact, the NAS will reset, at each startup, the file <code>/etc/passwd</code> and <code>/etc/shadow</code>, overwriting any modifications made from the shell. The script "<code>personal.i</code>" will automatically change the rights of the account, in particular, rewriting: - The user identifier (third field), the number that the operating system uses for internal purposes. Changing it to zero. (root) - The group identifier (fourth field). This number identifies the primary group of the user; That Are all files created by this user may Initially be accessible to this group. Changing it to zero. (group root) - The path to the user's home directory (sixth field). By changing the path with the "<code>/root</code>" directory - And changing the last field from "<code>/bin/false</code>" to "<code>/bin/bash</code>", allowing your account to access to ssh shell. Your username will become, to all effects, a new administrator with root privileges. Sorry for my bad English. The solution is simple, do not use the root account.
You have to create a new user on your NAS from the web interface.
In fact, the NAS will reset, at each startup, the file /etc/passwd and /etc/shadow, overwriting any modifications made from the shell.
The script “personal.i” will automatically change the rights of the account, in particular, rewriting:
- The user identifier (third field), the number that the operating system uses for internal purposes. Changing it to zero. (root)
- The group identifier (fourth field). This number identifies the primary group of the user; That Are all files created by this user may Initially be accessible to this group. Changing it to zero. (group root)
- The path to the user’s home directory (sixth field). By changing the path with the “/root” directory
- And changing the last field from “/bin/false” to “/bin/bash“, allowing your account to access to ssh shell.
Your username will become, to all effects, a new administrator with root privileges.

Sorry for my bad English.

]]> Commenti su LaCie 2Big Network hack: telnet, openssh, ntpd, cups and more.. di Sylvain http://www.steppen-wolf.eu/blog/2009/11/18/lacie-2big-network-hack-telnet-openssh-ntpd-cups-and-more/comment-page-2/#comment-2361 Sylvain Sat, 18 Feb 2012 23:44:23 +0000 http://www.steppen-wolf.eu/blog/?p=542#comment-2361 Sorry, I had a 403 error previously.. And if retry too.. I'm not lucky today :D Thank you for your time. I had create a file exports, not exactely like you, but it should work. If I change with telnet the root password of 2big, it works, I can access ssh from my laptop. Maybe I miss a step with your tutorial, I'll try another day to restart from beginning. Thanks for sharing :) Sorry, I had a 403 error previously.. And if retry too.. I’m not lucky today :D

Thank you for your time.
I had create a file exports, not exactely like you, but it should work.

If I change with telnet the root password of 2big, it works, I can access ssh from my laptop.

Maybe I miss a step with your tutorial, I’ll try another day to restart from beginning.
Thanks for sharing :)

]]> Commenti su LaCie 2Big Network hack: telnet, openssh, ntpd, cups and more.. di Steppenwolf http://www.steppen-wolf.eu/blog/2009/11/18/lacie-2big-network-hack-telnet-openssh-ntpd-cups-and-more/comment-page-2/#comment-2359 Steppenwolf Sat, 18 Feb 2012 20:35:46 +0000 http://www.steppen-wolf.eu/blog/?p=542#comment-2359 I'm sorry, I could not answer before, I was helping my friend with the C programming language. NFS. You have to export nas filesystem. To do this you have to configure <code>/etc/exports</code> file. something like this: <code># /etc/exports: the access control list for filesystems which may be exported # to NFS clients. See exports(5). # /home/share/<strong>path_name</strong> 192.168.1.0/24(ro)</code> where <strong>path_name</strong> is the name of your share on the nas, and <code>192.168.1.0/24(ro)</code> is the range of address of your lan. This is the way to export an NFS filesystem on a linux pc. Unfortunately i haven't been able to test the NFS kernel module. SSH. Do you have created your own user on the NAS? and above all, did you have created the <code>personal.i</code> file located in the <code>/etc/initng/</code> ? I'm talking about the section entitled "Persistenza dei privilegi dell’utente" (Persistence of user privileges). Be sure to edit <code>user = "utente"</code> replacing <code>"utente"</code> with your username. I’m sorry, I could not answer before, I was helping my friend with the C programming language.

NFS.
You have to export nas filesystem. To do this you have to configure /etc/exports file.
something like this:
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#

/home/share/path_name 192.168.1.0/24(ro)

where path_name is the name of your share on the nas, and
192.168.1.0/24(ro) is the range of address of your lan.
This is the way to export an NFS filesystem on a linux pc.
Unfortunately i haven’t been able to test the NFS kernel module.

SSH.
Do you have created your own user on the NAS?
and above all, did you have created the personal.i file located in the /etc/initng/ ?
I’m talking about the section entitled “Persistenza dei privilegi dell’utente” (Persistence of user privileges).
Be sure to edit user = "utente" replacing "utente" with your username.

]]> Commenti su LaCie 2Big Network hack: telnet, openssh, ntpd, cups and more.. di Sylvain http://www.steppen-wolf.eu/blog/2009/11/18/lacie-2big-network-hack-telnet-openssh-ntpd-cups-and-more/comment-page-2/#comment-2357 Sylvain Sat, 18 Feb 2012 17:01:19 +0000 http://www.steppen-wolf.eu/blog/?p=542#comment-2357 Sory for spam ;-) I can use rsync from telnet on 2big : root@LaCie-2big:/www/cgi-bin/public# rsync -avz 192.168.0.13:/home/user/Folder /home/share/ It works fine ! I continue to search for ssh (and nfs too). Ciao :] Sory for spam ;-)
I can use rsync from telnet on 2big :
root@LaCie-2big:/www/cgi-bin/public# rsync -avz 192.168.0.13:/home/user/Folder /home/share/
It works fine !
I continue to search for ssh (and nfs too).
Ciao :]

]]> Commenti su LaCie 2Big Network hack: telnet, openssh, ntpd, cups and more.. di Sylvain http://www.steppen-wolf.eu/blog/2009/11/18/lacie-2big-network-hack-telnet-openssh-ntpd-cups-and-more/comment-page-2/#comment-2356 Sylvain Sat, 18 Feb 2012 16:41:19 +0000 http://www.steppen-wolf.eu/blog/?p=542#comment-2356 $ ssh -v -l USER HOST debug1: Authentication succeeded (keyboard-interactive). Authenticated to 192.168.0.30 ([192.168.0.30]:22). debug1: channel 0: new [client-session] debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env XMODIFIERS = @im=none debug1: Sending env LANG = fr_FR.utf8 debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 Last login: Sat Feb 18 17:45:21 2012 from 192.168.0.13 debug1: channel 0: free: client-session, nchannels 1 Connection to 192.168.0.30 closed. Transferred: sent 1936, received 2088 bytes, in 0.1 seconds Bytes per second: sent 20590.5, received 22207.1 debug1: Exit status 1 :( $ ssh -v -l USER HOST

debug1: Authentication succeeded (keyboard-interactive).
Authenticated to 192.168.0.30 ([192.168.0.30]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env XMODIFIERS = @im=none
debug1: Sending env LANG = fr_FR.utf8
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
Last login: Sat Feb 18 17:45:21 2012 from 192.168.0.13
debug1: channel 0: free: client-session, nchannels 1
Connection to 192.168.0.30 closed.
Transferred: sent 1936, received 2088 bytes, in 0.1 seconds
Bytes per second: sent 20590.5, received 22207.1
debug1: Exit status 1

:(

]]> Commenti su LaCie 2Big Network hack: telnet, openssh, ntpd, cups and more.. di Sylvain http://www.steppen-wolf.eu/blog/2009/11/18/lacie-2big-network-hack-telnet-openssh-ntpd-cups-and-more/comment-page-2/#comment-2355 Sylvain Sat, 18 Feb 2012 16:35:02 +0000 http://www.steppen-wolf.eu/blog/?p=542#comment-2355 Hello, I think I've installed correctly ssh, but I can't connect to it from my pc. At the prompt after Password I've this message : Connection to 192.168.0.30 closed. Can you help me ? I would like also to use rsync. Thanks Sylvain Hello,
I think I’ve installed correctly ssh, but I can’t connect to it from my pc. At the prompt after Password I’ve this message : Connection to 192.168.0.30 closed.
Can you help me ? I would like also to use rsync.
Thanks
Sylvain

]]> Commenti su LaCie 2Big Network: supporto nfs di Sylvain http://www.steppen-wolf.eu/blog/2010/10/22/lacie-2big-network-supporto-nfs/comment-page-1/#comment-2353 Sylvain Sat, 18 Feb 2012 13:48:43 +0000 http://www.steppen-wolf.eu/blog/?p=834#comment-2353 Hi, I wrote like this, but i'm french :) First, a big thanks for your blog post about telnet, it works very fine, and for this nfs archive too. I succesful load module : root@LaCie-2big:/www/cgi-bin/public# lsmod Module Size Used by Not tainted nfsd 97924 0 exportfs 4512 1 nfsd lockd 69976 1 nfsd sunrpc 170452 2 nfsd,lockd usb_storage 68235 0 xfs 605412 1 But now I don't know how to mount a share folder on my desktop. I guess it's like this : # mount -t nfs 192.168.0.30:/home/share/ /media/lacie/ But I don't know the 2big path, and maybe we first do export nfs share on 2big ? Thanks for your help. Best regards Sylvain Hi,
I wrote like this, but i’m french :)
First, a big thanks for your blog post about telnet, it works very fine, and for this nfs archive too. I succesful load module :

root@LaCie-2big:/www/cgi-bin/public# lsmod
Module Size Used by Not tainted
nfsd 97924 0
exportfs 4512 1 nfsd
lockd 69976 1 nfsd
sunrpc 170452 2 nfsd,lockd
usb_storage 68235 0
xfs 605412 1

But now I don’t know how to mount a share folder on my desktop. I guess it’s like this : # mount -t nfs 192.168.0.30:/home/share/ /media/lacie/
But I don’t know the 2big path, and maybe we first do export nfs share on 2big ?

Thanks for your help.
Best regards
Sylvain

]]> Commenti su LaCie 2Big Network: supporto nfs di Steppenwolf http://www.steppen-wolf.eu/blog/2010/10/22/lacie-2big-network-supporto-nfs/comment-page-1/#comment-2265 Steppenwolf Sun, 05 Feb 2012 14:25:14 +0000 http://www.steppen-wolf.eu/blog/?p=834#comment-2265 autostart nfsd service: we need to edit <code>/etc/sysconfig/modules</code> and insert <code>nfsd</code> after <code>usb-storage</code> line: <code># vi /etc/sysconfig/modules # Begin /etc/sysconfig/modules - Module auto-loading configuration. # The syntax of this file is as follows: # <module> [<arg1> <arg2> ...] # # Each module should be on it's own line, and any options that you want # passed to the module should follow it. The line deliminator is either # a space or a tab. xfs usb-storage <b>nfsd</b> # End /etc/sysconfig/modules</code> and do ESC+wq for save the file. I have modified the modules archive: <a href="http://www.steppen-wolf.eu/blog/wp-content/kernel_modules_2big_nfsd.tar.gz" title="kernel nfsd modules for 2big Network" rel="nofollow">kernel_modules_2big_nfsd.tar.gz</a> In the new archive there are only these files: <code>/lib/modules/2.6.22.7/modules.alias /lib/modules/2.6.22.7/modules.ofmap /lib/modules/2.6.22.7/modules.inputmap /lib/modules/2.6.22.7/modules.isapnpmap /lib/modules/2.6.22.7/modules.usbmap /lib/modules/2.6.22.7/modules.ccwmap /lib/modules/2.6.22.7/modules.ieee1394map /lib/modules/2.6.22.7/modules.seriomap /lib/modules/2.6.22.7/modules.symbols /lib/modules/2.6.22.7/modules.pcimap /lib/modules/2.6.22.7/modules.dep /lib/modules/2.6.22.7/kernel/fs/exportfs/exportfs.ko /lib/modules/2.6.22.7/kernel/fs/lockd/lockd.ko /lib/modules/2.6.22.7/kernel/fs/nfsd/nfsd.ko /lib/modules/2.6.22.7/kernel/net/sunrpc/sunrpc.ko </code> I have modified modules.dep with the full absolute path for every kernel module, and i have changed the files rights to root user. To install the files in the nas you just extract the archive: <code># tar -xvzf kernel_modules_2big_nfsd.tar.gz -C /</code> Thanks again for your help Bert, if there is anything wrong with this procedure that I did let me know. The only problem I have and that I can test the nfsd until I return home. autostart nfsd service:
we need to edit /etc/sysconfig/modules and insert nfsd after usb-storage line:

# vi /etc/sysconfig/modules

# Begin /etc/sysconfig/modules - Module auto-loading configuration.

# The syntax of this file is as follows:
# [ ...]
#
# Each module should be on it's own line, and any options that you want
# passed to the module should follow it. The line deliminator is either
# a space or a tab.

xfs
usb-storage
nfsd

# End /etc/sysconfig/modules

and do ESC+wq for save the file.

I have modified the modules archive: kernel_modules_2big_nfsd.tar.gz

In the new archive there are only these files:

/lib/modules/2.6.22.7/modules.alias
/lib/modules/2.6.22.7/modules.ofmap
/lib/modules/2.6.22.7/modules.inputmap
/lib/modules/2.6.22.7/modules.isapnpmap
/lib/modules/2.6.22.7/modules.usbmap
/lib/modules/2.6.22.7/modules.ccwmap
/lib/modules/2.6.22.7/modules.ieee1394map
/lib/modules/2.6.22.7/modules.seriomap
/lib/modules/2.6.22.7/modules.symbols
/lib/modules/2.6.22.7/modules.pcimap
/lib/modules/2.6.22.7/modules.dep
/lib/modules/2.6.22.7/kernel/fs/exportfs/exportfs.ko
/lib/modules/2.6.22.7/kernel/fs/lockd/lockd.ko
/lib/modules/2.6.22.7/kernel/fs/nfsd/nfsd.ko
/lib/modules/2.6.22.7/kernel/net/sunrpc/sunrpc.ko

I have modified modules.dep with the full absolute path for every kernel module, and i have changed the files rights to root user.
To install the files in the nas you just extract the archive:
# tar -xvzf kernel_modules_2big_nfsd.tar.gz -C /
Thanks again for your help Bert, if there is anything wrong with this procedure that I did let me know.
The only problem I have and that I can test the nfsd until I return home.

]]> Commenti su LaCie 2Big Network: supporto nfs di Steppenwolf http://www.steppen-wolf.eu/blog/2010/10/22/lacie-2big-network-supporto-nfs/comment-page-1/#comment-2255 Steppenwolf Sat, 04 Feb 2012 03:25:59 +0000 http://www.steppen-wolf.eu/blog/?p=834#comment-2255 WOW! Thanks a lot for your contribute. (Ok, i apologize for my bad English :-p ) <blockquote><em>although i have not yet tested the userspace configuration of NFS…</em></blockquote> Userspace configuration of nfs is MORE or less deprecated.. wait... i got some nasty error... ok, found the problem... <code>[root@nas /oldroot/snapshots/snaps/03/lib/modules/2.6.22.7]# diff modules.dep.new /lib/modules/2.6.22.7/modules.dep --- modules.dep.new Fri Feb 3 17:51:20 2012 +++ /lib/modules/2.6.22.7/modules.dep Thu Mar 4 11:43:55 2010 @@ -1,37 +1,35 @@ -kernel/crypto/ecb.ko: -kernel/crypto/pcbc.ko: -kernel/fs/nfsd/nfsd.ko: kernel/fs/exportfs/exportfs.ko kernel/fs/lockd/lockd.ko kernel/net/sunrpc/sunrpc.ko -kernel/fs/nls/nls_cp850.ko: -kernel/fs/nls/nls_cp437.ko: -kernel/fs/isofs/isofs.ko: -kernel/fs/lockd/lockd.ko: kernel/net/sunrpc/sunrpc.ko -kernel/fs/fuse/fuse.ko: -kernel/fs/fat/fat.ko: -kernel/fs/udf/udf.ko: -kernel/fs/nfs/nfs.ko: kernel/fs/lockd/lockd.ko kernel/net/sunrpc/sunrpc.ko -kernel/fs/ntfs/ntfs.ko: -kernel/fs/vfat/vfat.ko: kernel/fs/fat/fat.ko -kernel/fs/xfs/xfs.ko: -kernel/fs/reiserfs/reiserfs.ko: -kernel/fs/hfsplus/hfsplus.ko: -kernel/fs/msdos/msdos.ko: kernel/fs/fat/fat.ko -kernel/fs/cifs/cifs.ko: -kernel/fs/exportfs/exportfs.ko: -kernel/net/appletalk/appletalk.ko: kernel/net/802/psnap.ko kernel/net/llc/llc.ko -kernel/net/802/p8022.ko: kernel/net/llc/llc.ko -kernel/net/802/psnap.ko: kernel/net/llc/llc.ko -kernel/net/llc/llc.ko: -kernel/net/sunrpc/sunrpc.ko: -kernel/drivers/scsi/iscsi_tcp.ko: kernel/drivers/scsi/libiscsi.ko kernel/drivers/scsi/scsi_transport_iscsi.ko -kernel/drivers/scsi/thor/mv61xx.ko: -kernel/drivers/scsi/libiscsi.ko: kernel/drivers/scsi/scsi_transport_iscsi.ko -kernel/drivers/scsi/scsi_transport_iscsi.ko: -kernel/drivers/scsi/scsi_wait_scan.ko: -kernel/drivers/char/hw_random/rng-core.ko: -kernel/drivers/usb/gadget/g_serial.ko: kernel/drivers/usb/gadget/marvell_udc.ko -kernel/drivers/usb/gadget/g_ether.ko: kernel/drivers/usb/gadget/marvell_udc.ko -kernel/drivers/usb/gadget/g_file_storage.ko: kernel/drivers/usb/gadget/marvell_udc.ko -kernel/drivers/usb/gadget/marvell_udc.ko: -kernel/drivers/usb/class/usblp.ko: -kernel/drivers/usb/storage/usb-storage.ko: -kernel/drivers/md/faulty.ko: +/lib/modules/2.6.22.7/kernel/fs/lockd/lockd.ko: /lib/modules/2.6.22.7/kernel/net/sunrpc/sunrpc.ko +/lib/modules/2.6.22.7/kernel/fs/vfat/vfat.ko: /lib/modules/2.6.22.7/kernel/fs/fat/fat.ko +/lib/modules/2.6.22.7/kernel/fs/cifs/cifs.ko: +/lib/modules/2.6.22.7/kernel/fs/nfs/nfs.ko: /lib/modules/2.6.22.7/kernel/fs/lockd/lockd.ko /lib/modules/2.6.22.7/kernel/net/sunrpc/sunrpc.ko +/lib/modules/2.6.22.7/kernel/fs/fat/fat.ko: +/lib/modules/2.6.22.7/kernel/fs/reiserfs/reiserfs.ko: +/lib/modules/2.6.22.7/kernel/fs/ntfs/ntfs.ko: +/lib/modules/2.6.22.7/kernel/fs/nls/nls_cp437.ko: +/lib/modules/2.6.22.7/kernel/fs/nls/nls_cp850.ko: +/lib/modules/2.6.22.7/kernel/fs/isofs/isofs.ko: +/lib/modules/2.6.22.7/kernel/fs/fuse/fuse.ko: +/lib/modules/2.6.22.7/kernel/fs/msdos/msdos.ko: /lib/modules/2.6.22.7/kernel/fs/fat/fat.ko +/lib/modules/2.6.22.7/kernel/fs/xfs/xfs.ko: +/lib/modules/2.6.22.7/kernel/fs/hfsplus/hfsplus.ko: +/lib/modules/2.6.22.7/kernel/fs/udf/udf.ko: +/lib/modules/2.6.22.7/kernel/crypto/ecb.ko: +/lib/modules/2.6.22.7/kernel/crypto/pcbc.ko: +/lib/modules/2.6.22.7/kernel/drivers/scsi/scsi_wait_scan.ko: +/lib/modules/2.6.22.7/kernel/drivers/scsi/scsi_transport_iscsi.ko: +/lib/modules/2.6.22.7/kernel/drivers/scsi/libiscsi.ko: /lib/modules/2.6.22.7/kernel/drivers/scsi/scsi_transport_iscsi.ko +/lib/modules/2.6.22.7/kernel/drivers/scsi/thor/mv61xx.ko: +/lib/modules/2.6.22.7/kernel/drivers/scsi/iscsi_tcp.ko: /lib/modules/2.6.22.7/kernel/drivers/scsi/libiscsi.ko /lib/modules/2.6.22.7/kernel/drivers/scsi/scsi_transport_iscsi.ko +/lib/modules/2.6.22.7/kernel/drivers/md/faulty.ko: +/lib/modules/2.6.22.7/kernel/drivers/char/hw_random/rng-core.ko: +/lib/modules/2.6.22.7/kernel/drivers/usb/storage/usb-storage.ko: +/lib/modules/2.6.22.7/kernel/drivers/usb/gadget/g_ether.ko: /lib/modules/2.6.22.7/kernel/drivers/usb/gadget/marvell_udc.ko +/lib/modules/2.6.22.7/kernel/drivers/usb/gadget/g_serial.ko: /lib/modules/2.6.22.7/kernel/drivers/usb/gadget/marvell_udc.ko +/lib/modules/2.6.22.7/kernel/drivers/usb/gadget/marvell_udc.ko: +/lib/modules/2.6.22.7/kernel/drivers/usb/gadget/g_file_storage.ko: /lib/modules/2.6.22.7/kernel/drivers/usb/gadget/marvell_udc.ko +/lib/modules/2.6.22.7/kernel/drivers/usb/class/usblp.ko: +/lib/modules/2.6.22.7/kernel/net/appletalk/appletalk.ko: /lib/modules/2.6.22.7/kernel/net/802/psnap.ko /lib/modules/2.6.22.7/kernel/net/llc/llc.ko +/lib/modules/2.6.22.7/kernel/net/802/p8022.ko: /lib/modules/2.6.22.7/kernel/net/llc/llc.ko +/lib/modules/2.6.22.7/kernel/net/802/psnap.ko: /lib/modules/2.6.22.7/kernel/net/llc/llc.ko +/lib/modules/2.6.22.7/kernel/net/llc/llc.ko: +/lib/modules/2.6.22.7/kernel/net/sunrpc/sunrpc.ko:</code> It seems that the NAS does not like local paths, and it needs absolute paths to the modules. Strange... ok, problem solved. I edited manually the original file, putting these two new line: /lib/modules/2.6.22.7/kernel/fs/nfsd/nfsd.ko: /lib/modules/2.6.22.7/kernel/fs/exportfs/exportfs.ko /lib/modules/2.6.22.7/kernel/fs/lockd/lockd.ko /lib/modules/2.6.22.7/kernel/net/sunrpc/sunrpc.ko /lib/modules/2.6.22.7/kernel/fs/exportfs/exportfs.ko: Testing: <code>[root@nas ~]# lsmod Module Size Used by Not tainted usb_storage 68235 0 xfs 605412 1 [root@nas ~]# free total used free shared buffers Mem: 61952 60228 1724 0 828 Swap: 128376 0 128376 Total: 190328 60228 130100 [root@nas ~]# modprobe -v nfsd Loading module sunrpc Loading module lockd Loading module exportfs Loading module nfsd [root@nas ~]# free total used free shared buffers Mem: 61952 59928 2024 0 928 Swap: 128376 0 128376 Total: 190328 59928 130400 [root@Anime ~]# lsmod Module Size Used by Not tainted nfsd 97924 0 exportfs 4512 1 nfsd lockd 68856 1 nfsd sunrpc 167892 2 nfsd,lockd usb_storage 68235 0 xfs 605412 1 </code> Good, now i need to do some tweaking.. Just for asking.. these file are really needed? modules.alias.bin modules.dep.bin modules.symbols.bin There are no *.bin in the orginal kernel.. I did all these tests via ssh, my NAS is at home while i'm off-site student If something had gone seriously wrong, I could not fix the problem before this Easter .. 04:21 AM... it's late. I need to sleep. I will continue testing tomorrow. Anyway, thanks very much for your contribution. I <strong>really</strong> appreciate it. :-) WOW! Thanks a lot for your contribute. (Ok, i apologize for my bad English :-p )

although i have not yet tested the userspace configuration of NFS…

Userspace configuration of nfs is MORE or less deprecated..

wait… i got some nasty error… ok, found the problem…

[root@nas /oldroot/snapshots/snaps/03/lib/modules/2.6.22.7]# diff modules.dep.new /lib/modules/2.6.22.7/modules.dep
--- modules.dep.new Fri Feb 3 17:51:20 2012
+++ /lib/modules/2.6.22.7/modules.dep Thu Mar 4 11:43:55 2010
@@ -1,37 +1,35 @@
-kernel/crypto/ecb.ko:
-kernel/crypto/pcbc.ko:
-kernel/fs/nfsd/nfsd.ko: kernel/fs/exportfs/exportfs.ko kernel/fs/lockd/lockd.ko kernel/net/sunrpc/sunrpc.ko
-kernel/fs/nls/nls_cp850.ko:
-kernel/fs/nls/nls_cp437.ko:
-kernel/fs/isofs/isofs.ko:
-kernel/fs/lockd/lockd.ko: kernel/net/sunrpc/sunrpc.ko
-kernel/fs/fuse/fuse.ko:
-kernel/fs/fat/fat.ko:
-kernel/fs/udf/udf.ko:
-kernel/fs/nfs/nfs.ko: kernel/fs/lockd/lockd.ko kernel/net/sunrpc/sunrpc.ko
-kernel/fs/ntfs/ntfs.ko:
-kernel/fs/vfat/vfat.ko: kernel/fs/fat/fat.ko
-kernel/fs/xfs/xfs.ko:
-kernel/fs/reiserfs/reiserfs.ko:
-kernel/fs/hfsplus/hfsplus.ko:
-kernel/fs/msdos/msdos.ko: kernel/fs/fat/fat.ko
-kernel/fs/cifs/cifs.ko:
-kernel/fs/exportfs/exportfs.ko:
-kernel/net/appletalk/appletalk.ko: kernel/net/802/psnap.ko kernel/net/llc/llc.ko
-kernel/net/802/p8022.ko: kernel/net/llc/llc.ko
-kernel/net/802/psnap.ko: kernel/net/llc/llc.ko
-kernel/net/llc/llc.ko:
-kernel/net/sunrpc/sunrpc.ko:
-kernel/drivers/scsi/iscsi_tcp.ko: kernel/drivers/scsi/libiscsi.ko kernel/drivers/scsi/scsi_transport_iscsi.ko
-kernel/drivers/scsi/thor/mv61xx.ko:
-kernel/drivers/scsi/libiscsi.ko: kernel/drivers/scsi/scsi_transport_iscsi.ko
-kernel/drivers/scsi/scsi_transport_iscsi.ko:
-kernel/drivers/scsi/scsi_wait_scan.ko:
-kernel/drivers/char/hw_random/rng-core.ko:
-kernel/drivers/usb/gadget/g_serial.ko: kernel/drivers/usb/gadget/marvell_udc.ko
-kernel/drivers/usb/gadget/g_ether.ko: kernel/drivers/usb/gadget/marvell_udc.ko
-kernel/drivers/usb/gadget/g_file_storage.ko: kernel/drivers/usb/gadget/marvell_udc.ko
-kernel/drivers/usb/gadget/marvell_udc.ko:
-kernel/drivers/usb/class/usblp.ko:
-kernel/drivers/usb/storage/usb-storage.ko:
-kernel/drivers/md/faulty.ko:
+/lib/modules/2.6.22.7/kernel/fs/lockd/lockd.ko: /lib/modules/2.6.22.7/kernel/net/sunrpc/sunrpc.ko
+/lib/modules/2.6.22.7/kernel/fs/vfat/vfat.ko: /lib/modules/2.6.22.7/kernel/fs/fat/fat.ko
+/lib/modules/2.6.22.7/kernel/fs/cifs/cifs.ko:
+/lib/modules/2.6.22.7/kernel/fs/nfs/nfs.ko: /lib/modules/2.6.22.7/kernel/fs/lockd/lockd.ko /lib/modules/2.6.22.7/kernel/net/sunrpc/sunrpc.ko
+/lib/modules/2.6.22.7/kernel/fs/fat/fat.ko:
+/lib/modules/2.6.22.7/kernel/fs/reiserfs/reiserfs.ko:
+/lib/modules/2.6.22.7/kernel/fs/ntfs/ntfs.ko:
+/lib/modules/2.6.22.7/kernel/fs/nls/nls_cp437.ko:
+/lib/modules/2.6.22.7/kernel/fs/nls/nls_cp850.ko:
+/lib/modules/2.6.22.7/kernel/fs/isofs/isofs.ko:
+/lib/modules/2.6.22.7/kernel/fs/fuse/fuse.ko:
+/lib/modules/2.6.22.7/kernel/fs/msdos/msdos.ko: /lib/modules/2.6.22.7/kernel/fs/fat/fat.ko
+/lib/modules/2.6.22.7/kernel/fs/xfs/xfs.ko:
+/lib/modules/2.6.22.7/kernel/fs/hfsplus/hfsplus.ko:
+/lib/modules/2.6.22.7/kernel/fs/udf/udf.ko:
+/lib/modules/2.6.22.7/kernel/crypto/ecb.ko:
+/lib/modules/2.6.22.7/kernel/crypto/pcbc.ko:
+/lib/modules/2.6.22.7/kernel/drivers/scsi/scsi_wait_scan.ko:
+/lib/modules/2.6.22.7/kernel/drivers/scsi/scsi_transport_iscsi.ko:
+/lib/modules/2.6.22.7/kernel/drivers/scsi/libiscsi.ko: /lib/modules/2.6.22.7/kernel/drivers/scsi/scsi_transport_iscsi.ko
+/lib/modules/2.6.22.7/kernel/drivers/scsi/thor/mv61xx.ko:
+/lib/modules/2.6.22.7/kernel/drivers/scsi/iscsi_tcp.ko: /lib/modules/2.6.22.7/kernel/drivers/scsi/libiscsi.ko /lib/modules/2.6.22.7/kernel/drivers/scsi/scsi_transport_iscsi.ko
+/lib/modules/2.6.22.7/kernel/drivers/md/faulty.ko:
+/lib/modules/2.6.22.7/kernel/drivers/char/hw_random/rng-core.ko:
+/lib/modules/2.6.22.7/kernel/drivers/usb/storage/usb-storage.ko:
+/lib/modules/2.6.22.7/kernel/drivers/usb/gadget/g_ether.ko: /lib/modules/2.6.22.7/kernel/drivers/usb/gadget/marvell_udc.ko
+/lib/modules/2.6.22.7/kernel/drivers/usb/gadget/g_serial.ko: /lib/modules/2.6.22.7/kernel/drivers/usb/gadget/marvell_udc.ko
+/lib/modules/2.6.22.7/kernel/drivers/usb/gadget/marvell_udc.ko:
+/lib/modules/2.6.22.7/kernel/drivers/usb/gadget/g_file_storage.ko: /lib/modules/2.6.22.7/kernel/drivers/usb/gadget/marvell_udc.ko
+/lib/modules/2.6.22.7/kernel/drivers/usb/class/usblp.ko:
+/lib/modules/2.6.22.7/kernel/net/appletalk/appletalk.ko: /lib/modules/2.6.22.7/kernel/net/802/psnap.ko /lib/modules/2.6.22.7/kernel/net/llc/llc.ko
+/lib/modules/2.6.22.7/kernel/net/802/p8022.ko: /lib/modules/2.6.22.7/kernel/net/llc/llc.ko
+/lib/modules/2.6.22.7/kernel/net/802/psnap.ko: /lib/modules/2.6.22.7/kernel/net/llc/llc.ko
+/lib/modules/2.6.22.7/kernel/net/llc/llc.ko:
+/lib/modules/2.6.22.7/kernel/net/sunrpc/sunrpc.ko:

It seems that the NAS does not like local paths, and it needs absolute paths to the modules.
Strange…
ok, problem solved. I edited manually the original file, putting these two new line:

/lib/modules/2.6.22.7/kernel/fs/nfsd/nfsd.ko: /lib/modules/2.6.22.7/kernel/fs/exportfs/exportfs.ko /lib/modules/2.6.22.7/kernel/fs/lockd/lockd.ko /lib/modules/2.6.22.7/kernel/net/sunrpc/sunrpc.ko

/lib/modules/2.6.22.7/kernel/fs/exportfs/exportfs.ko:

Testing:

[root@nas ~]# lsmod
Module Size Used by Not tainted
usb_storage 68235 0
xfs 605412 1
[root@nas ~]# free
total used free shared buffers
Mem: 61952 60228 1724 0 828
Swap: 128376 0 128376
Total: 190328 60228 130100
[root@nas ~]# modprobe -v nfsd
Loading module sunrpc
Loading module lockd
Loading module exportfs
Loading module nfsd
[root@nas ~]# free
total used free shared buffers
Mem: 61952 59928 2024 0 928
Swap: 128376 0 128376
Total: 190328 59928 130400
[root@Anime ~]# lsmod
Module Size Used by Not tainted
nfsd 97924 0
exportfs 4512 1 nfsd
lockd 68856 1 nfsd
sunrpc 167892 2 nfsd,lockd
usb_storage 68235 0
xfs 605412 1

Good, now i need to do some tweaking..
Just for asking.. these file are really needed?
modules.alias.bin
modules.dep.bin
modules.symbols.bin
There are no *.bin in the orginal kernel..

I did all these tests via ssh, my NAS is at home while i’m off-site student
If something had gone seriously wrong, I could not fix the problem before this Easter ..

04:21 AM… it’s late. I need to sleep. I will continue testing tomorrow.
Anyway, thanks very much for your contribution. I really appreciate it. :-)

]]>