On Thu, Jan 16, 2025 at 13:18:53 +0200, Anssi Saari wrote:
> Urs Thuermann writes:
> > mount | fgrep -vf <(awk '/^nodev/{print $2}' /proc/filesystems)
>
> Thanks. It has the benefit of not showing autofs, for example. But how
> to quote that for an alias?
The
Urs Thuermann writes:
> Felix Miata writes:
>
>> I have the following in ~/.bashrc for making that easier:
>>
>> alias Mnt='mount | egrep -v "cgroup|rpc|ramfs|tmpfs|^sys|on /dev|on /proc|on
>> /sys|on /var" | sort '
>
> mount | fgrep -
Felix Miata writes:
> I have the following in ~/.bashrc for making that easier:
>
> alias Mnt='mount | egrep -v "cgroup|rpc|ramfs|tmpfs|^sys|on /dev|on /proc|on
> /sys|on /var" | sort '
mount | fgrep -vf <(awk '/^nodev/{print $2}' /proc/filesystems)
urs
Greg Wooledge composed on 2025-01-14 07:30 (UTC-0500):
> Finally, please show the mount options of whatever file system is
> full. This means grepping something out of the output of "mount".
> It can be difficult to get the right line sometimes.
I have the following in ~
On 23 Jul 2024 14:49 -0300, from edua...@kalinowski.com.br (Eduardo M
KALINOWSKI):
> As described on the sshfs manpage, by default only the mounting user (root,
> in your case) can access the filesystem.
>
> You can use -o allow_other to allow other users. Or, if it's only eben
> that'll be acces
On 23/07/2024 14:40, Eben King wrote:
And after I issue this command:
root@cerberus:~# sshfs -o default_permissions
sshd@white_mycloud:/mnt/HD/HD_a2/Public /mnt/white_mycloud/
sshd@white_mycloud's password:
By the prompt (and the behavior below) I assume you're mounting as root.
it looks like
I have an older WD Mycloud Connect NAS. I'm currently trying to mount it
via sshfs (I prefer NFS, but can't make it work either). When it's not
mounted, /mnt looks like this to me:
eben@cerberus:~$ \ls -l /mnt
total 16
drwxr-xr-x 2 root root 4096 Mar 11 23:39 server
drwxr-xr-x 2
sandboxing. You can obtain command line
arguments. Attach to its mount namespace and inspect content of its
/proc//mounts or mountinfo. The next step would be to profile or at
least to trace a process.
I'm not sure i understand you there.
It was intended to express my surprise that "find&qu
lucky for 15 years and we should change
> the way we do things or is it a bug ? I will now take this to the
> kernel team and see what they have to say about it.
I take it you have read
https://docs.kernel.org/filesystems/sharedsubtree.html which says "A
shared mount can be replicated
> This can be solved with ACLs. Instead of creating a bind mount, this process
> that allows the user to share the directory can set an ACL and create a
> symlink.
For a few users maybe but not that easy when you have many thousands
users (that on top do not have local accounts). We&#
bug ? I will now take this to the
kernel team and see what they have to say about it.
> Especially if you keep insisting on using a way that was never officially
> supported, just because you got away with it for 15 years.
That's the very question i guess! How much mount is too much mount ;)
Thanks again for your help.
> At this point, I kinda doubt this issue has anything to do with Debian
> itself, but will most likely be an issue/limitation of the Linux Kernel
> itself.
>From my latest tests, it seems to point that way. Kernel 5.4 came with
a new mount API and it seems to break since then.
Duri
PS: if you maintain your own software and aren't able to find a way for
your user to do shares - especially while systems that most likely have
such functionality built-in out of the box surely exist, think Nextcloud
etc - that is covered by how Linux is supposed to be used, by definition
it's pret
Software is only tested to a certain degree. So mounts are tested to a
sensible number, if you move outside it, you have to bet on luck if it's
supported or not. At this point, I kinda doubt this issue has anything to
do with Debian itself, but will most likely be an issue/limitation of the
Linux K
it read/write to one user but read only to another
This can be solved with ACLs. Instead of creating a bind mount, this
process that allows the user to share the directory can set an ACL and
create a symlink.
PS: It would be better if you used a mailer that correctly sets mail
headers Refere
> For this, probably the easiest is to set up a common directory/a few common
> directories, set up proper permissions through use of groups and worst case
> create some symlinks from the user's home directories, if these directories
> really need to be accessible from within their home director
> Does it really have to be in the home directory? Can't the software (and/or
> the users) open files in, say, /shared/accounting?
It doesn't really matter where folders/mounts are. Users can share any
directory (and subdirectories) in their home directory with any other
user. The shared folder i
>> However do you need shared subtrees?
> I'm gonna test the effect of setting them to private.
This doesn't seem to fix the problem either
For this, probably the easiest is to set up a common directory/a few common
directories, set up proper permissions through use of groups and worst case
create some symlinks from the user's home directories, if these directories
really need to be accessible from within their home directories. That's
On 19/06/2024 05:46, Julien Petit wrote:
Rights are not the challenge here. It's to be able to share a
directory across multiple users.
For instance you would have : /users/bob/accounting shared with Alice
and accessible in her home directory /users/alice/accounting
Does it really have to be in
command line arguments.
> Attach to its mount namespace and inspect content of its /proc//mounts
> or mountinfo. The next step would be to profile or at least to trace a
> process.
I'm not sure i understand you there.
> I have not figured out from your description what proble
> Just to learn about it.
> What about using acl rather than bind mounts? What should be the
> problem in this solution?
As i said to Richard, rights are not the challenge here. It's to be
able to share a directory across multiple users. For instance you
would have : /users/bob/accounting shared w
n the directory, so you don't need a dedicated mount. But
> Maybe you want to create a separate topic where you describe exatcly what the
> basic requirements are and ask for suggestions what the best solution may be.
> Maybe something like AppArmor rules or other methods that aren
On 14/06/2024 16:30, Julien Petit wrote:
What processes are CPU hungry?
[...]
udisksd,
This one does not use mount namespace for the obvious reason. However it
tends to generate unnecessary activity. Perhaps it needs optimizations
for your case.
(fstrim)
There were some bugs including
ked to sandboxing.
>
> > However do you need shared subtrees? It may cause exponential
> > growth of number of moutpoints, see
>
> We only use mount bind to share an initial folder with other users
> with different access rights (rw or ro). So we probably don't
the
directory, so you don't need a dedicated mount. But Maybe you want to create a
separate topic where you describe exatcly what the basic requirements are and
ask for suggestions what the best solution may be. Maybe something like
AppArmor rules or other methods that aren't known by y
xecution permissions, just crate a separate
> partition, mount it somewhere - e.g. /home/test/mounts and tell mount/fstab
> to use the option noexec. No need for for your script. Or if it's a more
> advanced file system like btrfs you may be able to simply create a subvolume
&
st them.
It seems to happen with all processes accessing mounts. And since
disabling sandboxing with php fixed the problem for the php process,
it looks like it is linked to sandboxing.
> However do you need shared subtrees? It may cause exponential growth of
> number of moutpoints, see
ust crate a
separate partition, mount it somewhere - e.g. /home/test/mounts and tell
mount/fstab to use the option noexec. No need for for your script. Or if
it's a more advanced file system like btrfs you may be able to simply
create a subvolume with the same capabilities, no need to tink
On 12/06/2024 17:02, Julien Petit wrote:
for i in {1..14000}
do
echo "Mounting dir $i"
mkdir "/home/test/directories/dir_$i"
mkdir "/home/test/mounts/dir_$i"
mount --bind -o rw "/home/test/directories/dir_$i"
"/home/test/mounts/dir
Dear,
Not sure i should report a bug so here is a report first. For more
than 10 years now, we've been using mount binds to create shares rw or
ro. It's been working perfectly under older Debian. A few months ago,
we migrated to Ubuntu Jammy and started having processes running 100
Steve Matzura wrote:
> mount /mnt/bigvol1/dir-1 /home/steve/dir-1 -o bind,ro
In addition to what others have observed it might be worth mentioning
that the -v option to mount (i.e. verbose) often gives more information
about what's going on.
On Sun, Sep 17, 2023 at 02:43:16PM -0400, Steve Matzura wrote:
As Charles points out, this looks rather like CIFS, not NFS:
> # NAS box:
> //192.168.1.156/BigVol1 /mnt/bigvol1 cifs
> _netdev,username=,password=,ro 0 0
If Charles's (and my) hunch is cor
56/BigVol1 /mnt/bigvol1 cifs
_netdev,username=,password=,ro 0 0
Then I had the following line, replicated for several directories on bigvol1,
to bind them to directories on the home filesystem, all in a script called
/root/remount that I executed manually after each reboot:
mount /mnt/bigvol1/d
On Sun, 17 Sep 2023 14:43:16 -0400
Steve Matzura wrote:
> # NAS box:
> //192.168.1.156/BigVol1 /mnt/bigvol1 cifs
> _netdev,username=,password=,ro 0 0
Possibly part of the problem is that this is a CIFS (Samba) mount, not
an NFS mount.
Is samba installed?
If you try to mount t
=,password=,ro 0 0
Then I had the following line, replicated for several directories on
bigvol1, to bind them to directories on the home filesystem, all in a
script called /root/remount that I executed manually after each reboot:
mount /mnt/bigvol1/dir-1 /home/steve/dir-1 -o bind,ro
I had d
There is laptop with debian sid.
Sometimes on this laptop something create '/propagated-mount/'
directory.
I try to search with 'propagated-mount' but found only pages about
namespaces.
Can anyone point me to right direction? Which package is responsible for
creating th
On Sun 04 Jun 2023 at 11:59:21 (-0400), ce wrote:
> I have a mountpoint where all files under it have a group `fuse`.
>
> This is strange to me.
>
> As far as I can remember, Ubuntu doesn't do this.
Is this a system that's been around since wheezy? Up until then,
Debian had a system group called
gt; >
> > What kind of hardware is this file system on?
> >
> > What kind of file system is it?
> >
> > How did you mount it? (Show the command you used, and any output that
> > it produced.)
> >
> > What does "mount" with
On 6/5/23 7:23 AM, Greg Wooledge wrote:
>
> You can run the command "mount" with no arguments to see the details of
> each mounted file system. You don't even have to be root. I don't know
> how btrfs subvolumes work, so I don't know whether they appear in
On Sun, Jun 04, 2023 at 11:00:18PM -0400, ce wrote:
> On 6/4/23 5:46 PM, Greg Wooledge wrote:
> > What kind of hardware is this file system on?
> >
> > What kind of file system is it?
> >
> > How did you mount it? (Show the command you used, and any output th
s this file system on?
>
> What kind of file system is it?
>
> How did you mount it? (Show the command you used, and any output that
> it produced.)
>
> What does "mount" with no arguments say about the file system? (Hint:
> you can grep for the name of the file system
On Sun, Jun 04, 2023 at 11:59:21AM -0400, ce wrote:
> I have a mountpoint where all files under it have a group `fuse`.
You need to provide details, or else nobody can help you with anything.
What kind of hardware is this file system on?
What kind of file system is it?
How did you mount
I have a mountpoint where all files under it have a group `fuse`.
This is strange to me.
As far as I can remember, Ubuntu doesn't do this.
ghost is used to clone disk partition
it create .gho file, is it possible to mount it in linux?
Hello list,
I have the object storage service from the big providers (google cloud
storage, Amazon S3).
Now I want to mount them in Debian Linux as a block device.
Though I know there is s3fs:
sudo apt-get install s3fs
But i have no experience on it. Do you have any suggestion on using
> Filesystem Size Used Avail Use% Mounted on
> > /dev/vda1 9.7G 1.5G 7.9G 16% /
> > ...
> >
> > So I want to add a block device /dev/vdb and fdisk/format it and mount it
> > as /home dir.
>
> Have you checked your VPS provider's documentation
Hi,
On Mon, Mar 06, 2023 at 03:11:43AM +0800, Ken Young wrote:
> Filesystem Size Used Avail Use% Mounted on
> /dev/vda1 9.7G 1.5G 7.9G 16% /
> ...
>
> So I want to add a block device /dev/vdb and fdisk/format it and mount it
> as /home dir.
Have you checked y
ud-bloghost:~# df -h
>
> Filesystem Size Used Avail Use% Mounted on
>
> udev472M 0 472M 0% /dev
>
> tmpfs98M 496K 98M 1% /run
>
> /dev/vda1 9.7G 1.5G 7.9G 16% /
> ...
>
>
> So I want to add a block device /dev/vd
% /dev
tmpfs98M 496K 98M 1% /run
/dev/vda1 9.7G 1.5G 7.9G 16% /
...
So I want to add a block device /dev/vdb and fdisk/format it and mount it
as /home dir.
Since /home already exists (even have data in this path). can I mount it
without problem?
Sincerely,
Ken Young
On 18/01/2023 13:02, Richard Hector wrote:
I have a Wordpress site. The directory /srv/sitename/doc_root, and most
of the directories under it, are owned by user 'sitename'.
PHP runs as 'sitename-run', which has access (via group 'sitename') to
read all of that, but not write it. Some subdirec
../doc_root/wp-content/uploads, are group-writeable so that it can save
things there.
An authorised site maintainer, eg me ('richard') (but there may be any
number of others), needs to be able to write under /srv/sitename, so I
use bindfs to mount /srv/sitename under /home/richard/sit
On 18/01/2023 03:52, Richard Hector wrote:
On 17/01/23 23:52, Max Nikulin wrote:
lxc.idmap = u 0 10 1000
lxc.idmap = u 1000 1000 1
lxc.mount.entry = /home/richard/sitename/doc_root
srv/sitename/doc_root none bind,optional,create=dir
My goal is not to map container users to host users, b
On 17/01/23 23:52, Max Nikulin wrote:
On 17/01/2023 04:06, Richard Hector wrote:
I'm using bindfs in my web LXC containers to allow particular users to
write to their site docroot as the correct user.
I am not familiar with bindfs, so I may miss something important for
your use case.
Firs
On 17/01/2023 17:52, Max Nikulin wrote:
lxc.mount.entry = /home/richard/sitename/doc_root /srv/sitename/doc_root
none bind,optional,create=dir
Sorry, path inside the container should be without the leading slash.
lxc.mount.entry = /home/richard/sitename/doc_root srv/sitename/doc_root
none bin
On 17/01/2023 04:06, Richard Hector wrote:
I'm using bindfs in my web LXC containers to allow particular users to
write to their site docroot as the correct user.
I am not familiar with bindfs, so I may miss something important for
your use case.
First of all I am unsure why you prefer bin
cal/etc/bindfs_mounts'
while read line; do
mount "${line}"
done < "${file}"
In /usr/local/etc/bindfs_mounts (in the container):
===
On Wed, 21 Dec 2022 at 04:18, Lee wrote:
> On 12/20/22, David wrote:
> > $ echo -e '100:CD001\nXXX\n200:CD001' | awk 'BEGIN { FS=":" ; done=0 }
> > /CD001/ && done==0 { print $1 - 50 ; done=1 }'
> > 50
>
> You can do it without flags:
>
> $ echo -e '100:CD001\nXXX\n200:CD001' | awk -F: '/CD001/
Hi,
i meanwhile had a chance to inspect the image file and found that it
shows a repeating pattern of bytes with value 255 every 2352 bytes.
This corresponds to the size of medium level CD sectors, as can be obtained
by SCSI command "READ CD" (e.g. via Linux ioctl CDROMREADRAW).
CD-DA audio secto
On 12/20/22, David wrote:
> On Tue, 20 Dec 2022 at 22:04, David wrote:
>> On Tue, 20 Dec 2022 at 22:02, David wrote:
>
>> > $ echo -e '100:CD001\n200:CD001' | awk 'BEGIN { FS=":" } /CD001/ &&
>> > NR==1 { print $1 - 50 }'
>> > 50
>>
>> Oops, my mistake, that's not the solution. Give me another m
> Not that that is always important. But I just commented today
> because so often 'awk' is ignored as if its only capability is 'print $1'
> when in fact it is actually very powerful but neglected.
FWIW, `sed` can also do that job. Tho the subtraction part would take
a lot more work (`sed` does
On Tue, 20 Dec 2022 at 22:04, David wrote:
> On Tue, 20 Dec 2022 at 22:02, David wrote:
> > $ echo -e '100:CD001\n200:CD001' | awk 'BEGIN { FS=":" } /CD001/ &&
> > NR==1 { print $1 - 50 }'
> > 50
>
> Oops, my mistake, that's not the solution. Give me another minute and I
> will post a better one
Hi,
The Wanderer wrote:
> With the '-o' option, grep prints only the parts of the line that were
> matched - but the plural here is very relevant. If that guess is
> correct, then the "line" in question has *four* occurrences, so grep
> prints them all - each on a separate line of output.
The man
Hi,
Yvan Masson wrote:
> Kernel logs say "isofs_fill_super: get root inode failed".
So there is more stuff inserted between the volume descriptor and the
root directory of the ISO.
(The descriptor contains a minimal directory record which points to
the content of the root directory. All attribut
On Tue, 20 Dec 2022 at 22:02, David wrote:
> $ echo -e '100:CD001\n200:CD001' | awk 'BEGIN { FS=":" } /CD001/ &&
> NR==1 { print $1 - 50 }'
> 50
Oops, my mistake, that's not the solution. Give me another minute and I
will post a better one one.
On Tue, 20 Dec 2022 at 21:53, The Wanderer wrote:
> On 2022-12-20 at 05:37, David wrote:
> > On Tue, 20 Dec 2022 at 21:10, The Wanderer wrote:
> >> On 2022-12-20 at 02:51, Thomas Schmitt wrote:
> >>> This contradicts the promises of man grep about option -m.
> >> It does seem to, at least at a
On 2022-12-20 at 05:37, David wrote:
> On Tue, 20 Dec 2022 at 21:10, The Wanderer
> wrote:
>
>> On 2022-12-20 at 02:51, Thomas Schmitt wrote:
>>> This contradicts the promises of man grep about option -m.
>>
>> It does seem to, at least at a glance - but I think I've figured
>> out what's going
On Tue, 20 Dec 2022 at 21:10, The Wanderer wrote:
> On 2022-12-20 at 02:51, Thomas Schmitt wrote:
> >>> offst=$( expr \
> >>> $( grep -a -o -b -m 1 CD001 cdimage.iso \
> >>> | sed -e 's/:/ /' \
> >>> | awk '{ print $1 }' ) - 32769 )
> >
> > The Wande
On 2022-12-20 at 02:51, Thomas Schmitt wrote:
> Hi,
>
> i wrote:
>>> To obtain the offset of the first occurence of "CD001", do
>>>
>>> offst=$( expr \
>>> $( grep -a -o -b -m 1 CD001 cdimage.iso \
>>> | sed -e 's/:/ /' \
>>> | awk '{ print $1 }' )
which may be used with mount
option -o offset=.
I confirm that with this command I get the same result that what I had
done manually with hexdump. Unfortunately, mount still does not work
with "can't read superblock on /dev/loop0". Kernel logs say
"isofs_fill_super: get ro
-1 \
| sed -e 's/:/ /' \
| awk '{ print $1 }' ) - 32769 )
Afterwards $offst should hold a number > 0, which may be used with mount
option -o offset=.
---
About the occurences of CD001 in debian-11.5.0-amd64-netinst.iso :
32769:CD001 ...
On 2022-12-19 at 16:07, Thomas Schmitt wrote:
> Hi,
>
> Yvan Masson wrote:
>> I am really not at ease using tools like hexdump,
>
> I pondered a bit more. If it's an ISO filesystem wrapped into some header
> and maybe a footer, then mount option -o offset= could he
Hi,
Yvan Masson wrote:
> I am really not at ease using tools like hexdump,
I pondered a bit more. If it's an ISO filesystem wrapped into some header
and maybe a footer, then mount option -o offset= could help.
To obtain the offset of the first occurence of "CD001", d
bytes later is probably the Descriptor Set Terminator with
a leading byte of value 255: "\377CD001".
If they are displaced by the same offset as "\001CD001", then consider to
cut off the surplus bytes from the start of a copy of the image and try
to mount that shortened copy. At least
tes later is probably the Descriptor Set Terminator with
a leading byte of value 255: "\377CD001".
If they are displaced by the same offset as "\001CD001", then consider to
cut off the surplus bytes from the start of a copy of the image and try
to mount that shortened copy. At least
Le 19/12/2022 à 15:25, Kamil Jońca a écrit :
Yvan Masson writes:
Hi list,
I have a CD image of an old Win 95 game. I can mount it from dosbox
with the `imgmount` command (`imgmount D cdimage.iso -t iso`), but
could not mount it with Debian:
$ file cdimage.iso
cdimage.iso: data
$ sudo mount
Yvan Masson writes:
> Hi list,
>
> I have a CD image of an old Win 95 game. I can mount it from dosbox
> with the `imgmount` command (`imgmount D cdimage.iso -t iso`), but
> could not mount it with Debian:
>
> $ file cdimage.iso
> cdimage.iso: data
>
> $ sudo
Hi Thomas,
Le 19/12/2022 à 13:28, Thomas Schmitt a écrit :
Hi,
Yvan Masson wrote:
I have a CD image of an old Win 95 game. [...]
$ file cdimage.iso
cdimage.iso: data
So the cdimage.iso is not an ISO 9660 filesystem or somehow defaced.
(Does the image file perhaps begin by "RIFFCDXA" ?)
Hi,
Yvan Masson wrote:
> I have a CD image of an old Win 95 game. [...]
> $ file cdimage.iso
> cdimage.iso: data
So the cdimage.iso is not an ISO 9660 filesystem or somehow defaced.
(Does the image file perhaps begin by "RIFFCDXA" ?)
What do you get from the following runs ?
dd if=cdimage
Hi list,
I have a CD image of an old Win 95 game. I can mount it from dosbox with
the `imgmount` command (`imgmount D cdimage.iso -t iso`), but could not
mount it with Debian:
$ file cdimage.iso
cdimage.iso: data
$ sudo mount cdimage.iso /mnt -o loop
mount: /mnt/sshfs: wrong fs type, bad
On Tue, Oct 04, 2022 at 12:04:56PM +0100, tony wrote:
> I can successfully do (pls ignore spurious line break):
>
> mount -t nfs -o _netdev tony-fr:/mnt/sharedfolder
> /mnt/sharedfolder_client
>
> but the user id is incorrect.
What do you mean, "the user id"? A
Hi,
I need to mount a directory from a debian 11 server to a debian 10 client.
I can successfully do (pls ignore spurious line break):
mount -t nfs -o _netdev tony-fr:/mnt/sharedfolder
/mnt/sharedfolder_client
but the user id is incorrect. If I now try:
mount -t nfs -o _netdev,uid=1002 tony
Rock:
Hi,
I'm trying to bring up the Debian 10 root file system on an ARM SoC
board. When the rootfs was in an SD card the board worked well. When I
put the rootfs on an NFS server and tried to boot the board through NFS
mount, it reported error through serial port:
|[FAILED] Failed to
On Tue, Aug 16, 2022 at 04:20:36PM -0400, Greg Wooledge wrote:
> On Tue, Aug 16, 2022 at 03:58:30PM -0400, Lie Rock wrote:
> > So how is the process "create system users" performed when Linux/Debian
> > starts? What can be contributing to this error?
>
> unicorn:~$ grep -ri 'create system users' /
On Tue, Aug 16, 2022 at 03:58:30PM -0400, Lie Rock wrote:
> So how is the process "create system users" performed when Linux/Debian
> starts? What can be contributing to this error?
unicorn:~$ grep -ri 'create system users' /lib/systemd
/lib/systemd/system/systemd-sysusers.service:Description=Crea
Hi,
I'm trying to bring up the Debian 10 root file system on an ARM SoC board.
When the rootfs was in an SD card the board worked well. When I put the
rootfs on an NFS server and tried to boot the board through NFS mount, it
reported error through serial port:
[FAILED] Failed to start C
blkid and hwinfo are telling me
> > > and I know that that SSD is not sda or sdb, nor is it the DVD; so,
> > > what is it and how do I mount that SSD
> > > Isn't it weird that I don't see it on blkid or hwinfo? Could that
> > > possibly be some kind o
sdb, nor is it the DVD; so,
> > what is it and how do I mount that SSD
> > Isn't it weird that I don't see it on blkid or hwinfo? Could that
> > possibly be some kind of BIOS problem. I want to install Debian on
> > that box, but I want to make sure I can use the SSD.
&g
Albretch Mueller wrote:
> Sorry, for my late reaction. I'd wish I could dedicate myself to
> coding and reading only. This is what blkid and hwinfo are telling me
> and I know that that SSD is not sda or sdb, nor is it the DVD; so,
> what is it and how do I mount that SSD
>
Sorry, for my late reaction. I'd wish I could dedicate myself to
coding and reading only. This is what blkid and hwinfo are telling me
and I know that that SSD is not sda or sdb, nor is it the DVD; so,
what is it and how do I mount that SSD
Isn't it weird that I don't see it on
On 2022-07-27 15:20:19 -0500, Albretch Mueller wrote:
> https://wiki.debian.org/SSDOptimization
I'm wondering whether information is obsolete. At least for the
"Low-Latency IO-Scheduler" section, it talks about the cfq vs
deadline scheduler, but it seems that they no longer exist:
zira:~> cat /s
On 7/28/22 13:01, Nicolas George wrote:
gene heskett (12022-07-28):
gene@coyote:/var/log$ sudo sysctl -w
sysctl: no variables specified
Try `sysctl --help' for more information.
Have you tried reading the fine manual?
yes.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense
gene heskett (12022-07-28):
> gene@coyote:/var/log$ sudo sysctl -w
> sysctl: no variables specified
> Try `sysctl --help' for more information.
Have you tried reading the fine manual?
--
Nicolas George
t;
> debian bullseye, no reboot, takes 15+ minutes to get everything up and
> running after a reboot.
>
> What was I supposed to write?
>
> Thank Nic.
>
> Cheers, Gene Heskett.
> --
mount -a will work for any drive specified in /etc/fstab
All the very best,as ever,
A
On 7/28/22 05:24, Nicolas George wrote:
sudo syctl -w
A typu? Added an s...
gene@coyote:/var/log$ sudo sysctl -w
sysctl: no variables specified
Try `sysctl --help' for more information.
debian bullseye, no reboot, takes 15+ minutes to get everything up and
running after a reboot.
What was I
gene heskett (12022-07-28):
> > sudo vim /etc/sysctl.conf
> > kernel.dmesg_restrict=0
> Did that Nicolas, on bullseye still no perms w/o the sudo.
Did you reboot or have the corresponding service apply the change or do
the change manually (sudo syctl -w)?
Regards,
--
Nicolas George
On 7/27/22 13:06, Albretch Mueller wrote:
I googled: "mount solid state drive" Linux, and I got very few hits
(like 16?) which were mostly totally irrelevant.
I got a laptop with Windows installed on which I installed WSLg.
WIndows and WSLg both seem to detect the SSD just fine, b
On 7/28/22 03:26, David wrote:
On Thu, 28 Jul 2022 at 14:33, wrote:
On Wed, Jul 27, 2022 at 06:54:32PM -0400, Jude DaShiell wrote:
An easy way to locate an ssd is to have it unplugged from the system and
run lsblk and save that to a file then plug the ssd in and run lsblk again
saving its outp
a recap and this ought to be better.
lsblk >orig
# plug ssd in.
lsblk >new
comm -1 -3 -f orig new
On Thu, 28 Jul 2022, to...@tuxteam.de wrote:
> On Wed, Jul 27, 2022 at 03:06:47PM -0500, Albretch Mueller wrote:
> > I googled: "mount solid state drive" Linux, and I go
On 7/28/22 02:35, Nicolas George wrote:
to...@tuxteam.de (12022-07-28):
To add one to the toolbox: do "tail -f /var/log/messages" while plugging
in the device: you'll watch your OS pondering on what to do about it.
Or do "dmesg | tail" right away after having plugged it in. In both cases
you'll
1 - 100 of 1953 matches
Mail list logo
