Show Posts
|
|
Pages: 1 2 [3] 4
|
|
37
|
General Category / General Discussion / Re: Using the SheevaPlug as a fileserver?
|
on: June 04, 2010, 03:42:39 PM
|
|
The other machines on your LAN, are they linux or winboxen? If linux, you have a choice between NFS or Samba to share files. If winboxen, Samba would be the easiest. I'm sharing via NFS with autofs to my personal LAN, all linux based. At a site I provide IT support for, filesharing is via Samba server (not a gplug!) to winboxen. I can help with <cough> config files! The stock gplugS kernel is not compiled with support for nfs-kernel-server, only nfs-user-server, which seems a bit slower to connect.
Jim
|
|
|
|
|
38
|
Linux Stuff / General Linux questions / Re: Trouble using the Plug as a print server
|
on: June 04, 2010, 07:03:47 AM
|
feffer, I'd be interested in seeing what my cupsd.conf file is missing: The default file has several stanzas added to the bottom where the posted one leaves off. We may indeed have different cupsd.conf.default files. Here's the last bit of mine: sheevaplug-debian:~# tail /etc/cups/cupsd.conf.default </Limit>
<Limit All> Order deny,allow </Limit> </Policy>
# # End of "$Id: cupsd.conf.in 7199 2008-01-08 00:16:30Z mike $". #
Jim
|
|
|
|
|
39
|
Linux Stuff / General Linux questions / Re: Trouble using the Plug as a print server
|
on: June 02, 2010, 05:54:34 PM
|
I'm currently running a cups print server with sucess across my network. My cupsd.conf file if it may help: sheevaplug-debian:/etc/cups# cat cupsd.conf # # # Sample configuration file for the Common UNIX Printing System (CUPS) # scheduler. See "man cupsd.conf" for a complete description of this # file. #
# Log general information in error_log - change "info" to "debug" for # troubleshooting... LogLevel warning
# Administrator user group... SystemGroup lpadmin root jbarnes
# Only listen for connections from the local machine. Listen *:631 Listen /var/run/cups/cups.sock
# Show shared printers on the local network. Browsing On BrowseOrder allow,deny BrowseAllow all BrowseAddress @LOCAL
# Default authentication type, when authentication is required... DefaultAuthType Basic
# Restrict access to the server... <Location /> Allow All Order allow,deny </Location>
# Restrict access to the admin pages... <Location /admin> Allow All Order allow,deny </Location>
# Restrict access to configuration files... <Location /admin/conf> AuthType Default Allow All Order allow,deny </Location>
# Set the default printer/job policies... <Policy default> # Job-related operations must be done by the owner or an administrator... <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit>
# All administration operations require an administrator to authenticate... <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default> AuthType Default #Require user @SYSTEM Allow All Order deny,allow </Limit>
# All printer operations require a printer operator to authenticate... <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs CUPS-Reject-Jobs> AuthType Default Require user @SYSTEM Order deny,allow </Limit>
# Only the owner or an administrator can cancel or authenticate a job... <Limit Cancel-Job CUPS-Authenticate-Job> Require user @OWNER @SYSTEM Order deny,allow </Limit>
<Limit All> Order deny,allow </Limit> </Policy>
# #
HTH, jim
|
|
|
|
|
40
|
Linux Stuff / General Linux questions / Re: Startup Scripts or monitor scripts
|
on: June 02, 2010, 11:39:44 AM
|
So is there a way that i can get the startup scripts for certain apps to only activate only certain conditions? like a uuid of a drive being mounted man udev will show you the options for what you desire. /etc/udev is the configuration directory HTH,
|
|
|
|
|
42
|
General Category / General Discussion / Re: A project with guruplug
|
on: May 25, 2010, 10:49:55 AM
|
Here's mine. I've commented out all but one getty. # /etc/inittab: init(8) configuration. # $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $
# The default runlevel. id:2:initdefault:
# Boot-time system configuration/initialization script. # This is run first except when booting in emergency (-b) mode. si::sysinit:/etc/init.d/rcS
# What to do in single-user mode. ~~:S:wait:/sbin/sulogin
# /etc/init.d executes the S and K scripts upon change # of runlevel. # # Runlevel 0 is halt. # Runlevel 1 is single-user. # Runlevels 2-5 are multi-user. # Runlevel 6 is reboot.
l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 # Normally not reached, but fallthrough in case of emergency. z6:6:respawn:/sbin/sulogin
# What to do when CTRL-ALT-DEL is pressed. ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
# Action on special keypress (ALT-UpArrow). #kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."
# What to do when the power fails/returns. pf::powerwait:/etc/init.d/powerfail start pn::powerfailnow:/etc/init.d/powerfail now po::powerokwait:/etc/init.d/powerfail stop
# /sbin/getty invocations for the runlevels. # # The "id" field MUST be the same as the last # characters of the device (after "tty"). # # Format: # <id>:<runlevels>:<action>:<process> # # Note that on most Debian systems tty7 is used by the X Window System, # so if you want to add more getty's go ahead but skip tty7 if you run X. # 1:2345:respawn:/sbin/getty 38400 tty1 #2:23:respawn:/sbin/getty 38400 tty2 #3:23:respawn:/sbin/getty 38400 tty3 #4:23:respawn:/sbin/getty 38400 tty4 #5:23:respawn:/sbin/getty 38400 tty5 #6:23:respawn:/sbin/getty 38400 tty6
# Example how to put a getty on a serial line (for a terminal) # T0:23:respawn:/sbin/getty 115200 ttyS0 #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100
# Example how to put a getty on a modem line. # #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
HTH, Jim
|
|
|
|
|
44
|
General Category / General Discussion / Re: A project with guruplug
|
on: May 21, 2010, 07:40:42 AM
|
As per the directions, you need to run wlan.sh It is said to be located in your /root directory. Mine is not. To find it no matter where it is use which: sheevaplug-debian:~# which wlan.sh /usr/bin/wlan.sh As you can see mine is in /usr/bin Now you need to execute the script upon startup. One way to do that is to call the program from /etc/rc.local sheevaplug-debian:~# /nano /etc/rc.local Insert the path to wlan.sh, wheather it be /root/wlan.sh or /usr/bin/wlan.sh on a new line after /root/init_setup.sh exit & reboot HTH, Jim
|
|
|
|
|
45
|
General Category / General Discussion / Re: A project with guruplug
|
on: May 21, 2010, 06:18:01 AM
|
The directions assume one knows how to create a file. Do this: #nano my.conf Now you have my.conf (a new file) opened with an editor (nano). Copy and paste or type the contents the example my.conf into your open nano session, replacing <SSID> and <WPA_KEY> with your values. ^x (that's ctrl-x) to exit, answer y to save, and then enter. Now when you issue the comand #cat my.conf The contents will be displayed. HTH, Jim
|
|
|
|
|