Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #209886 > unrolled thread

Forgot name of Debian "configuration" {wrong word?} file

Back to article view | Back to linux.debian.user

Contents

  Forgot name of Debian "configuration" {wrong word?} file Richard Owlett <rowlett@cloud85.net> - 2019-06-14 13:20 +0200
    Re: Forgot name of Debian "configuration" {wrong word?} file john doe <johndoe65534@mail.com> - 2019-06-14 13:30 +0200
      Re: Forgot name of Debian "configuration" {wrong word?} file Richard Owlett <rowlett@cloud85.net> - 2019-06-14 13:50 +0200
    Re: Forgot name of Debian "configuration" {wrong word?} file Erwan David <erwan@rail.eu.org> - 2019-06-14 13:30 +0200
    Re: Forgot name of Debian "configuration" {wrong word?} file Erik Christiansen <dvalin@internode.on.net> - 2019-06-14 13:30 +0200
      Re: Forgot name of Debian "configuration" {wrong word?} file Richard Owlett <rowlett@cloud85.net> - 2019-06-14 14:00 +0200
        Re: Forgot name of Debian "configuration" {wrong word?} file Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-06-14 19:50 +0200
    Re: Forgot name of Debian "configuration" {wrong word?} file Jonas Smedegaard <jonas@jones.dk> - 2019-06-14 13:30 +0200
    Re: Forgot name of Debian "configuration" {wrong word?} file songbird <songbird@anthive.com> - 2019-06-14 14:40 +0200
    Re: Forgot name of Debian "configuration" {wrong word?} file Elimar Riesebieter <riesebie@lxtec.de> - 2019-06-14 18:10 +0200
    Re: Forgot name of Debian "configuration" {wrong word?} file Felix Miata <mrmazda@earthlink.net> - 2019-06-14 20:20 +0200
    Intended question - was {Re: Forgot name of Debian "configuration"  {wrong word?} file} Richard Owlett <rowlett@cloud85.net> - 2019-06-15 15:20 +0200
      Re: Intended question - was {Re: Forgot name of Debian  "configuration" {wrong word?} file} Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-06-15 16:30 +0200
        Re: Intended question Felix Miata <mrmazda@earthlink.net> - 2019-06-15 21:20 +0200
          Re: Intended question Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-06-15 21:30 +0200
        Re: Intended question - was {Re: Forgot name of Debian  "configuration" {wrong word?} file} Richard Owlett <rowlett@cloud85.net> - 2019-06-15 21:30 +0200
      Re: Intended question - was {Re: Forgot name of Debian  "configuration" {wrong word?} file} David Wright <deblis@lionunicorn.co.uk> - 2019-06-16 18:10 +0200
        Re: Intended question - was {Re: Forgot name of Debian  "configuration" {wrong word?} file} Richard Owlett <rowlett@cloud85.net> - 2019-06-16 21:20 +0200
          Re: Intended question - was {Re: Forgot name of Debian  "configuration" {wrong word?} file} john doe <johndoe65534@mail.com> - 2019-06-16 21:40 +0200
          Re: Intended question - was {Re: Forgot name of Debian  "configuration" {wrong word?} file} Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-06-17 00:30 +0200
          Re: Intended question - was {Re: Forgot name of Debian  "configuration" {wrong word?} file} David Wright <deblis@lionunicorn.co.uk> - 2019-06-17 04:10 +0200
            The use of VMs in experimentation schenarios (Was: Re: Intended          question - was...) Linux-Fan <Ma_Sys.ma@web.de> - 2019-06-17 23:00 +0200
              Re: The use of VMs in experimentation schenarios (Was: Re: Intended  question - was...) Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-06-17 23:10 +0200
            Re: Intended question - was {Re: Forgot name of Debian  "configuration" {wrong word?} file} Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-06-17 23:50 +0200
          Re: Intended question - was {Re: Forgot name of Debian  "configuration" {wrong word?} file} Felix Miata <mrmazda@earthlink.net> - 2019-06-17 05:00 +0200
            Re: Intended question - was {Re: Forgot name of Debian  "configuration" {wrong word?} file} Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-06-17 20:40 +0200
            Re: Intended question - was {Re: Forgot name of Debian  "configuration" {wrong word?} file} David Wright <deblis@lionunicorn.co.uk> - 2019-06-18 18:20 +0200
              Re: Intended question Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-06-20 20:10 +0200
                Re: Intended question David Wright <deblis@lionunicorn.co.uk> - 2019-06-21 04:40 +0200
    Bonus answers - was [Re: Forgot name of Debian "configuration" {wrong  word?} file] Richard Owlett <rowlett@cloud85.net> - 2019-06-15 15:40 +0200
      Re: Bonus answers - was [Re: Forgot name of Debian "configuration"  {wrong word?} file] songbird <songbird@anthive.com> - 2019-06-15 22:50 +0200
        Re: Bonus answers - was [Re: Forgot name of Debian "configuration"  {wrong word?} file] Richard Owlett <rowlett@cloud85.net> - 2019-06-16 11:50 +0200
      Re: Bonus answers - was [Re: Forgot name of Debian "configuration" {wrong word?} file] Jonas Smedegaard <jonas@jones.dk> - 2019-06-16 13:30 +0200
      Re: Bonus answers - was [Re: Forgot name of Debian "configuration"  {wrong word?} file] Dan Ritter <dsr@randomstring.org> - 2019-06-17 15:20 +0200

