You are not logged in.
Pages: 1
I'm back to having a problem with this. Let's start over. I've got nearly a gigabyte of RAM in the machine I'm using to run a CrunchBang Linux live CD... and I've got a HUGE swap partition on a hard drive. I've got swap memory turned on. The Live OS reads the swap memory and it correctly reads the amount of RAM I've got in this machine. It still runs out of room when attempting to run 'system-update --upgrade'. Isn't there any way to use an external hard drive to store some of my updates?
much thanx
Yes. Basically, I'm aware now of the fact that swap would increase the amount of RAM available for the Live CD. I think the problem is that I was accidentally turning off my swap with a configuration script I wrote. I thought I had swap on. Thanks.
I searched for this on the forums first, so hopefully I did not just miss an obvious prior thread on this topic. If I did, please re-direct me.
I've noticed that when I run the CrunchBang Linux LiveCD on any of my PC's, if I attempt to do a system update, the live CD runs out of room, and so the updates mess up, and then on top of not being able to install the programs I need (like Apache2 and OpenSSH-Server), programs that are already installed (like FireFox) will mess up. Then I have to reboot to begin where I started.
How can I use a HDD to support my LiveOS system & home partition file system?
Funny.... but I feel the same way. I reserve my most powerful machines to run Windows XP, and all of my older, less powerful machines run Linux or in a rare case, MS-DOS -- for older stuff. Strangely enough, some of my older machines, to this day, run Linux (especially Debian Lenny w/ no GUI) or FBSD great -- but will not run Windows XP. I've got an old Gateway 400C that runs Linux with no problem, and originally came with Windows 98! Pretty old -- circa 1998!
Hmm, I've never tried a persistent USB. At the moment, I'm trying to find the /etc/gdn/gdm.conf field to specify which user to auto-login with.
[edit: apparently, you're supposed to use the -custom config file to make custom changes to GDM. I guess that the use of gdm.conf for custom gdm settings is deprecated.
Thanks, ceil! This is *probably* exactly what I'm looking for! Thanks for including the path, as well! I will try this out and then I will update this thread on how it works for me. If this whole thing with the auto-configuration script and a live CD works out, I shall have a rather nice script & tutorial set to contribute to the community here at Crunchbang Linux forums.
Thanks a lot,
Erezer
Yes. The account cannot be deleted unless the user is logged out/forced to log out, first. As soon as a forced logout happens, the user is somehow automatically logged in, even if I log out from that user and log in as a different sudoer user.
I just tried "Starring-out" the user in /etc/passwd and changing the home dir to /bin/false, but it still attempted to log in, and asked me if I wanted to use the /root directory as a home directory. I selected "no", but it attempts, once more, to log in, using the /root directory as a home dir.
I think I may be able to simply change the GDM auto-login configuration to keep this from happening. My auto configuration script force-copies many configurations for newly installed and already installed programs. If I can find the GDM configuration file for users who auto-login, I can probably fix this, in combination with madifying the /etc/passwd file, pkill -KILL -u crunchbang and 'userdel'.
Auto-login configuration is a feature on the crunchbang menu, but my aim is to cause this to happen automatically, as with everything else in the script.
I want to run CB 9.04.01 from a live CD, and automatically configure my system at startup via a script I have written.
Here is my problem. The live CD automatically logs in with the user 'crunchbang', which, by default, is a sudo user with no password. My script automatically configures my user accounts with logins and passwords, but I cannot figure out how to permanently disable the CrunchBang account. I can change the password and manually disable this automatic login, but I would rather have my script automatically remove or at least disable this user, requiring no password change to this account (including a forced /home directory removal, if removing the user).
I have tried 'pkill -KILL -u crunchbang', but the account logs back in automatically, unless I manually change this.
Restarting GDM recreates the user 'crunchbang'
Pages: 1
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.