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

Groups > alt.os.linux.slackware > #34151 > unrolled thread

How do *you* install Slackware

Back to article view | Back to alt.os.linux.slackware

Contents

  How do *you* install Slackware Joseph Rosevear <Mail@JoesLife.org> - 2023-03-14 08:54 +0000
    Re: How do *you* install Slackware David Robley <david@me.invalid> - 2023-03-14 20:30 +1030
      Re: How do *you* install Slackware John Forkosh <ian@moone.com> - 2023-03-14 11:32 +0000
        Re: How do *you* install Slackware Joseph Rosevear <Mail@JoesLife.org> - 2023-03-14 22:39 +0000
          Re: How do *you* install Slackware Jimmy Johnson <Jimmy@disposable.invalid> - 2023-03-14 22:33 -0700
    Re: How do *you* install Slackware Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-03-14 14:28 +0000
      Re: How do *you* install Slackware Jim Diamond <JimDiamond@ns.sympatico.ca> - 2023-03-14 11:58 -0300
        Re: How do *you* install Slackware Rich <rich@example.invalid> - 2023-03-14 19:11 +0000
        Re: How do *you* install Slackware Mike Spencer <mds@bogus.nodomain.nowhere> - 2023-03-15 01:19 -0300
          Re: How do *you* install Slackware Jim Diamond <JimDiamond@jdvb.ca> - 2023-03-17 17:14 -0300
            Re: How do *you* install Slackware Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-03-18 10:37 +0000
            Re: How do *you* install Slackware Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-03-18 16:06 +0000
              Re: How do *you* install Slackware Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-03-18 17:39 +0000
              Re: How do *you* install Slackware Jim Diamond <JimDiamond@jdvb.ca> - 2023-03-20 16:09 -0300
                Re: How do *you* install Slackware Rich <rich@example.invalid> - 2023-03-20 22:00 +0000
                  Re: How do *you* install Slackware Jim Diamond <JimDiamond@jdvb.ca> - 2023-03-22 17:47 -0300
                    Re: How do *you* install Slackware Jimmy Johnson <Jimmy@disposable.invalid> - 2023-03-22 18:20 -0700
                      Re: How do *you* install Slackware Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-03-23 06:44 +0000
                      Re: How do *you* install Slackware Jim Diamond <JimDiamond@jdvb.ca> - 2023-03-25 15:37 -0300
                        Re: How do *you* install Slackware Jimmy Johnson <Jimmy@disposable.invalid> - 2023-03-25 15:24 -0700
                          Re: How do *you* install Slackware Rich <rich@example.invalid> - 2023-03-26 04:21 +0000
                            Re: How do *you* install Slackware Jimmy Johnson <Jimmy@disposable.invalid> - 2023-03-25 23:18 -0700
                              Re: How do *you* install Slackware Rich <rich@example.invalid> - 2023-03-26 15:50 +0000
                Re: How do *you* install Slackware Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2023-03-20 22:39 +0000
                  Re: How do *you* install Slackware Jim Diamond <JimDiamond@jdvb.ca> - 2023-03-22 17:42 -0300
                Re: How do *you* install Slackware republicanismiscancer@tutanota.com (TronNerd82) - 2024-12-16 01:30 +0000
                  Re: How do *you* install Slackware Gilberto F da Silva <gfs1989@gmx.net> - 2026-07-30 18:17 +0000
                    Re: How do *you* install Slackware Joseph Rosevear <Mail@JoesLife.org> - 2026-08-03 06:19 +0000
                      Re: How do *you* install Slackware jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-08-03 11:19 -0400
    Re: How do *you* install Slackware Rich <rich@example.invalid> - 2023-03-14 14:57 +0000
    Re: How do *you* install Slackware Silvenshadow <bogus@mail.com> - 2023-03-14 10:21 -0700
    Re: How do *you* install Slackware Dan C <youmustbejoking@lan.invalid> - 2023-03-14 17:34 +0000
      Re: How do *you* install Slackware Joseph Rosevear <Mail@JoesLife.org> - 2023-03-14 22:24 +0000
    Re: How do *you* install Slackware Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-03-15 06:36 +0000
    Re: How do *you* install Slackware bad sector <forgetski@INVALID.net> - 2023-03-15 08:16 -0400
      Re: How do *you* install Slackware Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-03-16 06:45 +0000
        Re: How do *you* install Slackware Martin Schöön <martin.schoon@gmail.com> - 2023-03-16 20:40 +0000
          Re: How do *you* install Slackware Martin Schöön <martin.schoon@gmail.com> - 2023-04-08 09:43 +0000
            Re: How do *you* install Slackware maus@smaus.org - 2023-04-08 11:47 +0000
              Re: How do *you* install Slackware noel <deletethis@invalid.lan> - 2023-04-08 23:05 +1000
                Re: How do *you* install Slackware maus@smaus.org - 2023-04-08 14:40 +0000
                  Re: How do *you* install Slackware Rich <rich@example.invalid> - 2023-04-08 14:48 +0000
                    Re: How do *you* install Slackware noel <deletethis@invalid.lan> - 2023-04-14 22:10 +1000
                      Re: How do *you* install Slackware Rich <rich@example.invalid> - 2023-04-14 13:04 +0000
                        Re: How do *you* install Slackware maus <maus@dmany.org> - 2023-04-14 13:21 +0000
                          Re: How do *you* install Slackware noel <deletethis@invalid.lan> - 2023-05-21 18:02 +1000
                        Re: How do *you* install Slackware noel <deletethis@invalid.lan> - 2023-05-21 17:47 +1000
                  Re: How do *you* install Slackware noel <deletethis@invalid.lan> - 2023-04-14 21:59 +1000
                    Re: How do *you* install Slackware Ferannia <ferannia@invalid.com> - 2023-06-06 12:17 -0700
                      Re: How do *you* install Slackware Ted Heise <theise@panix.com> - 2023-06-06 19:40 +0000
                        Re: How do *you* install Slackware Ferannia <ferannia@invalid.com> - 2023-06-06 13:01 -0700
                          Re: How do *you* install Slackware Ted Heise <theise@panix.com> - 2023-06-07 01:10 +0000
                    Re: How do *you* install Slackware bad sector <forgetski@_INVALID.net> - 2023-06-07 01:22 -0400
                      Re: How do *you* install Slackware slash <slash@invalid.invalid> - 2023-06-07 16:34 +0200
                        Re: How do *you* install Slackware bad sector <forgetski@invalid.org> - 2023-06-07 15:55 +0000
                          Re: How do *you* install Slackware slash <slash@invalid.invalid> - 2023-06-08 11:33 +0200
                            Re: {OT} How do *you* install Slackware bad sector <forgetski@_INVALID.net> - 2023-06-08 06:49 -0400
                              Re: {OT} How do *you* install Slackware slash <slash@invalid.invalid> - 2023-06-09 15:58 +0200
                                Re: {OT} How do *you* install Slackware bad sector <forgetski@_INVALID.net> - 2023-06-09 20:23 -0400
                                  Re: {OT} How do *you* install Slackware noel <deletethis@invalid.lan> - 2023-06-10 13:15 +1000
                                    Re: {OT} How do *you* install Slackware bad sector <forgetski@INVALID.net> - 2023-06-10 13:22 -0400
                                      Re: {OT} How do *you* install Slackware noel <deletethis@invalid.lan> - 2023-06-11 18:49 +1000
                                  Re: {OT} How do *you* install Slackware Erte Ribbile <erteribbile@sfracel.li> - 2023-06-12 08:17 +0200
                                    Re: {OT} How do *you* install Slackware bad sector <nomail@_invalid.nos.pam> - 2023-06-12 05:33 -0400
              Re: How do *you* install Slackware bad sector <forgetski@INVALID.net> - 2023-06-02 17:49 -0400
            Re: How do *you* install Slackware Martin Schöön <martin.schoon@gmail.com> - 2023-06-13 20:49 +0000
        Re: How do *you* install Slackware bad sector <forgetski@INVALID.net> - 2023-03-16 20:12 -0400
    Re: How do *you* install Slackware Peter 'Shaggy' Haywood <phaywood@alphalink.com.au> - 2023-03-16 09:57 +1100
    Re: How do *you* install Slackware "K. Venken" <karel.venken@domain.invalid> - 2023-03-16 16:37 +0100
    Re: How do *you* install Slackware Sylvain Robitaille <syl@therockgarden.ca> - 2023-05-01 06:07 +0000
      Re: How do *you* install Slackware Joseph Rosevear <Mail@JoesLife.org> - 2023-07-01 13:59 +0000
        Re: How do *you* install Slackware Sylvain Robitaille <syl@alcor.concordia.ca> - 2024-03-22 01:12 +0000
          Re: How do *you* install Slackware Joseph Rosevear <Mail@JoesLife.org> - 2024-03-26 06:14 +0000
            Re: How do *you* install Slackware "Auric__" <not.my.real@email.address> - 2024-03-27 18:26 +0000
              Re: How do *you* install Slackware Sam <sam@email-scan.com> - 2024-03-27 17:40 -0400
            Re: How do *you* install Slackware Sylvain Robitaille <syl@therockgarden.ca> - 2024-03-27 21:12 +0000
              Re: How do *you* install Slackware Joseph Rosevear <Mail@JoesLife.org> - 2024-03-29 20:27 +0000
                Re: How do *you* install Slackware Sylvain Robitaille <syl@therockgarden.ca> - 2024-03-29 23:40 +0000
                  Re: How do *you* install Slackware Luis Mendes <luisXXXlupeXXX@gmail.com> - 2024-04-15 20:27 +0000
                    Re: How do *you* install Slackware Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2024-04-16 05:49 +0000
                      Re: How do *you* install Slackware Luis Mendes <luisXXXlupeXXX@gmail.com> - 2024-04-16 18:08 +0000
                    Re: How do *you* install Slackware Sylvain Robitaille <syl@therockgarden.ca> - 2024-04-19 12:18 +0000
                      Re: How do *you* install Slackware The Real Bev <bashley101@gmail.com> - 2024-04-19 14:56 -0700
                        Re: How do *you* install Slackware Sylvain Robitaille <syl@therockgarden.ca> - 2024-04-21 14:34 +0000
                          Re: How do *you* install Slackware The Real Bev <bashley101@gmail.com> - 2024-04-21 08:50 -0700