Page 2 of 2 — ← Prev page 1 [2]

#209971 — Re: Intended question - was {Re: Forgot name of Debian "configuration" {wrong word?} file}

On Sun 16 Jun 2019 at 14:17:21 (-0500), Richard Owlett wrote:
> On 06/16/2019 11:03 AM, David Wright wrote:
> > On Sat 15 Jun 2019 at 08:15:24 (-0500), Richard Owlett wrote:
> > > On 06/14/2019 06:10 AM, Richard Owlett wrote:
> > > > I can't remember the name of the file which identifies the
> > > > association between a directory (i.e. \home) and which physical
> > > > partition it is on. The file I'm looking for also identifies which
> > > > partition is used for swap.
> > > 
> > > The filename I had forgotten was /etc/fstab .
> > > 
> > > Background:
> > > I have one laptop explicitly set aside for experimenting with Debian
> > > in order to determine *MY* ideal system. To this end I may have a half
> > > dozen copies of Debian to chose from at boot.
> > > 
> > > For my purposes, the Debian installer has two annoyances:
> > >    1. swap area designation.
> > >       Everything is fine on the 1st installation.
> > >       On following installations, when the existing swap partition is
> > >       is to be used its UUID is changed. This causes grief for the
> > >       other installations by making swap area appear missing. My
> > >       personally preferred solution is to activate swap only of the
> > >       initial installation. For subsequent installs actually requiring
> > >       a swap partition, I edit its /etc/fstab .
> > 
> > It's rather easy to work around this problem in one of two ways (at least):
> 
> Ways on order of {# users}**N { N < world_population} ;/

Eh?

> >    With a reasonable amount of memory (not a problam nowadays), just tell
> >    the d-i to leave the existing swap file alone and do without one. Then
> >    manually add the old UUID into the new installation's /etc/fstab
> 
> *ROFL* !!!!
> Been doing that forever. However, had not done it recently.
> I had forgotten the filename was "/etc/fstab"  ;<

I'm surprised, then, that you haven't written a shell script for the
process, in view of the number of Debian installations you must have
performed over the years. (The script could also remember the filename
for you.)

> > and /etc/initramfs-tools/conf.d/resume when it's up and running.
> 
> Never hear of that file. Will research after sending this message.

It's just the file that's consulted in building the initramfs, which
tells the system where it was written to during hibernation.

> >    (If you're only installing as an experiment in installation,
> 
> I'm not experimenting with the installation process, but with what I
> want the result to be.

A Debian installation is produced by the installation process, so
what's your point? I'm assuming you're not a d-i developer who's
working on how the d-i actually goes about installing a system.

> > I suspect
> >    you won't even need to bother, because you'll be overwriting it shortly.
> >    Does  top  show much use of swap anyway?)
> 
> Not a parameter of my experiment's protocol.

I don't care. My point is that any reasonably endowed modern PC is
unlikely to do any swapping during your "installation/result
experiment" (whatever terminology you want to call it) as they have
so much memory. My old 500MB desktop doesn't, nor did its 384MB
predecessor (used from potato through squeeze).

> As I do not "know" how much swap space I require, I provide swap space
> based on conservative estimates of _typical_ requirements. That
> logically leads to my preference for a SINGLE large swap vs multiple
> small swap areas. *YMMV* !!!

But your use case isn't typical: you're talking about installing
systems that you said might not even boot, let alone do productive
work after installation. So zero is a reasonable size.

> > or, even easier,
> > 
> >    Use a LABEL to indicate the swap partition in all your own
> >    /etc/fstab files, eg:
> >    LABEL=swan10          none           swap        sw
> >    and in /etc/initramfs-tools/conf.d/resume.
> >    The d-i will of course overwrite the swap partition UUID/LABEL
> >    as usual, but it's trivial to reset your LABEL at the end.
> >    When the d-i reaches the UTC question at the end, switch to VC2
> >    and type (with the appropriate values):
> >      # /target/sbin/swaplabel -L LLLLLL /dev/sdXN
> >    before answering the UTC question. The newly installed system
> >    will boot via its fresh UUID, but all your old systems will
> >    carry on using your LABEL as usual. (I assume that if you're
> >    going to keep the new system for any length of time, you will
> >    be editing its /etc/fstab anyway, and can set your usual LABEL
> >    there, as in the example above.)
> 
> I can't parse that.

I don't see how you can install Debian several times a day and yet not
understand most of that. You must be intimately familiar with the d-i,
LABELs, UUIDs, getting a shell on VC2, the UTC clock question (ie about
the last occasion in the installation process when it's possible to
use VC2), /target, and /dev/sdXN device terminology. All that remains
is LLLLLL, which stands for whatever "acceptably unique" or "reasonably
unique" (terms you've used in the past) LABEL you might put on the
swap partition with swaplabel.
What specifically are you finding difficult to parse?

> > >    2. Grub configuration.
> > >       The installer is egotistical enough to think that what is being
> > >       installed will always be the preferred version. NOT!
> > 
> > You've been flogging this dead horse for at least seven years now.
> 
> Horse ain't dead.
> 
> > Common sense dictates that anyone installing a new system wants it
> > to boot up by default.
> 
> You have neglected to *GROK* my goals ;/
> Some of my experiments are un-bootable.

And the authors of the d-i and Grub couldn't care in the least
about your experiments or your goals. Besides, how are those authors
meant to recognise people like you, guess their preferred default
disk, partition etc, when presented with any particular system?
How would they know whether the method that's been used for booting
up until now is capable of booting the new system being installed?
And if their guesses were incorrect, they'd be accused of installing
broken systems that won't boot. Get a grip.

> > Anything else would be like sending the final
> > copy of your magnum opus to the publisher only for them to distribute
> > an old draft. OSes aren't like marmalade, where you have to use up
> > the old jar before opening a new one.
> > 
> > >       My solution is install Grub only on the initial install and NO
> > >       boot loader on subsequent install. After completing one (or more)
> > >       additional installs, I boot the first install and run update-grub.
> > > 
> > > VM's had been suggested ;}
> > 
> > What for; to avoid having to type <down><down><down><return> when booting?
> 
> No

Then what *would* be the benefit of a VM? Why did you bring it up
in this thread?

> require my failures to be deterministic !!!!!!!!!!!!!!!!!!!!!
> 
> VM's are intrinsically unknown quantities.

I wouldn't know. I've never set one up.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#210007 — The use of VMs in experimentation schenarios (Was: Re: Intended question - was...)

[Multipart message — attachments visible in raw view] — view raw

David Wright writes:

> On Sun 16 Jun 2019 at 14:17:21 (-0500), Richard Owlett wrote:
> > On 06/16/2019 11:03 AM, David Wright wrote:
> > > On Sat 15 Jun 2019 at 08:15:24 (-0500), Richard Owlett wrote:
> > > > On 06/14/2019 06:10 AM, Richard Owlett wrote:

[...]

> > > >       My solution is install Grub only on the initial install and NO
> > > >       boot loader on subsequent install. After completing one (or more)
> > > >       additional installs, I boot the first install and run update-grub.
> > > >
> > > > VM's had been suggested ;}
> > >
> > > What for; to avoid having to type <down><down><down><return> when booting?
> >
> > No
>
> Then what *would* be the benefit of a VM? Why did you bring it up
> in this thread?
>
> > require my failures to be deterministic !!!!!!!!!!!!!!!!!!!!!
> >
> > VM's are intrinsically unknown quantities.

[...]

Just a few benefits of VMs I can think of here:

 * Do multiple installs simulateneously.

 * Use the same machine to read manuals, mailing list or whatever
   while at the same time running an install.

 * No need to worry about the other installations in terms of
   (1) storage management: all installations get their own individual
   partition table inside an image file and
   (2) bootloader management: all installations see only their own
   data, there is no unwanted interaction between any of the installations.

 * Historically, VMs were sometimes emulated and thus slower than operating
   a system "bare-metal". On my systems, installations in VMs are often
   faster than installations on the machine directly because they can make
   use of caching (e.g. for installation media which need not be provided as
   physical media but can be image files as well), libvirt has its own DHCP
   to provide IP addresses quickly etc. such that systems inside it respond
   faster to certain installation tasks like getting an IP address over DHCP.

 * Snapshots can be used to save and revert any state of a VM which is
   perfectly well-suited for doing experiments and reverting to a
   "known good" state later if only to refine the experiment and run
   it again. This may save the time of doing an installation repeatedly
   in some cases.

 * VM management software allows all VMs to be named individually which
   may be an improvement over a lot of similar bootloader entries.

 * Deleting installations is very easy and does in no way interact with
   other existing installations (no need to update bootloader entries).
   Also, followup installations in VMs are not restricted by the partition
   layout from previous installations but each installation is only limited
   by amount of available disk space.

 * Different exclusive technology like partitioning schemes (GPT/MBR) or
   LVM may be used on some and not necessarily all of the installations
   without issues. In case of physical installations, experimenting with
   GPT+MBR at the same time is very difficult or requires multiple hard drives.

Other ideas
 * https://www.makeuseof.com/tag/reasons-start-using-virtual-machine/
 * https://www.quora.com/What-are-the-benefits-of-VM-Virtual-Machines

Btw. at least one of the links recommends VirtualBox. I would rather prefer
Virt-Manager + KVM (see
https://masysma.lima-city.de/37/how_to_transition_from_virtualbox_to_kvm.xhtml
for reasons).

HTH
Linux-Fan

[toc] | [prev] | [next] | [standalone]

#210009 — Re: The use of VMs in experimentation schenarios (Was: Re: Intended question - was...)

[Multipart message — attachments visible in raw view] — view raw

On Mon, Jun 17, 2019 at 3:57 PM Linux-Fan <Ma_Sys.ma@web.de> wrote:

>
> Just a few benefits of VMs I can think of here:
> .....
>  * Historically, VMs were sometimes emulated and thus slower than operating
>    a system "bare-metal". On my systems, installations in VMs are often
>    faster than installations on the machine directly because they can make
>    use of caching (e.g. for installation media which need not be provided
> as
>    physical media but can be image files as well), libvirt has its own DHCP
>    to provide IP addresses quickly etc. such that systems inside it respond
>    faster to certain installation tasks like getting an IP address over
> DHCP.
>

We should mention the various virtualization hardware assists built-into
Intel and AMD CPUs
which allow VMs to run with near-native performance. Not to mention the
assistive code in
the linux kernel itself eg. TLB, etc. These technologies were available
beginning in the early
1960s (Atlas) and especially after 1965 (OS/360) and again after 1970 (MVS
and VM/370) in
the IBM mainframe universe.


> HTH
> Linux-Fan
>

[toc] | [prev] | [next] | [standalone]

#210010 — Re: Intended question - was {Re: Forgot name of Debian "configuration" {wrong word?} file}

[Multipart message — attachments visible in raw view] — view raw

On Sun, Jun 16, 2019 at 9:06 PM David Wright <deblis@lionunicorn.co.uk>
wrote:

> On Sun 16 Jun 2019 at 14:17:21 (-0500), Richard Owlett wrote:
>
> > > It's rather easy to work around this problem in one of two ways (at
> least):
> >
> > Ways on order of {# users}**N { N < world_population} ;/
>
> Eh?
>

He's claiming that his needs are the same as the rest of humanity to the
n-th power.
....

> > I suspect
> > >    you won't even need to bother, because you'll be overwriting it
> shortly.
> > >    Does  top  show much use of swap anyway?)
> >
> > Not a parameter of my experiment's protocol.
>
> I don't care. My point is that any reasonably endowed modern PC is
> unlikely to do any swapping during your "installation/result
> experiment" (whatever terminology you want to call it) as they have
> so much memory. My old 500MB desktop doesn't, nor did its 384MB
> predecessor (used from potato through squeeze).
>
> > As I do not "know" how much swap space I require, I provide swap space
> > based on conservative estimates of _typical_ requirements. That
> > logically leads to my preference for a SINGLE large swap vs multiple
> > small swap areas. *YMMV* !!!
>

