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 2 of 5 — ← Prev page 1 [2] 3 4 5  Next page →

#34222

Jimmy Johnson <Jimmy@disposable.invalid> wrote:
> 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.

"Directory" is the actual underlying filesystem name for the structure, 
and in the command line tools, "directory" is pretty much exclusively 
used as the name.  That's why the "permissions" character that shows in 
a long listing from ls (ls -l) is a "d" for directories, and why the 
"mkdir" (MaKeDIRectory), "rmdir" (ReMoveDIRectory), cd (Change 
Directory), and pwd (Print Working Directory) commands are named the 
way they are.

The name "folder" is all but exclusively used by graphical user 
interfaces as the name for what the OS, and the underlying tools, call 
a directory.  This difference likely came about from Apple copying 
Xerox and creating a "desktop metaphor" that included "files" stored in 
"folders" to mimic the then paper world of "folders" holding sheets of 
paper.  Microsoft then copying Apple to create windows also copied the 
"folder" naming, and so we have what we have.

And one can often deduce someone's level of skill with the underlying, 
non-graphical, command line by what term they normally use when 
referring to "directories".  If they use "folder" then it is highly 
likely they are primarially a GUI user with little to no command line 
experience.  If they use "directory" then they likely have lots of 
experience using the command line tools.  This of course is an 
imperfect predictor.

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

#34223

On 03/25/2023 09:21 PM, Rich wrote:

> "Directory" is the actual underlying filesystem name for the structure,
> and in the command line tools, "directory" is pretty much exclusively
> used as the name.  That's why the "permissions" character that shows in
> a long listing from ls (ls -l) is a "d" for directories, and why the
> "mkdir" (MaKeDIRectory), "rmdir" (ReMoveDIRectory), cd (Change
> Directory), and pwd (Print Working Directory) commands are named the
> way they are.

You have not proven my use of files and folders was incorrect. Nothing I 
said was wrong and I don't need your lesson to run Slackware as a matter 
of fact most of what I do with Slackware I do from a chroot and I've 
been using cli for a long long time.
-- 
Jimmy Johnson

Alien-19-Linux - AMD A8-7600 at sda11
Registered Linux User #380263

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

#34225

Jimmy Johnson <Jimmy@disposable.invalid> wrote:
> On 03/25/2023 09:21 PM, Rich wrote:
> 
>> "Directory" is the actual underlying filesystem name for the 
>> structure, and in the command line tools, "directory" is pretty much 
>> exclusively used as the name.  That's why the "permissions" 
>> character that shows in a long listing from ls (ls -l) is a "d" for 
>> directories, and why the "mkdir" (MaKeDIRectory), "rmdir" 
>> (ReMoveDIRectory), cd (Change Directory), and pwd (Print Working 
>> Directory) commands are named the way they are.
> 
> You have not proven my use of files and folders was incorrect.

Did I say anywhere in my post that you were wrong?

> Nothing I said was wrong and I don't need your lesson to run 
> Slackware as a matter of fact most of what I do with Slackware I do 
> from a chroot and I've been using cli for a long long time.

Then you are a member of the minority set for which using 'directory' 
or 'folder' is an inaccurate way to predict CLI usage experience.  
Which was way I included the final sentence stating that such was not a 
perfect predictor.

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

#34189

On Mon, 20 Mar 2023 16:09:58 -0300, Jim Diamond wrote:

> 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 ?

As I don't (yet) have any systems running Slackware 15.0, I can't answer
that question. However, all my 14.2 systems, both fresh install and upgrade
have an /etc/mtab file, and not a symlink.

Hope that helps
-- 
Lew Pitcher
"In Skills We Trust"

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

#34191

On 2023-03-20 at 19:39 ADT, Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote:
> On Mon, 20 Mar 2023 16:09:58 -0300, Jim Diamond wrote:

>> 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 ?

> As I don't (yet) have any systems running Slackware 15.0, I can't answer
> that question. However, all my 14.2 systems, both fresh install and upgrade
> have an /etc/mtab file, and not a symlink.

> Hope that helps

It does help, in the sense that I now know you don't have a large sample of
15.0 systems sitting there waiting to reveal their secrets.

Cheers.
                                Jim

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

#35071

I burn the ISO to a DVD or flash it to a USB. Then I boot and install as
normal.

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

#35721

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2024-12-16, TronNerd82 <republicanismiscancer@tutanota.com> wrote:
> I burn the ISO to a DVD or flash it to a USB. Then I boot and install as
> normal.

  Now I prepare the disk with Ventoy and put the ISO on it.
  
- -- 

Stela dato:2.461.251,767  Loka tempo:2026-07-30 03:23:55 Ĵaŭdo    
Slackware 15.0 x86_64
-----BEGIN PGP SIGNATURE-----
Comment: +-----------------------------------------------------+
Comment: !        https://t.me/Gilberto_F_da_Silva             !
Comment: +-----------------------------------------------------+