Page 1 of 5  [1] 2 3 4 5  Next page →

#34151 — How do *you* install Slackware

OK, this is a survey.  Pick all that apply:

   1.  I download the CD iso images, burn them to CDs, boot the first CD, 
and install.

   2.  Same as above, but download a single DVD iso image and burn to a 
DVD.

   3.  I download the CD iso images and use them directly, booting the 
first image using Grub.

   4.  Same as above, but download a single DVD iso image.

   5.  I clone an existing installation using rsync, then modify it as 
needed using patches and scripts.

   6.  I never install, I upgrade.

   7.  Some other way.

[toc] | [next] | [standalone]

#34152

On 14/03/2023 19:24, Joseph Rosevear wrote:
> OK, this is a survey.  Pick all that apply:
> 
>     1.  I download the CD iso images, burn them to CDs, boot the first CD,
> and install.
> 
>     2.  Same as above, but download a single DVD iso image and burn to a
> DVD.
> 
>     3.  I download the CD iso images and use them directly, booting the
> first image using Grub.
> 
>     4.  Same as above, but download a single DVD iso image.
> 
>     5.  I clone an existing installation using rsync, then modify it as
> needed using patches and scripts.
> 
>     6.  I never install, I upgrade.
> 
>     7.  Some other way.

7 - where 7 involves a bootable external device.

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