I'll pass David on the left here ;-)
Knoppix proved years ago that you can run the whole damn thing out of RAM
back when 512K was big.
In datacenters in recent years, if a server is swapping, a problem ticket
is opened and alarm raised. Just because
the OS can handle it easily, nevertheless it's still a negative indicator.
I just took possession of a free used Dell
PowerEdge R610 for home, retiring after 5 years hard time in chilled rooms.
It has 96GB RAM. I could run NASA out of that much RAM ;-)


>
> Cheers,
> David.
>

[toc] | [prev] | [next] | [standalone]

#209973 — Re: Intended question - was {Re: Forgot name of Debian "configuration" {wrong word?} file}

Richard Owlett composed on 2019-06-16 14:17 (UTC-0500):

> David Wright wrote:

>> or, even easier,
 
>>    Use a LABEL to indicate the swap partition in all your own
...> I can't parse that.
 
I recommend learning to use LABELs on all your filesystems. They are massively
easier for humans to work with than UUIDs. You get to assign them in accordance
with how your brain functions, e.g.:

# <file system> 	<mount point>   <type>  <options>			<dump> <pass>
LABEL=m12P01esp 	/boot/efi	vfat	codepage=437			0 0
LABEL=m12p02swap		swap	swap	defaults			0 0
LABEL=m12p03usrlcl	/usr/local	ext4	noatime,data=ordered		0 2
LABEL=m12p04home	/home		ext4	noatime,acl,user_xattr,data=ordered 0 2
LABEL=m12p05stw		/disks/stw	ext4	noatime,acl,user_xattr,nofail	0 0
LABEL=m12p06s150	/disks/s150	ext4	noatime,acl,user_xattr,nofail	0 0
LABEL=m12p07s151	/disks/s151	ext4	noatime,acl,user_xattr,nofail	0 0
LABEL=m12p08deb10		/	ext4	noatime,errors=remount-ro	0 1
LABEL=m12p09Ubionic	/disks/buntu	ext4	noatime,acl,user_xattr,nofail	0 0
LABEL=m12p10mint19	/disks/mint	ext4	noatime,acl,user_xattr,nofail	0 0