iFcDBQFqa5UhdAvwmry29xoRCCHIAQCO6tiQ7aR9GeL23p9lcs5Lt7QZQlUPDFGj
faAxLbEXaQD/ZBeRqgLgB+t8jkoxmjEmYBzM1apATtNI+pxzL0cxCVc=
=9ID1
-----END PGP SIGNATURE-----

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

#35723

On Thu, 30 Jul 2026 18:17:21 -0000 (UTC), Gilberto F da Silva wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> On 2024-12-16, TronNerd82 <republicanismiscancer@tutanota.com> wrote:
>> I burn the ISO to a DVD or flash it to a USB. Then I boot and install
>> as normal.
> 
>   Now I prepare the disk with Ventoy and put the ISO on it.

I'm a Grub user, but Ventoy sounds very easy to use.  I wonder though if 
I would like it?

-Joe

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

#35724

Joseph Rosevear <Mail@JoesLife.org> writes:

>>   Now I prepare the disk with Ventoy and put the ISO on it.
>
> I'm a Grub user, but Ventoy sounds very easy to use.  I wonder though if 
> I would like it?

Usually I just use cdrecord or dd but after hearing so many people talk
about Ventoy I tried it with a number of different images. One was
Slackware Linux, two were illumos, and maybe there were two more in
there that I forget the names of now. Only the Slackware one booted
despite the other ones being known-good (I used them for previous
installs). So, the advice here is test it before you rely on it. 

-- 
PGP Key ID: 781C A3E2 C6ED 70A6 B356  7AF5 B510 542E D460 5CAE
       "The Internet should always be the Wild West!"

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

#34155

Joseph Rosevear <Mail@joeslife.org> 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.

Depends:

Bare metal:

Download DVD .iso.

Then either burn to DVD or load to USB stick , boot from DVD/USB stick 
(which one depends upon what boot method the BIOS of bare metal machine 
supports), install.

Or:

Download DVD .iso, attach disk to additional drive port of existing 
running system, connect raw disk device to VirtualBox, link DVD .iso to 
VirtualBox, boot DVD in Virtual box, with /dev/sda of the virtual 
machine being the "linked" extra disk, install/configure inside VB.  
Then move pre-installed disk into end destination machine.

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

#34157

#7 - Monolithic DVD iso -> Usb drive -> Happiness

zmc


On 2023-03-14 01:54, 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.

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

#34158

On Tue, 14 Mar 2023 08:54:18 -0000 (UTC), 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.

Choice #2, but sometimes to a USB stick rather than a DVD.



-- 
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as the woodpecker approached his hot-air balloon.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
Thanks, Obama: http://brandybuck.site40.net/pics/politica/thanks.jpg

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

#34160

On Tue, 14 Mar 2023 17:34:39 GMT, Dan C wrote:

> On Tue, 14 Mar 2023 08:54:18 -0000 (UTC), 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.
> 
> Choice #2, but sometimes to a USB stick rather than a DVD.

This sounds similar to what I do. Do you use Grub like this (below) to 
boot the stick?:

        isofile='/Slackware/slackware-14.2-iso/slackware-14.2-install-
d1.iso'
        loopback loop $isofile
        linux   (loop)/kernels/hugesmp.s/bzImage
        initrd  (loop)/isolinux/initrd.img

Or some other way?  It was a big surprise when I learned how to do it 
this way.  I wonder if many people know this technique and also if this 
can be done with other boot loaders?

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

#34165

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

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

>    7.  Some other way.

I download the DVD iso and also the sources directory. Then spend some 
weeks on modifying the scripts in /usr/lib/setup in the installation 
initrd and adding custom packages including packages with scripts 
overwriting the scripts in /var/log/setup to give me a quick installation 
with only initial few questions. This custom installaiton boils down to 
two .iso-files, one for a bootable cdrom intended for a NFS install and 
one for a bootable bluray intended for standalone install.

I try to make any added software or any customization of configuration 
files to custom Slackware packages which are deployed on all 
installations.

regards Henrik

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

#34167

On 3/14/23 04:54, 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.

This one ^


>     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.

What I would like to see is a strictly user-oriented
install (off the net which is something I would let
Slackware do). I know this is well within the reach of
experts but I ain't no expert so...

Before anything at all got gets installed I would see
package selection start with me selecting let's say Firefox.
The installer would then list-in all the depends, the
first package thus selected naturally requiring a gigabyte
right off the bat. Then I would select others like maybe
Sylpheed, Kdenlive, etc. The idea would be that NOTHING
would get installed that wasn't *directly or indirectly*
commanded, no kwallet-anything to be blunt by way of one
example. I find that many distros pad the offerings by
just including stuff I would NEVER take off the shelf so
to speak.

I remember having tried this once with Suse I think, I
deleted every package from the offered list and then
started rebuilding from nothing but if my memory serves
right it just became a royal mess :-)

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

#34170

On Wed, 15 Mar 2023 08:16:21 -0400, bad sector wrote:
> The idea would be that NOTHING would get installed that wasn't
> *directly or indirectly*

