Re: /etc/fstab question (problem)?

On Sun 23 Apr 2023 at 01:14:05 (-0700), David Christensen wrote: > On 4/22/23 21:11, David Wright wrote: > > On Sat 22 Apr 2023 at 18:51:26 (-0700), David Christensen wrote: > > > "Back in the day", people running Linux had computers with limited > > > amounts of storage and memory. I imagine an

Re: /etc/fstab question (problem)?

On Sun, 23 Apr 2023 01:14:05 -0700 David Christensen wrote: > On 4/22/23 21:11, David Wright wrote: > > On Sat 22 Apr 2023 at 18:51:26 (-0700), David Christensen wrote: ... > >> "Back in the day", people running Linux had computers with limited > >> amounts of storage and memory. I imagine an

old memory sticks (was Re: /etc/fstab question (problem)?

David Wright wrote: ... > That must be nice. I don't know what it might have cost. I'm afraid > I only use cast-offs. The oldest has ½GB memory. i have some older memory sticks and chips that i will gladly send to anyone who has older machines. the only condition i would have for the gift is

Re: /etc/fstab question (problem)?

On 4/22/23 21:11, David Wright wrote: On Sat 22 Apr 2023 at 18:51:26 (-0700), David Christensen wrote: On 4/22/23 08:24, David Wright wrote: On Fri 21 Apr 2023 at 15:46:30 (-0700), David Christensen wrote: On 4/21/23 08:12, Max Nikulin wrote: On 20/04/2023 04:03, David Christensen wrote: *

Re: /etc/fstab question (problem)?

On Sat 22 Apr 2023 at 18:51:26 (-0700), David Christensen wrote: > On 4/22/23 08:24, David Wright wrote: > > On Fri 21 Apr 2023 at 15:46:30 (-0700), David Christensen wrote: > > > On 4/21/23 08:12, Max Nikulin wrote: > > > > On 20/04/2023 04:03, David Christensen wrote: > > > > > * What if root

Re: /etc/fstab question (problem)?

On 4/22/23 08:24, David Wright wrote: On Fri 21 Apr 2023 at 15:46:30 (-0700), David Christensen wrote: On 4/21/23 08:12, Max Nikulin wrote: On 20/04/2023 04:03, David Christensen wrote: * What if root attempts to remove everything under /etc, in anticipation of mounting a file system at /etc,

Re: /etc/fstab question (problem)?

On Fri 21 Apr 2023 at 15:46:30 (-0700), David Christensen wrote: > On 4/21/23 08:12, Max Nikulin wrote: > > On 20/04/2023 04:03, David Christensen wrote: > > > * What if root attempts to remove everything under /etc, in > > > anticipation of mounting a file system at /etc, when one or > > > more

Re: gitification (was Re: /etc/fstab question (problem)?

Am 22.04.2023 um 08:33 schrieb Max Nikulin: > On 21/04/2023 00:43, songbird wrote: >> Max Nikulin wrote: >>> On 20/04/2023 19:10, songbird wrote:     one of the worst design decisions i've come across in the modern era was the lack of git respecting file metadata. >> >> i know what all

Re: gitification (was Re: /etc/fstab question (problem)?

On 21/04/2023 00:43, songbird wrote: Max Nikulin wrote: On 20/04/2023 19:10, songbird wrote: one of the worst design decisions i've come across in the modern era was the lack of git respecting file metadata. i know what all you've written below but it does not apply to what i want or how

Re: /etc/fstab question (problem)?

On 4/21/23 08:12, Max Nikulin wrote: On 20/04/2023 04:03, David Christensen wrote: * What if root attempts to remove everything under /etc, in anticipation of mounting a file system at /etc, when one or more programs have one or more open temporary files? David, you were wrote /etc instead

Re: gitification (was Re: /etc/fstab question (problem)?

Jeremy Ardley wrote: ... > I have not used these, but there seem to be some work-arounds for > storing metadata in/with git > > lfs has the ability to script xattr handling > > https://git-lfs.github.com/ i'll look at that one and see if it brings things to mind that i've already messed with

Re: /etc/fstab question (problem)?

On 20/04/2023 04:03, David Christensen wrote: * What if root attempts to remove everything under /etc, in anticipation of mounting a file system at /etc, when one or more programs have one or more open temporary files? David, you were wrote /etc instead of /tmp in several messages, so at

Re: /etc/fstab question (problem)?

On Fri, Apr 21, 2023 at 04:59:36AM -0400, rhkra...@gmail.com wrote: > On Wednesday, April 19, 2023 05:02:16 PM Default User wrote: > > sudo cp -r from the live usb. > > Recently I've been trying to get in the habit of using cp -aru because those > options do what I usually want: > >* -a

Re: /etc/fstab question (problem)?

On Wednesday, April 19, 2023 05:02:16 PM Default User wrote: > sudo cp -r from the live usb. Recently I've been trying to get in the habit of using cp -aru because those options do what I usually want: * -a preserves dates (and ownership and permissions), and doesn't follow (copy from)

Re: /etc/fstab question (problem)?

On Thu, Apr 20, 2023 at 11:29:26PM -0500, David Wright wrote: > On Thu 20 Apr 2023 at 22:16:56 (+0700), Max Nikulin wrote: > > On 20/04/2023 19:05, songbird wrote: > > > Default User wrote: > > > > And when partitions were named /dev/hda5, not > > > > 6a105a72-f5d5-441b-b926-1e405151ee84. > >

Re: /etc/fstab question (problem)?

On Thu 20 Apr 2023 at 22:16:56 (+0700), Max Nikulin wrote: > On 20/04/2023 19:05, songbird wrote: > > Default User wrote: > > > And when partitions were named /dev/hda5, not > > > 6a105a72-f5d5-441b-b926-1e405151ee84. With modern hardware, you'd probably not want to go back to those device names,

Re: gitification (was Re: /etc/fstab question (problem)?

On 4/20/23 14:51, songbird wrote: David Christensen wrote: ... Please describe your use-case(s), what the requirements are and why, and how Git is failing. i require maintaining an accurate record of the file and it's attributes - i consider that a part of the reason the file exists to

Re: gitification (was Re: /etc/fstab question (problem)?

On 21/4/23 05:41, songbird wrote: Stefan Monnier wrote: songbird I have not used these, but there seem to be some work-arounds for storing metadata in/with git lfs has the ability to script xattr handling https://git-lfs.github.com/ These applications work directly with metadata

Re: gitification (was Re: /etc/fstab question (problem)?

Stefan Monnier wrote: ... > BTW, the `bup` tool does add some of the needed functionality > (e.g. storing metadata), but it's not developed with an eye towards > merging some of that extra functionality into Git, and it doesn't aim to > be a "generic file storage tool" either :-( i tried bup

Re: gitification (was Re: /etc/fstab question (problem)?

David Christensen wrote: ... > Please describe your use-case(s), what the requirements are and why, and > how Git is failing. i require maintaining an accurate record of the file and it's attributes - i consider that a part of the reason the file exists to begin with (otherwise why have a

Re: gitification (was Re: /etc/fstab question (problem)?

On 4/20/23 05:10, songbird wrote: David Wright wrote: ... I see nothing unreasonable. The only oddity to me is that the listings you give (which are from the backups, I assume) have today's date, which means that the backup method is not preserving the file metadata. (If you've not used

Re: gitification (was Re: /etc/fstab question (problem)?

>> It could be a sister project of Git. > there are other attempts which are done for it and > process flows for me but i'd really prefer just a > simple flag or environment variable i could set which > would do it instead so then i'd be able to get rid of > the gyrations. AFAIK the Git

Re: gitification (was Re: /etc/fstab question (problem)?

Stefan Monnier wrote: ... > FWIW, I think it makes perfect sense for Git to ignore such metadata > in the context of the intended use of Git (i.e. tracking source code). it didn't make sense to me then and still doesn't but whatever... :) > But I wish there was a concerted effort to

Re: gitification (was Re: /etc/fstab question (problem)?

Max Nikulin wrote: > On 20/04/2023 19:10, songbird wrote: >>one of the worst design decisions i've come across in >> the modern era was the lack of git respecting file metadata. > > In the case of git you can get commit time from git log. i do not want commit time, i want the file

Re: gitification (was Re: /etc/fstab question (problem)?

On 20/04/2023 19:10, songbird wrote: one of the worst design decisions i've come across in the modern era was the lack of git respecting file metadata. In the case of git you can get commit time from git log. Version control systems update modification time on operations like "git

Re: /etc/fstab question (problem)?

On 20/04/2023 19:05, songbird wrote: Default User wrote: And when partitions were named /dev/hda5, not 6a105a72-f5d5-441b-b926-1e405151ee84. i use labels on all of my partitions and give them a legible name. those are what i use in my fstab and also in any grub or refind configs. i

Re: /etc/fstab question (problem)?

On Thu, 2023-04-20 at 10:09 +0200, DdB wrote: > You got your plan mapped out. and i agree, except for one little > detail: > see below. - > > Am 19.04.2023 um 22:06 schrieb Default User: > > > I think, it is the case when reboot is safer. Open file > > > descriptors > > > remain on the original

Re: gitification (was Re: /etc/fstab question (problem)?

> one of the worst design decisions i've come across in > the modern era was the lack of Git respecting file metadata. > > i got bit by this a few weeks ago yet again. i hate using > Git because of it destroying my file meta data. FWIW, I think it makes perfect sense for Git to ignore such

Re: gitification (was Re: /etc/fstab question (problem)?

On 20/4/23 20:10, songbird wrote: aside rant, thank gitification for that IMO. one of the worst design decisions i've come across in the modern era was the lack of git respecting file metadata. i got bit by this a few weeks ago yet again. i hate using git because of it

Re: /etc/fstab question (problem)?

Default User wrote: ... > Well, now I am totally confused.  > > I had hoped for, and really expected, an easy, obvious, intuitive > solution. But I guess that may be a distant memory of the good old > days, before [insert string of four-letter words here] like dbus, > systemd, and Gnome 3. And

Re: /etc/fstab question (problem)?

davidson wrote: ... > Consider the -a option to cp for backup/backdown operations, to > preserve all attributes (including timestamps), recursively copy > directories, and more. Read the manual for details. that's what i use by default for all copies. saves me a lot of wondering where

gitification (was Re: /etc/fstab question (problem)?

David Wright wrote: ... > I see nothing unreasonable. The only oddity to me is that the listings > you give (which are from the backups, I assume) have today's date, > which means that the backup method is not preserving the file metadata. > (If you've not used partition 5 for a while, the dates

Re: /etc/fstab question (problem)?

You got your plan mapped out. and i agree, except for one little detail: see below. - Am 19.04.2023 um 22:06 schrieb Default User: >> I think, it is the case when reboot is safer. Open file descriptors >> remain on the original partition. However I do not expect that single >> user mode or

Re: /etc/fstab question (problem)?

On Wed, 2023-04-19 at 23:40 +, davidson wrote: > On Wed, 19 Apr 2023 Default User wrote: > > On Wed, 2023-04-19 at 16:56 -0400, Default User wrote: > > > On Wed, 2023-04-19 at 15:36 -0500, David Wright wrote: > > > > On Wed 19 Apr 2023 at 16:06:57 (-0400), Default User wrote: > > > > > > > >

Re: [SOLVED] Re: /etc/fstab question (problem)?

On 4/19/23 17:24, Default User wrote: >> On Wed, 2023-04-19 at 18:07 +0700, Max Nikulin wrote: >>> Perhaps update-initramfs is necessary after restoring of >>> /etc/fstab in any chosen approach. Looking at the Wikipedia page "Initial ramdisk": https://en.wikipedia.org/wiki/Initrd

[SOLVED] Re: /etc/fstab question (problem)?

On Wed, 2023-04-19 at 15:09 -0700, David Christensen wrote: > On 4/19/23 15:03, David Christensen wrote: > > On 4/19/23 14:26, Default User wrote: > > > On Wed, 2023-04-19 at 14:03 -0700, David Christensen wrote: > > > > On 4/19/23 13:06, Default User wrote: > > > > > On Wed, 2023-04-19 at 18:07

Re: /etc/fstab question (problem)?

On Wed, 19 Apr 2023 Default User wrote: On Wed, 2023-04-19 at 16:56 -0400, Default User wrote: On Wed, 2023-04-19 at 15:36 -0500, David Wright wrote: On Wed 19 Apr 2023 at 16:06:57 (-0400), Default User wrote: Anyway, here is where I am at: I have two Clonezilla backups. 1) a full disk

Re: /etc/fstab question (problem)?

On 4/19/23 15:03, David Christensen wrote: On 4/19/23 14:26, Default User wrote: On Wed, 2023-04-19 at 14:03 -0700, David Christensen wrote: On 4/19/23 13:06, Default User wrote: On Wed, 2023-04-19 at 18:07 +0700, Max Nikulin wrote: Perhaps update-initramfs is necessary after restoring of

Re: /etc/fstab question (problem)?

On 4/19/23 14:26, Default User wrote: On Wed, 2023-04-19 at 14:03 -0700, David Christensen wrote: On 4/19/23 13:06, Default User wrote: On Wed, 2023-04-19 at 18:07 +0700, Max Nikulin wrote: Perhaps update-initramfs is necessary after restoring of /etc/fstab in any chosen approach. But, I

Re: /etc/fstab question (problem)?

On Wed, 2023-04-19 at 14:03 -0700, David Christensen wrote: > On 4/19/23 13:06, Default User wrote: > > On Wed, 2023-04-19 at 18:07 +0700, Max Nikulin wrote: > > > On 19/04/2023 16:16, David Christensen wrote: > > > > On 4/18/23 20:16, Stefan Monnier wrote: > > > > > > > > > You can also do > > >

Re: /etc/fstab question (problem)?

On 4/19/23 13:06, Default User wrote: On Wed, 2023-04-19 at 18:07 +0700, Max Nikulin wrote: On 19/04/2023 16:16, David Christensen wrote: On 4/18/23 20:16, Stefan Monnier wrote: You can also do mount --bind / /mnt and then look at /mnt/tmp. No need to reboot into single-user mode for

Re: /etc/fstab question (problem)?

On Wed, 2023-04-19 at 16:56 -0400, Default User wrote: > On Wed, 2023-04-19 at 15:36 -0500, David Wright wrote: > > On Wed 19 Apr 2023 at 16:06:57 (-0400), Default User wrote: > > > > > Anyway, here is where I am at: > > > > > > I have two Clonezilla backups. > > > 1) a full disk backup. > > >

Re: /etc/fstab question (problem)?

On Wed, 2023-04-19 at 15:36 -0500, David Wright wrote: > On Wed 19 Apr 2023 at 16:06:57 (-0400), Default User wrote: > > > Anyway, here is where I am at: > > > > I have two Clonezilla backups. > > 1) a full disk backup. > > 2) a "partitions" backup. > > So, if things really go bad, I can

Re: /etc/fstab question (problem)?

On Wed 19 Apr 2023 at 18:07:51 (+0700), Max Nikulin wrote: > On 19/04/2023 16:16, David Christensen wrote: > > On 4/18/23 20:16, Stefan Monnier wrote: > > > > > You can also do > > > > > > mount --bind / /mnt > > > > > > and then look at /mnt/tmp. > > > No need to reboot into single-user

Re: /etc/fstab question (problem)?

On Wed 19 Apr 2023 at 16:06:57 (-0400), Default User wrote: > Anyway, here is where I am at: > > I have two Clonezilla backups. > 1) a full disk backup. > 2) a "partitions" backup. > So, if things really go bad, I can theoretically revert to the setup as > of 2023-04-18, when this thread was

Re: /etc/fstab question (problem)?

Default User wrote: > > Well, now I am totally confused.  > > I had hoped for, and really expected, an easy, obvious, intuitive > solution. But I guess that may be a distant memory of the good old > days, before [insert string of four-letter words here] like dbus, > systemd, and Gnome 3. And

Re: /etc/fstab question (problem)?

On Wed, 2023-04-19 at 18:07 +0700, Max Nikulin wrote: > On 19/04/2023 16:16, David Christensen wrote: > > On 4/18/23 20:16, Stefan Monnier wrote: > > > > > You can also do > > > > > > mount --bind / /mnt > > > > > > and then look at /mnt/tmp. > > > No need to reboot into single-user mode

Re: /etc/fstab question (problem)?

On Wed, 2023-04-19 at 18:07 +0700, Max Nikulin wrote: > On 19/04/2023 16:16, David Christensen wrote: > > On 4/18/23 20:16, Stefan Monnier wrote: > > > > > You can also do > > > > > > mount --bind / /mnt > > > > > > and then look at /mnt/tmp. > > > No need to reboot into single-user mode

Re: /etc/fstab question (problem)?

On 19/04/2023 16:16, David Christensen wrote: On 4/18/23 20:16, Stefan Monnier wrote: You can also do mount --bind / /mnt and then look at /mnt/tmp. No need to reboot into single-user mode for that. +1  I like that better than the reboot/ live drive idea I posted. I think, it is the

Re: /etc/fstab question (problem)?

On 4/18/23 20:16, Stefan Monnier wrote: You can also do mount --bind / /mnt and then look at /mnt/tmp. No need to reboot into single-user mode for that. +1 I like that better than the reboot/ live drive idea I posted. David

Re: /etc/fstab question (problem)?

On Tue, Apr 18, 2023 at 10:15:30PM +0100, Tom Furie wrote: > On Tue, Apr 18, 2023 at 09:00:00PM +0200, to...@tuxteam.de wrote: > > Since Debian erases /tmp at each boot anyway: wouldn't it be > > much easier to set up an entry in fstab along the lines of > > > > tmpfs/tmptmpfs

Re: /etc/fstab question (problem)?

> So—I would clean /tmp as best you can before you close down, then > boot in single user mode, clean anything still remaining in /tmp, > edit your fstab, and then reboot. You can also do mount --bind / /mnt and then look at /mnt/tmp. No need to reboot into single-user mode for that.

Re: /etc/fstab question (problem)?

On Tue 18 Apr 2023 at 21:12:33 (-0400), Default User wrote: > > (Not so) fun fact: Clonezilla always refuses to back up swap > partitions. I don't know why. It's not clear to me how you could restore the entire rest of the system to the state it was in when you made your backup of swap. So the

Re: /etc/fstab question (problem)?

On 4/18/23 18:12, Default User wrote: On 4/18/23 07:59, Default User wrote: I just realized that my /tmp partition is not being mounted at startup. Finally, after the current situation is resolved, I would still like to know what caused the problem in the first place. Looking back at

Re: /etc/fstab question (problem)?

On Tue, 18 Apr 2023 21:12:33 -0400 Default User wrote: > (Not so) fun fact: Clonezilla always refuses to back up swap > partitions. I don't know why. Because there is no reason to do so. It has nothing in it of any value, except possibly to a cracker, and even that is stale. -- Does anybody

Re: /etc/fstab question (problem)?

On Tue, 2023-04-18 at 16:53 -0700, David Christensen wrote: > On 4/18/23 14:42, Default User wrote: > > On Tue, 2023-04-18 at 13:03 -0700, David Christensen wrote: > > > On 4/18/23 07:59, Default User wrote: > > > > Hey, I have a strange situation! > > > > > > > > I just realized that my /tmp

Re: /etc/fstab question (problem)?

On 4/18/23 14:42, Default User wrote: On Tue, 2023-04-18 at 13:03 -0700, David Christensen wrote: On 4/18/23 07:59, Default User wrote: Hey, I have a strange situation! I just realized that my /tmp partition is not being mounted at startup. Instead, I think the filesystem may be allocating

Re: /etc/fstab question (problem)?

On Tue, Apr 18, 2023 at 05:42:52PM -0400, Default User wrote: > stat -c %d / /tmp > 66306 > 66306 > (I am not sure what that means - is that saying that /tmp is mounted > under / on the / partition?) Yes. And by the way, "df /tmp" is a much more intuitive way to get that same answer. unicorn:~$

Re: /etc/fstab question (problem)?

On Tue, 2023-04-18 at 13:03 -0700, David Christensen wrote: > On 4/18/23 07:59, Default User wrote: > > Hey, I have a strange situation! > > > > I just realized that my /tmp partition is not being mounted at > > startup. > > Instead, I think the filesystem may be allocating space in another > >

Re: /etc/fstab question (problem)?

On Tue, Apr 18, 2023 at 09:00:00PM +0200, to...@tuxteam.de wrote: > Since Debian erases /tmp at each boot anyway: wouldn't it be > much easier to set up an entry in fstab along the lines of > > tmpfs/tmptmpfsdefaults,noatime,mode=1777 0 0 > > (assuming you want a tmpfs there,

Re: /etc/fstab question (problem)?

On 4/18/23 07:59, Default User wrote: Hey, I have a strange situation! I just realized that my /tmp partition is not being mounted at startup. Instead, I think the filesystem may be allocating space in another partition (maybe /root?) for tmp stuff. I would like to return to the prior setup,

Re: /etc/fstab question (problem)?

On Tue, Apr 18, 2023 at 09:37:51AM -0600, Charles Curley wrote: > On Tue, 18 Apr 2023 10:59:19 -0400 > Default User wrote: > > > What to do? > > I suspect that what you need to do is: > > 1) Preserve the current contents of /tmp, > > 2) Adjust fstab to include the /tmp partition, > > 3)

Re: /etc/fstab question (problem)?

On 18/04/2023 22:37, Charles Curley wrote: 1) Preserve the current contents of /tmp, 2) Adjust fstab to include the /tmp partition, 3) Mount the /tmp partition 4) Restore the contents of /tmp Some issues may arise due to files (regular ones, already deleted, sockets, fifos) opened by running

Re: /etc/fstab question (problem)?

Default User wrote: ... > What to do? if the tmp partition exists then put it back in your fstab and see if you can mount it manually. it may or may not mount. if it doesn't you can reboot and it should then mount. of course, make sure you have the mount point defined. > And if further

Re: /etc/fstab question (problem)?

On Tue, 18 Apr 2023 10:59:19 -0400 Default User wrote: > What to do? I suspect that what you need to do is: 1) Preserve the current contents of /tmp, 2) Adjust fstab to include the /tmp partition, 3) Mount the /tmp partition 4) Restore the contents of /tmp You should probably do all of