#34153

David Robley <david@me.invalid> wrote:
> On 14/03/2023 19:24, Joseph Rosevear wrote:
>> OK, this is a survey.  Pick all that apply:
>> 
>>   1. I download the CD iso images, burn them to CDs,
>>      boot the first CD, and install.
>>   2. Same as above, but download a single DVD iso image
>>      and burn to a DVD.
>>   3. I download the CD iso images and use them directly,
>>      booting the first image using Grub.
>>   4. Same as above, but download a single DVD iso image.
>>   5. I clone an existing installation using rsync,
>>      then modify it as needed using patches and scripts.
>>   6. I never install, I upgrade.
>>   7. Some other way.
> 
>    7. where 7 involves a bootable external device.
>       David Robley

     7. (a) copy the entire slackware directory, i.e.,
            rsync -av --delete \
             rsync://mirrors.kernel.org/slackware/slackware64-current/ \
             slackware64-mylocalcopy/
        (b) use  usb-and-pxe-installers/usbimg2disk.sh  to create
            a bootable install stick

For what purpose(s) are you taking a "survey"?
-- 
John Forkosh  ( mailto:  j@f.com  where j=john and f=forkosh )

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

#34161

On Tue, 14 Mar 2023 11:32:08 -0000 (UTC), John Forkosh wrote:

> David Robley <david@me.invalid> wrote:
>> On 14/03/2023 19:24, Joseph Rosevear wrote:
>>> OK, this is a survey.  Pick all that apply:
>>> 
>>>   1. I download the CD iso images, burn them to CDs,
>>>      boot the first CD, and install.
>>>   2. Same as above, but download a single DVD iso image
>>>      and burn to a DVD.
>>>   3. I download the CD iso images and use them directly,
>>>      booting the first image using Grub.
>>>   4. Same as above, but download a single DVD iso image.
>>>   5. I clone an existing installation using rsync,
>>>      then modify it as needed using patches and scripts.
>>>   6. I never install, I upgrade.
>>>   7. Some other way.
>> 
>>    7. where 7 involves a bootable external device.
>>       David Robley
> 
>      7. (a) copy the entire slackware directory, i.e.,
>             rsync -av --delete \
>              rsync://mirrors.kernel.org/slackware/slackware64-current/ \
>              slackware64-mylocalcopy/
>         (b) use  usb-and-pxe-installers/usbimg2disk.sh  to create
>             a bootable install stick
> 
> For what purpose(s) are you taking a "survey"?

There is no formality to this--sorry if it sounded otherwise.  I'm just 
curious, and I thought it would be a good conversation starter.

I used to use method 1.  Now I use 3 and 5.  I wondered if I was alone in 
my methodology or if I had company.  It sounds like I have company, but 
there is more variation than I expected.

