1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

web server

Discussion in 'Cisco/Linksys Network Storage Devices' started by jack_r, Mar 17, 2010.

  1. jack_r

    jack_r Guest

    Hi

    I want to install the jac4 firmware, but I want t know before what light web server is it possible to install on NAS200 after ?
    I want to know too, if it is possible to schedule the power on ?
    Is there a tool to write on NTfs usb support ?

    Thanks

    jack_r
     
  2. jac_goudsmit

    jac_goudsmit Super Moderator Staff Member Member

    The NAS200 uses a modified version of thttpd as built-in web server. It's possible to run a second instance by starting it from the command line (e.g. /usr/sbin/thttpd -C /path/to/my/thttpd.conf) or from a script but because of a modification it will load index.cgi as default page instead of index.htm or index.html. There are some other modifications in the web server that might cause unexpected problems, if you don't want to deal with them you can compile your own, or get one that's precompiled for i386.

    It's technically impossible to do a scheduled power on as far as I know. On a PC this is done by letting the battery-powered clock generate a PME# event but I doubt that this is implemented in the hardware on the NAS200 (the battery-powered clock is kinda wonky anyway, it's apparently connected to the parallel port. The kernel has quite a number of modifications to support it).

    NTFS support in the stock firmware and in my firmware is read-only. It may be possible to compile NTFS-3g for the NAS200 but I haven't looked into it.

    ===Jac
     
  3. morgan_greywolf

    morgan_greywolf Addicted to LI Member

    <blockquote>the battery-powered clock is kinda wonky anyway, it's apparently connected to the parallel port. The kernel has quite a number of modifications to support it</blockquote>

    Why? :confused:

    The NAS200 has some of the most bizarre hardware I've ever seen.
     
  4. jac_goudsmit

    jac_goudsmit Super Moderator Staff Member Member

    In a regular PC, the battery clock is on a couple of standard I/O addresses and can be written to and read from in a standard way (I don't remember the details). Apparently the RDC3210 doesn't emulate the battery clock and Linksys (Sercomm?) decided for some reason that it would be cheaper or easier to add a clock chip that's based on I2C, possibly because that way they don't have to add one or two other chips to decode the address on the ISA or PCI bus.

    There's no I2C bus on the RDC processor either, as far as I know, but emulating an I2C controller with bitbanging on the parallel port has been done many times before, and the parallel port wasn't needed for anything else. So they added a patch to the kernel that's normally applied for the Velleman parallel-to-I2C controllers. It works but unfortunately it means that at boot time the clock is set to some random time (Aug 9th, 2009 on my box, IIRC), and you have to run a program to set it from the battery clock, or use NTP.

    ===Jac
     

Share This Page