In case you're wondering about the above naming logic, m12 is simply the last
three characters of the disk's serial number, something to reduce possibility
of label duplication when swapping disks around, or cloning.

Labeling makes output lines in blkid longer, but that enables making parsing much
easier for most human brains. Labels can be especially helpful with multiboot in
constructing custom boot stanzas much shorter and more easily parsable compared
to those generated by grub-mkconfig, e.g.:

menuentry "Debian 10 Buster" {
	search --no-floppy --set=root --hint-baremetal=ahci0,gpt8 --label m12p08deb10
	linux	/vmlinuz root=LABEL=m12p08deb10 noresume
	initrd	/initrd.img
}

The exercise might even make the string /etc/fstab more memorable. :-D
-- 
Evolution as taught in public schools is religion, not science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#209999 — Re: Intended question - was {Re: Forgot name of Debian "configuration" {wrong word?} file}

Le 17/06/2019 à 04:50, Felix Miata a écrit :
>   
> I recommend learning to use LABELs on all your filesystems. They are massively
> easier for humans to work with than UUIDs. You get to assign them in accordance
> with how your brain functions, e.g.:
> 
> # <file system> 	<mount point>   <type>  <options>			<dump> <pass>
> LABEL=m12P01esp 	/boot/efi	vfat	codepage=437			0 0
> LABEL=m12p02swap		swap	swap	defaults			0 0
> LABEL=m12p03usrlcl	/usr/local	ext4	noatime,data=ordered		0 2
(...)
> In case you're wondering about the above naming logic, m12 is simply the last
> three characters of the disk's serial number, something to reduce possibility
> of label duplication when swapping disks around, or cloning.