I was reading the Slackware FAQ last night.  One of the questions in it 
is about installing via FTP.  The answer given doesn't tell the whole 
story.  No you can't install via FTP, but you can download iso files via 
ftp, then boot and install without burning a disk. Therefore, it seems to 
me that the responses to this survey could be useful information to new 
and seasoned users.

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

#34163

On 03/14/2023 03:39 PM, Joseph Rosevear wrote:
> Therefore, it seems to
> me that the responses to this survey could be useful information to new
> and seasoned users.

Okay:

!. Get a USB flash drive that can hold the Slackware.iso
Using Gparted make a DOS partition table on the USB flash drive, format 
it fat32 and make boot flag.

2. Open file manager where the down loaded slackware.iso is and Ctrl+F4 
to open console where the .iso is, now # md5sum slackware.iso to check 
the md5sum

3. Put USB flash drive into computer and # fdisk -l to get name of the 
"unmounted" USB flash drive

4. dd bs=4M if=slackware.iso of=/dev/sdb
In the above use the real name of the .iso and the real name of the 
flash drive, don't mess up the spacing and hit the enter key

5. Make sure your BIOS is set to boot the USB drive, boot flash drive 
and install Slackware. As long as the USB flash drive is not corrupted 
you can reuse it.
-- 
Jimmy Johnson

Slackware64 Current - AMD A8-7600 at sda7
Registered Linux User #380263

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

#34154

On Tue, 14 Mar 2023 08:54:18 +0000, Joseph Rosevear wrote:

> OK, this is a survey.  Pick all that apply:
> 
>    1.  I download the CD iso images, burn them to CDs, boot the first CD, 
> and install.
> 
>    2.  Same as above, but download a single DVD iso image and burn to a 
> DVD.
> 
>    3.  I download the CD iso images and use them directly, booting the 
> first image using Grub.
> 
>    4.  Same as above, but download a single DVD iso image.
> 
>    5.  I clone an existing installation using rsync, then modify it as 
> needed using patches and scripts.
> 
>    6.  I never install, I upgrade.
> 
>    7.  Some other way.

These days, when I install a new Slackware system to bare metal, I 
#2 Download the DVD iso image and burn it to a DVD (or other suitable
media). I also keep the iso as a file on one of my systems, to be NFS
shared and loop-mounted, so that I can either netboot from that iso,
or can mount and extract components (like single packages) from it.

For my existing Slackware systems, I /upgrade/ from the downloaded
iso. First, I drop into single-user, then I mount the iso (or DVD)
and start upgrading packages as per Slackware's instructions in
UPGRADE.TXT. (FWIW, before I upgradepkg, I run a set of scripts that
tell me which existing packages are absent from the upgrade, which
are present but unchanged, or present with upgrade path, and which
are new to the upgrade. I plan my upgrade, including finding replacements
for the dropped packages, from this list.)


HTH
-- 
Lew Pitcher
"In Skills We Trust"

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

#34156

On 2023-03-14 at 11:28 ADT, Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote:
> On Tue, 14 Mar 2023 08:54:18 +0000, Joseph Rosevear wrote:
>
>> OK, this is a survey.  Pick all that apply:

<snip>

> For my existing Slackware systems, I /upgrade/ from the downloaded
> iso.

<snip>

A while back there was some discussion about whether /etc/mtab is (or
should be) a file or a link to /proc/mounts (or /proc/self/mounts).

So... please chime in...  What is /etc/mtab on your systems, upgraded and
fresh installs?

                                Jim

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

#34159

Jim Diamond <JimDiamond@ns.sympatico.ca> wrote:
> On 2023-03-14 at 11:28 ADT, Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote:
>> On Tue, 14 Mar 2023 08:54:18 +0000, Joseph Rosevear wrote:
>>
>>> OK, this is a survey.  Pick all that apply:
> 
> <snip>
> 
>> For my existing Slackware systems, I /upgrade/ from the downloaded
>> iso.
> 
> <snip>
> 
> A while back there was some discussion about whether /etc/mtab is (or
> should be) a file or a link to /proc/mounts (or /proc/self/mounts).
> 
> So... please chime in...  What is /etc/mtab on your systems, upgraded and
> fresh installs?

Brand new fresh Slack-15 install (this past weekend).

/etc/mtab is a symlink to /proc/mounts

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

#34162

Jim Diamond <JimDiamond@ns.sympatico.ca> writes:

> A while back there was some discussion about whether /etc/mtab is (or
> should be) a file or a link to /proc/mounts (or /proc/self/mounts).

> So... please chime in...  What is /etc/mtab on your systems, upgraded and
> fresh installs?

I think I was the OP on that.  Slackware 15 installed from bootable
DVD created from d/l iso.  Came up with mtab as link to /proc/mounts.

I often mount laptop or 2nd desktop on main box's fs, for backup or
other purposes.  Annoyance that root has to umount them.

