• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Linux Stuff / General Linux questions / Re: enabling/disabling services during startup on: July 16, 2010, 04:14:44 PM
Most of those look like important system services (logging, cron), that you might be able to mess with if you're feeling brave, but I wouldn't recommend it.  SSH is optional, but I'm guessing that's how you're connecting to your plug, so can't get rid of that.

The only exception is "ondemand"; I'm not sure what that is (and it doesn't appear in the Debian install I have on mine).  Okay, a quick search tells me it does CPU frequency scaling, which you maybe don't want if you're going for the best performance.  But you should find out more about it first.

If you want to learn more about any of the services being started, you just need to find out what package they belong to.  Just use "dpkg -S" on the script in the init folder and it will tell you (eg. "dpkg -S /etc/init.d/ondemand").  Then use "aptitude show" to get more information about that package (eg. "aptitude show initscripts").

Oh yeah, and if you're going for the fastest possible boot, there's only so much you can do by fiddling with system services.  If you want to get faster, you're going to need some deep magic that is well beyond me.
2  Linux Stuff / General Linux questions / Re: enabling/disabling services during startup on: July 16, 2010, 10:21:33 AM
Well, what services are being started?  Look through the various /etc/rc*.d folders for anything beginning with a capital S (those are the services being started), and tell us what they are.

Everything found in rcS.d is probably best to leave as-is, and there shouldn't be many other services starting unless you installed them in the first place.
3  Linux Stuff / General Linux questions / Re: Adding to empty fstab on: April 04, 2010, 07:28:23 AM
I haven't tried it, but I think you can just add the rootfs entry to your fstab and add the options there.  I'm guessing that the rootfs automounts simply because it's defined in UBoot and isn't defined in the fstab; adding it to fstab should (I think) make it take those options.

I suggest giving it a try and, if your plug doesn't boot, you can take the SD card to any working computer and edit out the extra fstab line there.
4  Linux Stuff / General Linux questions / Re: start X11 on bootup on: March 29, 2010, 02:49:03 PM
That's really not a good idea.  How familiar are you with Linux in general?  You should run everything as an unprivileged user (ie: not root) as much as possible.  This is extra true for running X.

But if you're certain you know what you're doing, you can take that code I posted earlier and add it to the end of /root/.profile (the /root directory is essentially the home directory for the root user).  However, I don't know how you can force an automatic login; you may have to look into a login manager for that.  I know gdm can do it.
5  Linux Stuff / General Linux questions / Re: start X11 on bootup on: March 27, 2010, 10:08:32 PM
On my desktop, I don't bother starting X until logged in.  If you're using a login manager like gdm, you'll have to do it like how fragfutter has suggested, but if you're skipping that, just add this to your ~/.profile

Code:
if [[ -z "$DISPLAY" ]] && [[ $(tty) = /dev/tty1 ]]; then
  startx
  logout
fi

This says that, if you're on terminal 1, start X; once X finishes, log out.  Since you start on terminal 1 by default, this'll make X start unless you switch to another terminal to prevent it.  Of course, you'll need a properly set-up ~/.xinitrc.  Also, this will only work for your login; logins by root or other users will need to be set up the same way to get the automatic X.
6  Linux Stuff / General Linux questions / Re: Adding to empty fstab on: March 18, 2010, 11:29:45 AM
Much thanks to DamonHD, who set me straight in a private message.  It turns out that all that autoconfig magic happens completely independently of the fstab.  As a result, I just needed to add the line to mount my disk, and none of the other mounted things were affected.

PS: I decided not to mount it at /home; I figured this would cause it to spin up with every login, which seems inefficient.  Then again, I've heard rumours of Seagate drives never spinning down in Linux, so I may be damned either way.  Is there any good way to watch for that without just standing by the drive and listening?
7  Linux Stuff / General Linux questions / Re: Can't get into lighttpd log directory anymore on: March 16, 2010, 06:33:00 PM
So you're saying that being able to read a directory is being able to see the contents, while being able to execute a directory is being able to access those contents?  That's pretty cool, thanks for sharing.
8  Linux Stuff / General Linux questions / Adding to empty fstab on: March 16, 2010, 06:30:14 PM
Dear everyone,

Some months ago, I installed a prebuilt Debian rootfs to an SD card on my SheevaPlug, and it's been working dreamily ever since.

Recently, I've decided that some extra storage capacity would be useful and would like to add an external USB drive (with its own power source, I know that).  So I went to edit /etc/fstab to mount the drive on boot, when I saw that its current contents are "# UNCONFIGURED FSTAB FOR BASE SYSTEM".

I know how to add an entry to an fstab, but I fear that just appending a line for the USB drive will make it go from some-magic-autoconfiguration into completely-broken.  I also know that there's more to an fstab than just the root partition, so I'm afraid of guessing my way through.

So, can anyone recommend how to get this filled in?  Since I think it might be relevant, here's the output of df:
Code:
Filesystem           1K-blocks      Used Available Use% Mounted on
tmpfs                   256876         0    256876   0% /lib/init/rw
udev                     10240       120     10120   2% /dev
tmpfs                   256876         4    256872   1% /dev/shm
rootfs                15413328    633608  13996764   5% /

PS: I'm considering mounting that USB drive at /home (but might just put it at /shared or something).  Any words on that?
9  Linux Stuff / General Linux questions / Re: Can't get into lighttpd log directory anymore on: March 15, 2010, 07:03:18 PM
I've never understood why, but directories must also be executable in order for you to get into them.
Code:
chmod +x /var/log/lighttpd
(done as root) will fix it.
10  Linux Stuff / General Linux questions / Re: FREE Webserver to access files??? on: March 02, 2010, 03:00:03 PM
The absolutely easiest way is to use just a webserver without any of these fancy content management systems; either lighttpd or apache will do, others might work too.  You're going to have to install a webserver first anyways, so give it a shot.

For lighttpd, you just need to edit the configuration file (/etc/lighttpd/lighttpd.conf) so that its document root (called "server.document-root" in the config) points to the folder in which all your files are stored, and make sure directory listings ("server.dir-listing", I think) are enabled.  Then, when you connect to your plug through a web browser, it should make all the files in that directory (and all directories below it) available for download.  To upload, you'll need a fancier system, but one step at a time, right?
11  Hardware and U-Boot firmware / U-Boot stuff / ext2load hanging on: January 13, 2010, 11:24:20 PM
Hi everybody.

On realizing that Ubuntu support would eventually end, I decided to give Arch mobile a try on my plug, following these instructions to the letter.  However, the boot sequence just prints out the results of mmcinit, then hangs (for at least 5 minutes or so; that's the longest I've waited).  Entering the commands manually seems to work perfectly up until the ext2load command, which simply does not respond at all.  In case you're wondering, ext2ls can see the files just fine.

I haven't seen any mention of this problem elsewhere and am at a loss.  If this is new, can I get it named after me?
Pages: [1]