Re: chown all files on a data drive
Chris Howie [EMAIL PROTECTED] wrote:On Jan 5, 2008 6:54 AM, dave N [EMAIL PROTECTED] wrote: I used to run Fedora and now all the files on my data drives are uid 500 and gid 500. As root I've set the permissions for the drive (loaded under /share/other) to be owned by root but the group to be users. this didn't get recursively filtered down. Now under Debian the same user name and password I'd previously had are uid 1000 and gid 1000. Though I can access the files on the drive I can't do anything with them except as root. How can I rectify this? chown -R 1000:1000? This'll cause problems with the lost+found as well as any .Trash folders, should I then change the uids and gids back? I'm not sure exactly what you're trying to accomplish. If you want everyone to have access to the drive you can do something like: # chown -R root:root /share/other # chmod -R o+rwX /share/other If you only want your user account to have access then something like: # chown -R youruser /share/other # chown root:root /share/other # chown root:root /share/other/lost+found Chris Howie Thanks Chris. Why would I leave the owner and group of all of the files and folders as root? Why not root:users? Should the lost+found remain root:root and u -rw g-rw. There aren't many / any executable files so I'm not too worried about playing with the execute bit. This is only a single user machine but I have another that I am switching over to Debian which will have a couple users, same group, and access to the same files. Dave
Re: Waiting for root file system problem
--- Daniel Burrows [EMAIL PROTECTED] wrote: On Wed, Jan 02, 2008 at 10:24:07AM -0800, Andrew Sackville-West [EMAIL PROTECTED] was heard to say: On Wed, Jan 02, 2008 at 06:24:07AM -0500, dave N wrote: If you wait long enough (at least 30 seconds, maybe a couple minutes, I can't remember) you should get dropped to a busybox shell. Then look at /scripts/local-top and see what it's trying to run there. That may provide a clue. You can also pass break at the kernel command line. See initramfs-tools(8) for more boot options, including places you can break the init script. Daniel Well finally got in, followed somewhat what the other user did who had a similar problem and the messages on this thread. I've also found that the drive assignment varies depending on the boot device in my BIOS. If CDROM is 1st boot device and Hard drive is second: - my root partition, etc is on /dev/sda If Hard drive is 1st boot device and CDROM is second - my root partition, etc is on /dev/sdc ODD!! Setting labels in fstab caused many fsck errors and other problems, going back to device assignments everything worked fine. It seems that the partition devices and labels showed up differently with the older knoppix DVD I'm using and what is showing up with the Debian install. I'll need to verify this get an updated live DVD. Question: In the menu.lst grub file, how would I use the label assignment in the line: kernel /vmlinuz-2.6.18-5-686 root=/dev/sdc2 ro Thanks to everyone for the help. Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Waiting for root file system problem
Hi: I've installed Etch r1 and the only real thing I've done to the system is updated the system, though during the update it updated the kernel to the same kernel that was installed during the installation (used the medium to try and get more control over Grub install). The computer is about 2 years old, dual CPU Xeons, with 2 SATA drives and 2 SCSI drives. The system has not been highly used over the past 2 years. The system drive where Debian is installed is on a SATA 36 Gb Raptor that is just for the OS, drive was reformatted during install using ext3. During boot the system appears to find all the drives OK when I am reading as fast as I can, but then I get the following (from a photo of the screen messages) Begin: Mounting root file system... ... Begin: running /scripts/local-top ... ide0: I/O resource 0x1F0-0x1F7 not free. ide0: ports already in use, skipping probe ide1: I/O resource 0x170-0x177 not free. ide1: ports already in use, skipping probe Done. Begin: Waiting for root file system... ... And it stops right there. 0's above may be 8's, can't tell from the picture. I booted with Knoppix live and there is nothing in /var/log/messages, none of the logs appear to have changed since I last booted 2 days ago. I have not run fsck or anything else on this yet. Ideas? Thanks Dave
Re: Waiting for root file system problem
dave N [EMAIL PROTECTED] wrote: Hi: I've installed Etch r1 and the only real thing I've done to the system is updated the system, though during the update it updated the kernel to the same kernel that was installed during the installation (used the medium to try and get more control over Grub install). The computer is about 2 years old, dual CPU Xeons, with 2 SATA drives and 2 SCSI drives. The system has not been highly used over the past 2 years. The system drive where Debian is installed is on a SATA 36 Gb Raptor that is just for the OS, drive was reformatted during install using ext3. During boot the system appears to find all the drives OK when I am reading as fast as I can, but then I get the following (from a photo of the screen messages) Begin: Mounting root file system... ... Begin: running /scripts/local-top ... ide0: I/O resource 0x1F0-0x1F7 not free. ide0: ports already in use, skipping probe ide1: I/O resource 0x170-0x177 not free. ide1: ports already in use, skipping probe Done. Begin: Waiting for root file system... ... And it stops right there. 0's above may be 8's, can't tell from the picture. I booted with Knoppix live and there is nothing in /var/log/messages, none of the logs appear to have changed since I last booted 2 days ago. I have not run fsck or anything else on this yet. Ideas? Thanks Dave e2fsck -f /dev/sda8 reported no errors for the 5 different passes when done from a superuser window in Knoppix. I'm stumped! Dave
Re: Waiting for root file system problem
Andrei Popescu [EMAIL PROTECTED] wrote: On Wed, Jan 02, 2008 at 06:04:18AM -0500, dave N wrote: I booted with Knoppix live and there is nothing in /var/log/messages, none of the logs appear to have changed since I last booted 2 days ago. I have not run fsck or anything else on this yet. Ideas? This is usually a root device misnaming (is this a word?). Try setting up your fstab/menu.lst by uuid or labels. (If you have no idea what I'm talking about then I totally misjudged your knowledge level. Please report back with any questions you might have). Regards, Andrei Thanks, I'll try this a little later using lables or devices (/dev/sda2) I didn't know there were uuid's for devices, how do I find that for a partition?
Re: debian how-to
Douglas A. Tutty [EMAIL PROTECTED] wrote: On Mon, Dec 31, 2007 at 08:13:31AM -0500, [EMAIL PROTECTED] wrote: From: Douglas A. Tutty Sent: Monday, December 31, 2007 7:08 AM - Original Message - From: Rick Dooling Sent: Sunday, December 30, 2007 9:05 PM Hello all, I started out on Debian. Moved to Ubuntu for a few months, and then moved back to Debian a couple of years ago. I still find this Ubuntu How-To by David Martin very helpful, and I'm wondering if there is such an animal for Debian. http://www.funnestra.org/ubuntu/gutsy/ I know about Debian Reference and Debian Help site, but I'm more interested in a list of common how-tos that most people would like to do after installation, such as add mp3 playing ability, installing flash, mounting usb drives or ntfs drives and so on, the sort of things found in Martin's Ubuntu How-To. I know that some work in both. I guess I'm just curious if a similar thing already exists for Debian. And if not would it be a useful project to redo the Ubuntu How-To with an eye toward the Debian user. Thanks, Rick Dooling ** The docs are always under /usr/share/doc/[package name] apropos which locate find As a n00b to Debian (though I've used several distributions over the past few years) a lot of these simple things can take quite a while to figure out. For those of you who have been intimately involved and continuously using Debian it is so obvious but to the rest of us - nope. That kind of info should be in the debian-reference, debian-policy, fhs, etc. Doug. Thanks everyone for your suggestions, I was just trying to site some examples for a need for a more simplistic starter guide for n00bs, I've been doing already some of the suggestions and found my own alternatives. It's more the wading through the voluminous documentation and finding the right piece within that that's the issue. It's a very daunting and often confusing process trying to figure some of this out for one's self. As was suggested a quick summary of how to do some of these (with appropriate references), all in one spot was a nice idea, I thought and I was trying to substantiate the original post by Rick Dooling yesterday (inserted above) and his observation / suggestion / request / ??. Dave