Another poster remarked on having scripts to pre-identify how an
upgrade would/might break his setup.  I've tried to avoid those
worries with always a new install, then reconstructing (with much
bother as my pleas for help here reflect) the numerous idiosyncrasies
of my setup.

-- 
Mike Spencer                  Nova Scotia, Canada

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

#34179

On 2023-03-15 at 01:19 ADT, Mike Spencer <mds@bogus.nodomain.nowhere> wrote:
>
> Jim Diamond <JimDiamond@ns.sympatico.ca> writes:
>
>> A while back there was some discussion about whether /etc/mtab is (or
>> should be) a file or a link to /proc/mounts (or /proc/self/mounts).
>
>> So... please chime in...  What is /etc/mtab on your systems, upgraded and
>> fresh installs?
>
> I think I was the OP on that.  Slackware 15 installed from bootable
> DVD created from d/l iso.  Came up with mtab as link to /proc/mounts.
>
> I often mount laptop or 2nd desktop on main box's fs, for backup or
> other purposes.  Annoyance that root has to umount them.
>
> Another poster remarked on having scripts to pre-identify how an
> upgrade would/might break his setup.  I've tried to avoid those
> worries with always a new install, then reconstructing (with much
> bother as my pleas for help here reflect) the numerous idiosyncrasies
> of my setup.

I was really hoping the guy who talked about his many systems (some clean
installs, some upgrades) would chime in.  But so far, no luck.

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

#34181

On Fri, 17 Mar 2023 17:14:03 -0300, Jim Diamond wrote:
> I was really hoping the guy who talked about his many systems (some
> clean installs, some upgrades) would chime in.  But so far, no luck.

I have many systems, but I don't think I am that guy as all my systems 
are clean installs (with patches and some extra packages applied).

On my 14.2 systems and earlier /etc/mtab is a file.
On my 15.0 system /etc/mtab is a symbolic link.

I have not had the need to umount nfs as a normal user as I make /etc/
rc.d/rc.autofs executable on my systems and instead access nfs exports 
by /net/<the_other_host_name>.

I think the above is the default behavior with the automounter running, 
but I have made some customizations to /etc/auto.master so I can't say 
for sure. In my /etc/auto.master there is a line:

/net    /etc/auto.net

I am rather sure that /etc/auto.net has not been modified by me, but this 
is what it looks like:

-8<-------------------------
#
# Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#
#/misc  /etc/auto.misc
#
# NOTE: mounts done from a hosts map will be mounted with the
#       "nosuid" and "nodev" options unless the "suid" and "dev"
#       options are explicitly given.
#
#/net   -hosts
#       -hosts does no longer work with autofs 5.0.8
/net    /etc/auto.net
#
# Include /etc/auto.master.d/*.autofs
#
+dir:/etc/auto.master.d
#
# Include central master map if it can be found using
# nsswitch sources.
#
# Note that if there are entries for /net or /misc (as
# above) in the included master map any keys that are the
# same will not be seen as the first read key seen takes
# precedence.
#
+auto.master.slack150
bash-5.1$ ls /etc/auto.master.d/
bash-5.1$ md5sum /etc/auto.net 
9113a0a4baccab3bf5cc9a476476d9c6  /etc/auto.net
bash-5.1$ cat /etc/auto.net 
#!/bin/bash

# This file must be executable to work! chmod 755!

# Look at what a host is exporting to determine what we can mount.
# This is very simple, but it appears to work surprisingly well

key="$1"

# add "nosymlink" here if you want to suppress symlinking local 
filesystems
# add "nonstrict" to make it OK for some filesystems to not mount
opts="-fstype=nfs,hard,nodev,nosuid"

for P in /bin /sbin /usr/bin /usr/sbin
do
        for M in showmount kshowmount
        do
                if [ -x $P/$M ]
                then
                        SMNT=$P/$M
                        break 2
                fi
        done
done

[ -x $SMNT ] || exit 1

# Newer distributions get this right
SHOWMOUNT="$SMNT --no-headers -e $key"

$SHOWMOUNT | LC_ALL=C cut -d' ' -f1 | LC_ALL=C sort -u | \
        awk -v key="$key" -v opts="$opts" -- '
        BEGIN   { ORS=""; first=1 }
                { if (first) { print opts; first=0 }; print " \\\n\t" $1, 
key ":" $1 }
        END     { if (!first) print "\n"; else exit 1 }
        ' | sed 's/#/\\#/g'

-8<-------------------------

Whenever someone or something tries to cd to /net/the_other_hostname the 
automounter calls the above executable script which uses showmount to see 
what that host exports by NFS and the automounter mounts those 
directories. When the directories are no longer in use the aoutmounter 
will umount them after some time.

regards Henrik

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

#34183

On Fri, 17 Mar 2023 17:14:03 -0300, Jim Diamond wrote:

> On 2023-03-15 at 01:19 ADT, Mike Spencer <mds@bogus.nodomain.nowhere> wrote:
>>
>> Jim Diamond <JimDiamond@ns.sympatico.ca> writes:
>>
>>> A while back there was some discussion about whether /etc/mtab is (or
>>> should be) a file or a link to /proc/mounts (or /proc/self/mounts).
>>
>>> So... please chime in...  What is /etc/mtab on your systems, upgraded and
>>> fresh installs?
>>
>> I think I was the OP on that.  Slackware 15 installed from bootable
>> DVD created from d/l iso.  Came up with mtab as link to /proc/mounts.
>>
>> I often mount laptop or 2nd desktop on main box's fs, for backup or
>> other purposes.  Annoyance that root has to umount them.
>>
>> Another poster remarked on having scripts to pre-identify how an
>> upgrade would/might break his setup.  I've tried to avoid those
>> worries with always a new install, then reconstructing (with much
>> bother as my pleas for help here reflect) the numerous idiosyncrasies
>> of my setup.
> 
> I was really hoping the guy who talked about his many systems (some clean
> installs, some upgrades) would chime in.  But so far, no luck.

That might be me?

As I said before, bare metal installs I usually perform directly from
bootable media (DVD or usb hard drive). Upgrades, I perform from from
DVD or hard drive, with the assistance of a number of home-grown scripts.

As I do not perform a Slackware "full install" on any of my systems. I
install only what I use, save for libraries, of which I install all that
are supplied. That means that a "full upgrade" is out of the question.

So, I used my IT background (retired programmer/systems programmer/analyst/architect)
to craft some scripts that would assist in the upgrade. One script figures
out the differences between the current installation and the "installation
after upgrade", pointing out installed packages that have been dropped,
installed packages that have not changed, installed packages that have
an upgrade, and new packages that don't have an installed equivalent, 

From there, I can identify what I want to do with each of the packages,
and a second script builds a set of "installation scripts" that will
perform the installation in an orderly manner. 

This set of scripts also manages a list of patches and local packages
that the upgrade process might need to affect.

For the most part, the scripts are a success, in that I can do an
ordered upgrade with no problems. For instance, I upgraded from 13.0
to 14.0 (skipping 13.1 and 13.37) successfully, using these scripts.

-- 
Lew Pitcher
"In Skills We Trust"

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

#34184

On Sat, 18 Mar 2023 16:06:30 +0000, Lew Pitcher wrote:

> On Fri, 17 Mar 2023 17:14:03 -0300, Jim Diamond wrote:
> 
>> On 2023-03-15 at 01:19 ADT, Mike Spencer <mds@bogus.nodomain.nowhere> wrote:
>>>
>>> Jim Diamond <JimDiamond@ns.sympatico.ca> writes:
>>>
>>>> A while back there was some discussion about whether /etc/mtab is (or
>>>> should be) a file or a link to /proc/mounts (or /proc/self/mounts).
>>>
>>>> So... please chime in...  What is /etc/mtab on your systems, upgraded and
>>>> fresh installs?
>>>
>>> I think I was the OP on that.  Slackware 15 installed from bootable
>>> DVD created from d/l iso.  Came up with mtab as link to /proc/mounts.
>>>
>>> I often mount laptop or 2nd desktop on main box's fs, for backup or
>>> other purposes.  Annoyance that root has to umount them.
>>>
>>> Another poster remarked on having scripts to pre-identify how an
>>> upgrade would/might break his setup.  I've tried to avoid those
>>> worries with always a new install, then reconstructing (with much
>>> bother as my pleas for help here reflect) the numerous idiosyncrasies
>>> of my setup.
>> 
>> I was really hoping the guy who talked about his many systems (some clean
>> installs, some upgrades) would chime in.  But so far, no luck.
> 
> That might be me?

[snip]

For what it's worth, I currently run three Slackware systems, all at 64bit
Slackware 14.2. One runs my internet-facing services, while a second runs
my PBX and a third provides my desktop processing needs. I've used my upgrade
scripts on two of the three (the PBX started life as 64bit Slackware 14.2)
since the days of 32bit Slackware 11.

I'd rather not discuss the internals of those home-grown upgrade scripts here,
but I welcome email inquiries.

-- 
Lew Pitcher
"In Skills We Trust"

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

#34187

On 2023-03-18 at 13:06 ADT, Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote:
> On Fri, 17 Mar 2023 17:14:03 -0300, Jim Diamond wrote:

>> On 2023-03-15 at 01:19 ADT, Mike Spencer <mds@bogus.nodomain.nowhere> wrote:

>>> Jim Diamond <JimDiamond@ns.sympatico.ca> writes:

>>>> A while back there was some discussion about whether /etc/mtab is (or
>>>> should be) a file or a link to /proc/mounts (or /proc/self/mounts).