/etc/fstab question (problem)?

Am 18.04.2023 um 16:59 schrieb Default User: > Hey, I have a strange situation! Wow! Am I misunderstanding something? You seem to be well in control of your system, thus i am i bit surprised as of the simplicity of your question. If it was me, i would just find out, where exactly tmp resides now,

/etc/fstab question (problem)?

Hey, I have a strange situation! I just realized that my /tmp partition is not being mounted at startup. Instead, I think the filesystem may be allocating space in another partition (maybe /root?) for tmp stuff. I would like to return to the prior setup, where the /tmp partition is mounted at

Re: an fstab question

Ben Caradoc-Davies writes: > Martin, please show us the failing line. noatime works fine for me in > fstab Thank you. Your example reminded me of the error of my ways or rather syntax. The , was missing in the following line: UUID=[] /

Re: an fstab question

On 10/05/17 14:50, Martin McCormick wrote: One of the suggestions for improving the longevity of solid-state drives is to mount them using the noatime flag which reduces the number of times that inodes are written to. if I try something like: UUID=[string] / ext4 errors=remount-ro

an fstab question

One of the suggestions for improving the longevity of solid-state drives is to mount them using the noatime flag which reduces the number of times that inodes are written to. if I try something like: UUID=[string] / ext4 errors=remount-ro 0 1 It works. If I put relatime