Adding a prefix or suffix to avoid label collisions is a good practice. 
However IMO a label should be associated to the contents, not to the 
container (disk or partition) at least on fixed disks. I do not care 
that a given filesystem is in partition X on disk Y, all that matters to 
me is that it contains the home directory for system 'foo' (for 
instance) -> foo_home.

[toc] | [prev] | [next] | [standalone]

#210056 — Re: Intended question - was {Re: Forgot name of Debian "configuration" {wrong word?} file}

On Sun 16 Jun 2019 at 22:50:28 (-0400), Felix Miata wrote:
> Richard Owlett composed on 2019-06-16 14:17 (UTC-0500):
> > David Wright wrote:
> 
> >> or, even easier,
>  
> >>    Use a LABEL to indicate the swap partition in all your own
> ...> I can't parse that.
>  
> I recommend learning to use LABELs on all your filesystems. They are massively
> easier for humans to work with than UUIDs. You get to assign them in accordance
> with how your brain functions, e.g.:

That's right.

[…]

> In case you're wondering about the above naming logic, m12 is simply the last
> three characters of the disk's serial number, something to reduce possibility
> of label duplication when swapping disks around, or cloning.

I write permanent 4-letter names on my disks with a marker
pen. Computers too. The partitions are just 2-digit suffixes.
Names makes it easier to remember that PC wasp contains
disks faye and chad, for example.