>>>> So... please chime in...  What is /etc/mtab on your systems, upgraded and
>>>> fresh installs?

>>> I think I was the OP on that.  Slackware 15 installed from bootable
>>> DVD created from d/l iso.  Came up with mtab as link to /proc/mounts.

>>> I often mount laptop or 2nd desktop on main box's fs, for backup or
>>> other purposes.  Annoyance that root has to umount them.

>>> Another poster remarked on having scripts to pre-identify how an
>>> upgrade would/might break his setup.  I've tried to avoid those
>>> worries with always a new install, then reconstructing (with much
>>> bother as my pleas for help here reflect) the numerous idiosyncrasies
>>> of my setup.

>> I was really hoping the guy who talked about his many systems (some clean
>> installs, some upgrades) would chime in.  But so far, no luck.

> That might be me?

Indeed it is.

> As I said before, bare metal installs I usually perform directly from
> bootable media (DVD or usb hard drive). Upgrades, I perform from from
> DVD or hard drive, with the assistance of a number of home-grown scripts.

<much snippage>

What you didn't address was the question I asked.  Let me restate, with a
bit more detail...

Since you seem to have multiple systems, some upgraded and some fresh
installs, is it the case that /etc/mtab is always a symlink on the fresh
install systems and always a file on systems upgraded from 14.2 ?

(Perhaps answering this is too much effort for the perceived value, but if
it isn't, I'm curious, and perhaps others are as well.)

                                Jim

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

#34188

Jim Diamond <JimDiamond@jdvb.ca> wrote:
> What you didn't address was the question I asked.  Let me restate, with a
> bit more detail...
> 
> Since you seem to have multiple systems, some upgraded and some fresh
> installs, is it the case that /etc/mtab is always a symlink on the fresh
> install systems and always a file on systems upgraded from 14.2 ?
> 
> (Perhaps answering this is too much effort for the perceived value, but if
> it isn't, I'm curious, and perhaps others are as well.)

You can answer this question yourself.

Go to your friendly slackware mirror, and within the 15.0 file tree, 
browse to the source/installe/sources/initrd directory.

Download the skeleton_initrd.tar.gz file.

Decompress the tar.gz file somewhere, and within the unpacked contents, 
navigate to the usr/lib/setup directory.

View the 'setup' file in usr/lib/setup.

search for 'mtab' in the 'setup' file.

You will find this within the setup code:

  # On a new system, make /etc/mtab a symlink to /proc/mounts:
  if [ ! -r $T_PX/etc/mtab ]; then
    mkdir -p $T_PX/etc
    ( cd $T_PX/etc ; ln -sf /proc/mounts mtab )
  fi

What that says is if there is no "/etc/mtab' file on the disk being 
installed onto, then create mtab as a sysmlink to /proc/mounts.

So, for a fresh install, /etc/mtab will always be a symlink to 
/proc/mounts.

For an upgrade, with an existing /etc/mtab, the existing /etc/mtab will 
be untouched.

For an upgrade, without an existing /etc/mtab (unlikely, but someone 
could rm it before beginning the install) a symlink from /etc/mtab to 
/proc/mounts will also be created.

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

#34192

On 2023-03-20 at 19:00 ADT, Rich <rich@example.invalid> wrote:
> Jim Diamond <JimDiamond@jdvb.ca> wrote:
>> What you didn't address was the question I asked.  Let me restate, with a
>> bit more detail...

>> Since you seem to have multiple systems, some upgraded and some fresh
>> installs, is it the case that /etc/mtab is always a symlink on the fresh
>> install systems and always a file on systems upgraded from 14.2 ?

>> (Perhaps answering this is too much effort for the perceived value, but if
>> it isn't, I'm curious, and perhaps others are as well.)

> You can answer this question yourself.

> Go to your friendly slackware mirror, and within the 15.0 file tree, 
> browse to the source/installe/sources/initrd directory.

> Download the skeleton_initrd.tar.gz file.

> Decompress the tar.gz file somewhere, and within the unpacked contents, 
> navigate to the usr/lib/setup directory.

> View the 'setup' file in usr/lib/setup.

> search for 'mtab' in the 'setup' file.

> You will find this within the setup code:

>   # On a new system, make /etc/mtab a symlink to /proc/mounts:
>   if [ ! -r $T_PX/etc/mtab ]; then
>     mkdir -p $T_PX/etc
>     ( cd $T_PX/etc ; ln -sf /proc/mounts mtab )
>   fi

> What that says is if there is no "/etc/mtab' file on the disk being 
> installed onto, then create mtab as a sysmlink to /proc/mounts.

> So, for a fresh install, /etc/mtab will always be a symlink to 
> /proc/mounts.

How curious...  I did a fresh install, and yet my mtab is a file.  I wonder
what I might have done to cause this to happen.  Perhaps a stray neutrino
hit some gate in my CPU or some bit in a register just at the wrong moment.