Re: /etc/fstab question

On Mon, 11 Nov 2013 04:06:16 +0100 berenger.mo...@neutralite.org wrote: I am sorry, I do not understand what you mean by minimize wear. ( yes, I do not only use that list to learn stuff about Debian, it also helps me to work my English since I have no other occasions to do that, sadly ;)

Re: /etc/fstab question

Le 11.11.2013 10:09, Joe a écrit : On Mon, 11 Nov 2013 04:06:16 +0100 berenger.mo...@neutralite.org wrote: I am sorry, I do not understand what you mean by minimize wear. ( yes, I do not only use that list to learn stuff about Debian, it also helps me to work my English since I have no

Re: /etc/fstab question

berenger.mo...@neutralite.org wrote: Le 10.11.2013 19:54, Richard Owlett a écrit : berenger.mo...@neutralite.org wrote: Le 10.11.2013 18:06, Richard Owlett a écrit : Will doing chmod -R 777 /owlett allow all users of any Debian install having the edited /etc/fstab have unrestricted access to

Re: /etc/fstab question

David Christensen wrote: On 11/10/2013 09:06 AM, Richard Owlett wrote: I wish to have all users of all Debian installs on my laptop have unrestricted access to everything on a particular partition. It was suggested adding a line to /etc/fstab would accomplish my goal. ... /dev/sda5

Re: /etc/fstab question

David Christensen wrote: On 11/10/2013 10:54 AM, Richard Owlett wrote: I'm the only physical user. The laptop in question is dedicated to my learning experiments. It physically does not even have network access of any kind. Ouch. I assume you mean no Ethernet interface. Note that it is

Re: /etc/fstab question

Hi, On 11/10/2013 05:28 PM, berenger.mo...@neutralite.org wrote: Le 10.11.2013 18:06, Richard Owlett a écrit : Will doing chmod -R 777 /owlett allow all users of any Debian install having the edited /etc/fstab have unrestricted access to all files and folders on that partition? TIA It

Re: /etc/fstab question

On Mon, 2013-11-11 at 04:06 +0100, berenger.mo...@neutralite.org wrote: Le 10.11.2013 19:54, Richard Owlett a écrit : Since you seems to use ext2, you anyway do not have the log feature ( the thing which avoid corrupted files in case of a problem ) so I only see the drawback of file

/etc/fstab question

I wish to have all users of all Debian installs on my laptop have unrestricted access to everything on a particular partition. It was suggested adding a line to /etc/fstab would accomplish my goal. Original /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the

Re: /etc/fstab question

On Sun, 2013-11-10 at 11:06 -0600, Richard Owlett wrote: /dev/sda5/owlettext2rw,users,exec Will doing chmod -R 777 /owlett allow all users of any Debian install having the edited /etc/fstab have unrestricted access to all files and folders on that partition? I can't say

Re: /etc/fstab question

Le 10.11.2013 18:06, Richard Owlett a écrit : Will doing chmod -R 777 /owlett allow all users of any Debian install having the edited /etc/fstab have unrestricted access to all files and folders on that partition? TIA It will, but remember that it will also allow them to change file

Re: /etc/fstab question

Am Sonntag, 10. November 2013, 18:28:54 schrieb berenger.mo...@neutralite.org: Le 10.11.2013 18:06, Richard Owlett a écrit : Will doing chmod -R 777 /owlett allow all users of any Debian install having the edited /etc/fstab have unrestricted access to all files and folders on that

Re: /etc/fstab question

On Sun, 2013-11-10 at 11:06 -0600, Richard Owlett wrote: On rebooting it failed with a missing mount point message. And it failed for the first reboot only? Didn't you mount the fstab entries manually before rebooting? $ mount --help | grep fstab -a, --all mount all filesystems

Re: /etc/fstab question

Richard Owlett wrote: I wish to have all users of all Debian installs on my laptop have unrestricted access to everything on a particular partition. It was suggested adding a line to /etc/fstab would accomplish my goal. I saw that thread, and the suggestion, but didn't comment then because I

Re: /etc/fstab question

berenger.mo...@neutralite.org wrote: Le 10.11.2013 18:06, Richard Owlett a écrit : Will doing chmod -R 777 /owlett allow all users of any Debian install having the edited /etc/fstab have unrestricted access to all files and folders on that partition? TIA It will, but remember that it will

Re: /etc/fstab question

Ralf Mardorf wrote: On Sun, 2013-11-10 at 11:06 -0600, Richard Owlett wrote: /dev/sda5/owlettext2rw,users,exec Will doing chmod -R 777 /owlett allow all users of any Debian install having the edited /etc/fstab have unrestricted access to all files and folders on that partition?

Re: /etc/fstab question

Richard Owlett wrote: to which I added this line /dev/sda5/owlettext2rw,users,exec 'users' should be 'user'. Also add '0 0' at he end of the line. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Re: /etc/fstab question

On 11 November 2013 06:47, Siard shiems...@kpnplanet.nl wrote: Richard Owlett wrote: to which I added this line /dev/sda5/owlettext2rw,users,exec 'users' should be 'user'. Also add '0 0' at he end of the line. According to 'man 5 fstab', adding '0 0' is unecessary: If the

Re: /etc/fstab question

Le 10.11.2013 19:54, Richard Owlett a écrit : berenger.mo...@neutralite.org wrote: Le 10.11.2013 18:06, Richard Owlett a écrit : Will doing chmod -R 777 /owlett allow all users of any Debian install having the edited /etc/fstab have unrestricted access to all files and folders on that

Re: /etc/fstab question

On 11/10/2013 09:06 AM, Richard Owlett wrote: I wish to have all users of all Debian installs on my laptop have unrestricted access to everything on a particular partition. It was suggested adding a line to /etc/fstab would accomplish my goal. ... /dev/sda5 /owlett

Re: /etc/fstab question

On 11/10/2013 09:28 AM, berenger.mo...@neutralite.org wrote: ... In my opinion, if you want [a scratch pad partition for all groups/users], the easier solution is to use a partition system which does not have the user right feature. The first one which comes to my mind, is the FAT family. +1

Re: /etc/fstab question

On 11/10/2013 10:37 AM, Bob Proulx wrote: ... ['chmod -R 777 /owlett'] would be a bad thing to do for several reasons. One is that not all files should be executable. Mode 777 will make all files executable even files that should not be executable. Another is that if you ever copy a file out

Re: /etc/fstab question

On 11/10/2013 09:46 AM, Hans wrote: Wouldn't it be much easier to define a group, give the partition or directory this group write permission and put all users, which are allowed to write (and trusted) into this group? It's been a while, but I've done that. I seem to recall that the key was

Re: /etc/fstab question

On 11/10/2013 10:54 AM, Richard Owlett wrote: I'm the only physical user. The laptop in question is dedicated to my learning experiments. It physically does not even have network access of any kind. Ouch. I assume you mean no Ethernet interface. Note that it is possible to network over

Re: /etc/fstab question

David Christensen wrote: On 11/10/2013 09:46 AM, Hans wrote: Wouldn't it be much easier to define a group, give the partition or directory this group write permission and put all users, which are allowed to write (and trusted) into this group? It's been a while, but I've done that. I

mount/fstab question [WAS: Re: SV: Unidentified subject!]

On Tue, 20 Jul 1999 [EMAIL PROTECTED] wrote: Oki. I just put a 'defaults' there... What does nosuid,nodev and use do? Where is the man page for this? (Not the normal man fstab) The fstab manpage refers you to the mount manpage. In there, it tells what nearly all the options for all the various

Re: mount/fstab question [WAS: Re: SV: Unidentified subject!]

Oki. I just put a 'defaults' there... What does nosuid,nodev and use do? Where is the man page for this? (Not the normal man fstab) The options are filesystem-specific. Try mount(8) and nfs(5) to see what options are available for the filesystem you are mounting. Skip the nfs page if you do't

Re: fstab question

On 12-Mar-99 shaul wrote: I am using sudo for doing it. Perhaps the automounter can also help, but I have not tried it. I do not know if there is a way to do it with groups permitions and fstab. If there is I would also like to know.

Re: fstab question

On Thu, Mar 11, 1999 at 04:33:04AM -, Pollywog wrote: Is there a way for me to be able to mount both /a and /floppy on the KDE desktop (no, not at the same time)? It seems I will have to mount /a from the command line only, when I need to mount a dos floppy (not often). Do you really

Re: fstab question

Hi, When I use the 'auto' filesystem type in fstab, my vfat floppies are detected as umsdos and I lose the long filenames. Is there a way around this? Andy Holmes West Sussex, England [EMAIL PROTECTED] The path of my life is strewn with cow pats from the devil's own satanic herd!, Edmund

Re: fstab question

Is there a way for me to be able to mount both /a and /floppy on the KDE desktop (no, not at the same time)? It seems I will have to mount /a from the command line only, when I need to mount a dos floppy (not often). Using mtools can save you the trouble of dealing with fstab when dos/vfat

  1   2   >