> Labeling makes output lines in blkid longer, but that enables making parsing much
> easier for most human brains. Labels can be especially helpful with multiboot in
> constructing custom boot stanzas much shorter and more easily parsable compared
> to those generated by grub-mkconfig, e.g.:
> 
> menuentry "Debian 10 Buster" {
> 	search --no-floppy --set=root --hint-baremetal=ahci0,gpt8 --label m12p08deb10
> 	linux	/vmlinuz root=LABEL=m12p08deb10 noresume
> 	initrd	/initrd.img
> }

Thanks for the example. It's long been a disappointment that
there's no   GRUB_DISABLE_LINUX_LABEL=true   parameter in
/etc/default/grub. For years I've post-processed grub.cfg
with a shell script to replace the UUIDs with LABELs by
using data from /run/udev/data/b* (and making a few other
tweaks). But I can see I ought to be doing more pruning.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#210151 — Re: Intended question

Le 18/06/2019 à 18:15, David Wright a écrit :
> 
> It's long been a disappointment that there's no
> GRUB_DISABLE_LINUX_LABEL=true parameter in /etc/default/grub.

What for ? grub-mkconfig does not use LABELs by defaut, so there is no 
need to disable them. I wish there was a way to tell grub-mkconfig to 
use LABELs, PARTUUIDs or PARTLABELs, not only in the linux root 
parameter but also in search commands.

[toc] | [prev] | [next] | [standalone]

#210174 — Re: Intended question

On Thu 20 Jun 2019 at 20:01:39 (+0200), Pascal Hambourg wrote:
> Le 18/06/2019 à 18:15, David Wright a écrit :
> > 
> > It's long been a disappointment that there's no
> > GRUB_DISABLE_LINUX_LABEL=true parameter in /etc/default/grub.
> 
> What for ? grub-mkconfig does not use LABELs by defaut, so there is no
> need to disable them. I wish there was a way to tell grub-mkconfig to
> use LABELs, PARTUUIDs or PARTLABELs, not only in the linux root
> parameter but also in search commands.

Well spotted; I did of course mean GRUB_ENABLE_LINUX_LABEL=true.
I edited the line from UUID to LABEL (as that was the subject)
but overlooked changing DIS→EN.
Happy that you are in agreement.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#209933 — Bonus answers - was [Re: Forgot name of Debian "configuration" {wrong word?} file]