Anyway, thanks for the detailed pointer to the code which creates the
link.

                        Jim

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

#34194

On 03/22/2023 01:47 PM, Jim Diamond wrote:

> How curious...  I did a fresh install, and yet my mtab is a file.

Yes, in 14.2, 15.0 and Current mtab is a file and not a folder. I have 
all 3 installed and I checked.
-- 
Jimmy Johnson
Slackware Current - AMD A8-7600 at sda7
Registered Linux User #380263

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

#34196

On Wed, 22 Mar 2023 18:20:11 -0700, Jimmy Johnson wrote:

> On 03/22/2023 01:47 PM, Jim Diamond wrote:
> 
>> How curious...  I did a fresh install, and yet my mtab is a file.
> 
> Yes, in 14.2, 15.0 and Current mtab is a file and not a folder. I have
> all 3 installed and I checked.

For me, on all Slackware 15 fresh installs, /etc/mtab is a symbolic link:

-8<--------------------------
bash-5.1$ ls -al /etc/mtab 
lrwxrwxrwx 1 root root 12 Jul 17  2022 /etc/mtab -> /proc/mounts
bash-5.1$ cat /etc/slackware-version 
Slackware 15.0
-8<--------------------------

On 14.2 and older it is a file:

-8<--------------------------
bash-4.3$ ls -al /etc/mtab
-rw-r--r-- 1 root root 735 Mar 19 11:31 /etc/mtab
bash-4.3$ cat /etc/slackware-version 
Slackware 14.2
-8<--------------------------

On Slackware 15.0, /etc/mtab will become a file if the symbolic link is 
removed. From /etc/rc.d/rc.S:

-8<--------------------------
# If /etc/mtab is a symlink (probably to /proc/mounts) then we don't want 
to mess with it.
if [ ! -L /etc/mtab -o ! -r /etc/mtab ]; then
  # /etc/mtab is a file (or doesn't exist), so we'll handle it the old 
way:
  # Any /etc/mtab that exists here is old, so we start with a new one:
  /bin/rm -f /etc/mtab{,~,.tmp} && /bin/touch /etc/mtab
-8<--------------------------

regards Henrik

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

#34218

On 2023-03-22 at 22:20 ADT, Jimmy Johnson <Jimmy@disposable.invalid> wrote:
> On 03/22/2023 01:47 PM, Jim Diamond wrote:
>
>> How curious...  I did a fresh install, and yet my mtab is a file.
>
> Yes, in 14.2, 15.0 and Current mtab is a file and not a folder.  I have 
> all 3 installed and I checked.

As Henrik (and maybe others) have pointed out, the "fresh install" code
should make it a link.

But when you say "not a folder" (and I assume you mean "not a directory"),
that isn't the issue.  It might be a symlink to /proc/mounts.

Were your 15.0 and current systems upgraded from 14.2 or fresh installs?

                                Jim

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

#34221

On 03/25/2023 11:37 AM, Jim Diamond wrote:
> On 2023-03-22 at 22:20 ADT, Jimmy Johnson <Jimmy@disposable.invalid> wrote:
>> On 03/22/2023 01:47 PM, Jim Diamond wrote:

>>> How curious...  I did a fresh install, and yet my mtab is a file.
>>
>> Yes, in 14.2, 15.0 and Current mtab is a file and not a folder.  I have
>> all 3 installed and I checked.

> As Henrik (and maybe others) have pointed out, the "fresh install" code
> should make it a link.

> But when you say "not a folder" (and I assume you mean "not a directory"),
> that isn't the issue.  It might be a symlink to /proc/mounts.

So you've decided to become the teacher and not the student, how rude of 
you. I don't normally go around correction such trivial things but in 
your case I will make the exception. When I open my file manager and go 
to my /home/"folder" and right click I get the option to make a new 
"folder". No where is the word "directory" mentioned. And in your file 
manager you have two things folders and files, that makes a symbolic 
link a file. Now please don't go around correcting people for trivial 
things it is rude. By the way "Were" is not the word you wanted to use, 
maybe "where" or "was" is what you wanted to say. Now I'm done being the 
one who is rude. :)

> Were your 15.0 and current systems upgraded from 14.2 or fresh installs?

You install the current stable(today that would be 15.0) and go to 
/etc/slackpkg/mirrors and switch to current, done. And like I said, I 
run old stable, current stable and current. And yes, upgrading current 
will give you the next stable, I have done both, upgrade install and 
fresh install, If you want stable a fresh install is the best way to go. 
And yes 14.2 was upgraded to 15.0, but like I said doing a fresh install 
is the best way to go.
-- 
Jimmy Johnson

Slackware64 15.0 - i7-2820QM - EXT4 at sda9
Registered Linux User #380263

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

Page 1 of 5  [1] 2 3 4 5  Next page →

Back to top | Article view | alt.os.linux.slackware

csiph-web