There are other Linux distributions which have different kinds of package 
management solutions which includes dependency resolution. Slackware 
package management does not have dependency resoltion. If you think you 
know what you are doing you can manually select packages during 
installation but the recomended way to install is to do a full install.

Then there are third party repositories for Slackware like 
slackbuilds.org which together with different tools offer dependency 
resolution for their third party packages. However, all those dependency 
resolutions only apply to the third party packages, they all assume that  
you have made a full install of Slackware.

For good and bad Slackware does not have dependency resolution. What 
would be the best way to upgrade or remove package X on which package Y 
depends? Even with the dependency resolution from third party package 
providers like slackbuilds.org it can quickly become a mess. Suppose that 
you install package Y which depends upon package X. Two years later you 
install package Z which also depends upon package X, but requires a newer 
version of package X. To get package Z you will need to compile and 
install a newer version of package X, but this will break package Y. If 
you are lucky you might be able to recompile and reinstall package Y, if 
you are unlucky your package Y is not compatible with the newer version 
of package X.

With the original Slackware packages we know that they will allways match 
each other. If a package is provided as a upgraded security patch any 
other package which needs to be recompiled will also be provided from 
Slackware.

regards Henrik

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

#34173

Den 2023-03-16 skrev Henrik Carlqvist <Henrik.Carlqvist@deadspam.com>:
> On Wed, 15 Mar 2023 08:16:21 -0400, bad sector wrote:
>> The idea would be that NOTHING would get installed that wasn't
>> *directly or indirectly*
>
> There are other Linux distributions which have different kinds of package 
> management solutions which includes dependency resolution. Slackware 
> package management does not have dependency resoltion. If you think you 
> know what you are doing you can manually select packages during 
> installation but the recomended way to install is to do a full install.
>
< large snip >
>
> other package which needs to be recompiled will also be provided from 
> Slackware.
>
> regards Henrik

Isn't Salix supposed to have dependency resolution? Any thoughts on
that?

/Martin (used to Debian, curious about Slackware)

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

#34248

Den 2023-03-16 skrev Martin Schöön <martin.schoon@gmail.com>:
> Den 2023-03-16 skrev Henrik Carlqvist <Henrik.Carlqvist@deadspam.com>:
>> On Wed, 15 Mar 2023 08:16:21 -0400, bad sector wrote:
>>> The idea would be that NOTHING would get installed that wasn't
>>> *directly or indirectly*
>>
>> There are other Linux distributions which have different kinds of package 
>> management solutions which includes dependency resolution. Slackware 
>> package management does not have dependency resoltion. If you think you 
>> know what you are doing you can manually select packages during 
>> installation but the recomended way to install is to do a full install.
>>
>< large snip >
>>
>> other package which needs to be recompiled will also be provided from 
>> Slackware.
>>
>> regards Henrik
>
> Isn't Salix supposed to have dependency resolution? Any thoughts on
> that?
>
> /Martin (used to Debian, curious about Slackware)

I wanted to try out Salix but as I want to use it with full disk
encryption it was put on hold. Then I learned about Slint which
builds on Salix and has an installer that does the disk encryption for
you. I installed Slint on a virtual machine (Qemu) and the installer
worked just fine including encryption.

So now I have the opportunity to try out Gslapt and its dependency
resolution. It is work in progress. Some packages provide Gslapt with
the information needed to install missing dependencies. Other packages
miss this information.

I also test Flatpak. It works but consumes disk space like there is no
tomorrow. Disclaimer: I have only done really simple testing.

/Martin

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

#34249

On 2023-04-08, Martin Schöön <martin.schoon@gmail.com> wrote:
> Den 2023-03-16 skrev Martin Schöön <martin.schoon@gmail.com>:
>> Den 2023-03-16 skrev Henrik Carlqvist <Henrik.Carlqvist@deadspam.com>:
>>> On Wed, 15 Mar 2023 08:16:21 -0400, bad sector wrote:
>>>> The idea would be that NOTHING would get installed that wasn't
>>>> *directly or indirectly*
>>>
> worked just fine including encryption.
>
> So now I have the opportunity to try out Gslapt and its dependency
> resolution. It is work in progress. Some packages provide Gslapt with
> the information needed to install missing dependencies. Other packages
> miss this information.
>
> I also test Flatpak. It works but consumes disk space like there is no
> tomorrow. Disclaimer: I have only done really simple testing.
>
> /Martin

Encryptation is bunk. All the utilities are backdoored to hell.


-- 
greymausg@mail.com

Fe, Fi, Fo, Fum, I smell the stench of an Influencer.
Where is our money gone, Dude?

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

#34250

On Sat, 08 Apr 2023 11:47:31 +0000, maus wrote:

| Encryptation is bunk. All the utilities are backdoored to hell.

greymaus... a name from a lifetime ago (if you are him)... from the chat 
net run by that scott scanner fella, you always were a one-liner guy

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

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

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

csiph-web