On 06/14/2019 06:10 AM, Richard Owlett wrote:
> I can't remember the name of the file which identifies the association 
> between a directory (i.e. \home) and which physical partition it is on. 
> The file I'm looking for also identifies which partition is used for swap.
> 
> TIA
> 

I was looking for /etc/fstab .

Suggestions were made for tools such as df, mount, and inxi used in an 
analytic mode. I either ran them or looked up relevant documentation.

If I had been looking for information one of them could provide, is 
there a URL that attempts to summarize such tools?

[toc] | [prev] | [next] | [standalone]

#209956 — Re: Bonus answers - was [Re: Forgot name of Debian "configuration" {wrong word?} file]

Richard Owlett wrote:
...
> If I had been looking for information one of them could provide, is 
> there a URL that attempts to summarize such tools?

  i go in roughly this order.

command line:
  man -k keyword
  apt-cache search keyword

browser:
  google linux keyword


  songbird

[toc] | [prev] | [next] | [standalone]

#209957 — Re: Bonus answers - was [Re: Forgot name of Debian "configuration" {wrong word?} file]

On 06/15/2019 11:55 AM, songbird wrote:
> Richard Owlett wrote:
> ...
>> If I had been looking for information one of them could provide, is
>> there a URL that attempts to summarize such tools?
> 
>    i go in roughly this order.
> 
> command line:
>    man -k keyword
>    apt-cache search keyword
> 
> browser:
>    google linux keyword
> 
> 
>    songbird
> 

You had snipped context. I had said:
"... for *tools such as* df, mount, and inxi used in an analytic mode."
and then:
"... is there a URL that attempts to summarize *such tools* ?"

I was looking for a functional index of tools. Your suggestion works 
only if I already know which tool can do the job.

[toc] | [prev] | [next] | [standalone]

#209959 — Re: Bonus answers - was [Re: Forgot name of Debian "configuration" {wrong word?} file]

[Multipart message — attachments visible in raw view] — view raw

Quoting Richard Owlett (2019-06-15 15:33:37)
> On 06/14/2019 06:10 AM, Richard Owlett wrote:
> > I can't remember the name of the file which identifies the 
> > association between a directory (i.e. \home) and which physical 
> > partition it is on. The file I'm looking for also identifies which 
> > partition is used for swap.
> > 
> > TIA
> > 
> 
> I was looking for /etc/fstab .
> 
> Suggestions were made for tools such as df, mount, and inxi used in an 
> analytic mode. I either ran them or looked up relevant documentation.
> 
> If I had been looking for information one of them could provide, is 
> there a URL that attempts to summarize such tools?

You mentioned "directory", "partition", and "swap".

You could use only man-related tools.  Tedious, but possible:

  apropos swap

...lists "mkswap", "swaplabel", "swapoff" and "swapon", among others

  man swapon

...mentions /etc/fstab in its "See also" section (and man pages of other 
commands mention swapon in their "See also" section).


I would probably have given up before reaching to a sensible result, and 
instead tried a search on https://DuckDuckGo.com/


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

[toc] | [prev] | [next] | [standalone]

#209980 — Re: Bonus answers - was [Re: Forgot name of Debian "configuration" {wrong word?} file]

Richard Owlett wrote: 
> On 06/14/2019 06:10 AM, Richard Owlett wrote:
> > I can't remember the name of the file which identifies the association
> > between a directory (i.e. \home) and which physical partition it is on.
> > The file I'm looking for also identifies which partition is used for
> > swap.
> > 
> > TIA
> > 
> 
> I was looking for /etc/fstab .
> 
> Suggestions were made for tools such as df, mount, and inxi used in an
> analytic mode. I either ran them or looked up relevant documentation.
> 
> If I had been looking for information one of them could provide, is there a
> URL that attempts to summarize such tools?

Have you read the Debian Administrator's Handbook?

https://debian-handbook.info/

https://www.debian.org/doc/manuals/debian-handbook/

While the currently published version is accurate for Jessie/8,
it's a good place to start looking. I understand that it's being
updated for Buster.

-dsr-

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web