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

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

WiFi without Network Manager

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

Contents

  WiFi without Network Manager Kenneth Parker <sea7kenp@gmail.com> - 2019-02-12 15:20 +0100
    Re: WiFi without Network Manager <tomas@tuxteam.de> - 2019-02-12 15:40 +0100
      Re: WiFi without Network Manager Kenneth Parker <sea7kenp@gmail.com> - 2019-02-12 15:50 +0100
        Re: WiFi without Network Manager <tomas@tuxteam.de> - 2019-02-12 16:00 +0100
          Re: WiFi without Network Manager Kenneth Parker <sea7kenp@gmail.com> - 2019-02-12 19:00 +0100
            Re: WiFi without Network Manager Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2019-02-12 19:50 +0100
              Re: WiFi without Network Manager Kenneth Parker <sea7kenp@gmail.com> - 2019-02-12 20:10 +0100
      Re: WiFi without Network Manager Kenneth Parker <sea7kenp@gmail.com> - 2019-02-15 00:30 +0100
        Re: WiFi without Network Manager mett <mett@pmars.jp> - 2019-02-15 05:00 +0100
          Re: WiFi without Network Manager Kenneth Parker <sea7kenp@gmail.com> - 2019-02-15 06:00 +0100
            Re: WiFi without Network Manager didier gaumet <didier.gaumet@gmail.com> - 2019-02-15 09:10 +0100
    Re: WiFi without Network Manager ghe <ghe@slsware.net> - 2019-02-12 15:50 +0100
      Glenn -> Re: WiFi without Network Manager deb <deb@rangingthoughts.org> - 2019-02-12 17:20 +0100
        Re: WiFi without Network Manager ghe <ghe@slsware.net> - 2019-02-12 21:10 +0100
          Re: WiFi without Network Manager deb <deb@rangingthoughts.org> - 2019-02-13 14:40 +0100
            Re: WiFi without Network Manager rhkramer@gmail.com - 2019-02-13 14:50 +0100
              Re: WiFi without Network Manager John Hasler <jhasler@newsguy.com> - 2019-02-13 15:20 +0100
                Re: WiFi without Network Manager Ric Moore <wayward4now@gmail.com> - 2019-02-13 17:40 +0100
            Re: WiFi without Network Manager mick crane <mick.crane@gmail.com> - 2019-02-13 15:00 +0100
          Swap space choice on a SSD <- Current best practice on? deb <deb@rangingthoughts.org> - 2019-02-13 14:50 +0100
            Re: Swap space choice on a SSD <- Current best practice on? Michael Stone <mstone@debian.org> - 2019-02-13 14:50 +0100
              Re: Swap space choice on a SSD <- Current best practice on? deb <deb@rangingthoughts.org> - 2019-02-13 15:00 +0100
                Re: Swap space choice on a SSD <- Current best practice on? Dan Ritter <dsr@randomstring.org> - 2019-02-13 15:20 +0100
                  Thanks Dan. Re: Swap space choice on a SSD <- Current best practice  on? deb <deb@rangingthoughts.org> - 2019-02-13 15:40 +0100
            Re: Swap space choice on a SSD <- Current best practice on? David Christensen <dpchrist@holgerdanske.com> - 2019-02-13 22:20 +0100
              Re: Swap space choice on a SSD <- Current best practice on? Dan Ritter <dsr@randomstring.org> - 2019-02-13 22:30 +0100
                Re: Swap space choice on a SSD <- Current best practice on? Andy Smith <andy@strugglers.net> - 2019-02-13 22:50 +0100
                Re: Swap space choice on a SSD <- Current best practice on? David Christensen <dpchrist@holgerdanske.com> - 2019-02-14 05:20 +0100
              Re: Swap space choice on a SSD <- Current best practice on? Andy Smith <andy@strugglers.net> - 2019-02-13 22:30 +0100
                Re: Swap space choice on a SSD <- Current best practice on? David Christensen <dpchrist@holgerdanske.com> - 2019-02-14 05:30 +0100
              Re: Swap space choice on a SSD <- Current best practice on? Michael Stone <mstone@debian.org> - 2019-02-13 22:30 +0100

Page 1 of 2  [1] 2  Next page →

#205234 — WiFi without Network Manager

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

I occasionally run, what I will describe as "Coffee House Lan Parties".
That means I connect to the Internet via WiFi, and then supply a "Local
Ethernet" network (with ipv4), for others to connect with.

Doing this with Network Manager "worked", but only with "loud complaining"
by Network Manager.

What I want now, are the "steps" that Network Manager takes, to bring up
WiFi, so I can create an "in-demand" Root-level Script that I can run, for
the WiFi part.  (The rest works fine, using /etc/network/interfaces).

Thank you!

Kenneth Parker (eyeblinkuniverse.com)

[toc] | [next] | [standalone]

#205235

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

On Tue, Feb 12, 2019 at 09:10:08AM -0500, Kenneth Parker wrote:
> I occasionally run, what I will describe as "Coffee House Lan Parties".
> That means I connect to the Internet via WiFi, and then supply a "Local
> Ethernet" network (with ipv4), for others to connect with.
> 
> Doing this with Network Manager "worked", but only with "loud complaining"
> by Network Manager.
> 
> What I want now, are the "steps" that Network Manager takes, to bring up
> WiFi, so I can create an "in-demand" Root-level Script that I can run, for
> the WiFi part.  (The rest works fine, using /etc/network/interfaces).

Actually ifupdown is perfectly capable of doing the work (well, it just
orchestrates it, but it commes with all the necessary scripts for that).

Here's my stanza in /etc/network/interfaces (passphrase somewhat decorated,
to protect the innocent):

  iface wlan0 inet dhcp
    wpa-ssid dubcek
    wpa-psk XXXXXXXXXXXXXXXX

That's all it is needed for ifup to set up wlan0, go out with DHCP and
fetch an IP address from our local DHCP server.

Of course it relies on wpasupplicant and dhclient to do the actual
magic behind the scenes.

Enjoy simple life :-)

Cheers
-- t

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

#205236

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

On Tue, Feb 12, 2019, 9:30 AM <tomas@tuxteam.de wrote:

> On Tue, Feb 12, 2019 at 09:10:08AM -0500, Kenneth Parker wrote:
> > I occasionally run, what I will describe as "Coffee House Lan Parties".
> > That means I connect to the Internet via WiFi, and then supply a "Local
> > Ethernet" network (with ipv4), for others to connect with.
> >
> > Doing this with Network Manager "worked", but only with "loud
> complaining"
> > by Network Manager.
> >
> > What I want now, are the "steps" that Network Manager takes, to bring up
> > WiFi, so I can create an "in-demand" Root-level Script that I can run,
> for
> > the WiFi part.  (The rest works fine, using /etc/network/interfaces).
>
> Actually ifupdown is perfectly capable of doing the work (well, it just
> orchestrates it, but it commes with all the necessary scripts for that).
>
> Here's my stanza in /etc/network/interfaces (passphrase somewhat decorated,
> to protect the innocent):
>
>   iface wlan0 inet dhcp
>     wpa-ssid dubcek
>     wpa-psk XXXXXXXXXXXXXXXX
>
> That's all it is needed for ifup to set up wlan0, go out with DHCP and
> fetch an IP address from our local DHCP server.
>
> Of course it relies on wpasupplicant and dhclient to do the actual
> magic behind the scenes.
>

Which part is "interactive", asking me for WiFi and Password?
Wpasupplicant?  Thanks!

>
> Enjoy simple life :-)
>
> Cheers
> -- t
>

Indeed.  Debian Always!

Kenneth Parker   (eyeblinkuniverse.com)

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

#205238

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

On Tue, Feb 12, 2019 at 09:44:47AM -0500, Kenneth Parker wrote:
> On Tue, Feb 12, 2019, 9:30 AM <tomas@tuxteam.de wrote:
> 
> > On Tue, Feb 12, 2019 at 09:10:08AM -0500, Kenneth Parker wrote:
> > > I occasionally run, what I will describe as "Coffee House Lan Parties".

[...]

> > Of course it relies on wpasupplicant and dhclient to do the actual
> > magic behind the scenes.
> >
> 
> Which part is "interactive", asking me for WiFi and Password?
> Wpasupplicant?  Thanks!

There's no interactive part. I just invoke "sudo ifup wlan0" on console
(this is because I have neither "auto wlan0" nor "allow-hotplug wlan0"
on my /etc/network/interfaces: I actually want to decide whether to
wlan or not) -- and seconds later I have a connection. That's all.

Cheers
-- t

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

#205243

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

On Tue, Feb 12, 2019, 9:59 AM <tomas@tuxteam.de wrote:

> On Tue, Feb 12, 2019 at 09:44:47AM -0500, Kenneth Parker wrote:
> > On Tue, Feb 12, 2019, 9:30 AM <tomas@tuxteam.de wrote:
> >
> > > On Tue, Feb 12, 2019 at 09:10:08AM -0500, Kenneth Parker wrote:
> > > > I occasionally run, what I will describe as "Coffee House Lan
> Parties".
>
> [...]
>
> > > Of course it relies on wpasupplicant and dhclient to do the actual
> > > magic behind the scenes.
> > >
> >
> > Which part is "interactive", asking me for WiFi and Password?
> > Wpasupplicant?  Thanks!
>
> There's no interactive part. I just invoke "sudo ifup wlan0" on console
> (this is because I have neither "auto wlan0" nor "allow-hotplug wlan0"
> on my /etc/network/interfaces: I actually want to decide whether to
> wlan or not) -- and seconds later I have a connection. That's all.
>

What gives you the list of potential WiFi hosts, to choose from?  (These
LAN Parties may be at a Coffee House I haven't been to before).

That's what I meant by "Interactive".

>
> Cheers
> -- t
>

Thanks!    Kenneth Parker

>

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

#205244

On ter, 12 fev 2019, Kenneth Parker wrote:
> What gives you the list of potential WiFi hosts, to choose from?  (These
> LAN Parties may be at a Coffee House I haven't been to before).
>
> That's what I meant by "Interactive".

So you want something that does exactly what NetworkManager does, but  
is not NetworkManager?

There's wicd, which is similar. I don't know of any others.
-- 
Eduardo M KALINOWSKI
eduardo@kalinowski.com.br

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

#205245

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

On Tue, Feb 12, 2019, 1:42 PM Eduardo M KALINOWSKI <
eduardo@kalinowski.com.br wrote:

> On ter, 12 fev 2019, Kenneth Parker wrote:
> > What gives you the list of potential WiFi hosts, to choose from?  (These
> > LAN Parties may be at a Coffee House I haven't been to before).
> >
> > That's what I meant by "Interactive".
>
> So you want something that does exactly what NetworkManager does, but
> is not NetworkManager?
>
> There's wicd, which is similar. I don't know of any others.
>

NetworkManager does what I want, but is too much of a Control Freak (even
approaching Autocratic).  I don't have much experience with wicd, but have
heard good things about it.

>
Perhaps I should check out the Source for nm and wicd:  That should give me
the "how", and Code Samples.

-- 
> Eduardo M KALINOWSKI
> eduardo@kalinowski.com.br


Thanks!

Kenneth Parker

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

#205341

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

On Tue, Feb 12, 2019 at 9:30 AM <tomas@tuxteam.de> wrote:

> On Tue, Feb 12, 2019 at 09:10:08AM -0500, Kenneth Parker wrote:
> > I occasionally run, what I will describe as "Coffee House Lan Parties".
> > That means I connect to the Internet via WiFi, and then supply a "Local
> > Ethernet" network (with ipv4), for others to connect with.
> >
> > Doing this with Network Manager "worked", but only with "loud
> complaining"
> > by Network Manager.
> >
> > What I want now, are the "steps" that Network Manager takes, to bring up
> > WiFi, so I can create an "in-demand" Root-level Script that I can run,
> for
> > the WiFi part.  (The rest works fine, using /etc/network/interfaces).
>
> Actually ifupdown is perfectly capable of doing the work (well, it just
> orchestrates it, but it commes with all the necessary scripts for that).
>
> Here's my stanza in /etc/network/interfaces (passphrase somewhat decorated,
> to protect the innocent):
>
>   iface wlan0 inet dhcp
>     wpa-ssid dubcek
>     wpa-psk XXXXXXXXXXXXXXXX
>
> That's all it is needed for ifup to set up wlan0, go out with DHCP and
> fetch an IP address from our local DHCP server.
>
> Of course it relies on wpasupplicant and dhclient to do the actual
> magic behind the scenes.
>

What did you have to do, the first time?  When you were determining the
Network Name (wpa-ssid)?  (Having to know everything in advance isn't too
cool,  when you visit multiple Coffee Houses. And connecting to the wrong
ssid could get you into some  *SERIOUS*  trouble!)

I am doing my own investigation, by the way, finding general information
on a "competing" Distro (Arch):

   https://wiki.archlinux.org/index.php/WPA_supplicant

This site suggests that wpa_cli gives useful information,  so I will see
what that looks like, and then use your interfaces method.

Enjoy simple life :-)
>
> Cheers
> -- t
>

Thanks!

Kenneth Parker

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

#205350

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

On 2019年2月15日 8:23:04 JST, Kenneth Parker <sea7kenp@gmail.com> wrote:
>On Tue, Feb 12, 2019 at 9:30 AM <tomas@tuxteam.de> wrote:
>
>> On Tue, Feb 12, 2019 at 09:10:08AM -0500, Kenneth Parker wrote:
>> > I occasionally run, what I will describe as "Coffee House Lan
>Parties".
>> > That means I connect to the Internet via WiFi, and then supply a
>"Local
>> > Ethernet" network (with ipv4), for others to connect with.
>> >
>> > Doing this with Network Manager "worked", but only with "loud
>> complaining"
>> > by Network Manager.
>> >
>> > What I want now, are the "steps" that Network Manager takes, to
>bring up
>> > WiFi, so I can create an "in-demand" Root-level Script that I can
>run,
>> for
>> > the WiFi part.  (The rest works fine, using
>/etc/network/interfaces).
>>
>> Actually ifupdown is perfectly capable of doing the work (well, it
>just
>> orchestrates it, but it commes with all the necessary scripts for
>that).
>>
>> Here's my stanza in /etc/network/interfaces (passphrase somewhat
>decorated,
>> to protect the innocent):
>>
>>   iface wlan0 inet dhcp
>>     wpa-ssid dubcek
>>     wpa-psk XXXXXXXXXXXXXXXX
>>
>> That's all it is needed for ifup to set up wlan0, go out with DHCP
>and
>> fetch an IP address from our local DHCP server.
>>
>> Of course it relies on wpasupplicant and dhclient to do the actual
>> magic behind the scenes.
>>
>
>What did you have to do, the first time?  When you were determining the
>Network Name (wpa-ssid)?  (Having to know everything in advance isn't
>too
>cool,  when you visit multiple Coffee Houses. And connecting to the
>wrong
>ssid could get you into some  *SERIOUS*  trouble!)
>
>I am doing my own investigation, by the way, finding general
>information
>on a "competing" Distro (Arch):
>
>   https://wiki.archlinux.org/index.php/WPA_supplicant
>
>This site suggests that wpa_cli gives useful information,  so I will
>see
>what that looks like, and then use your interfaces method.
>
>Enjoy simple life :-)
>>
>> Cheers
>> -- t
>>
>
>Thanks!
>
>Kenneth Parker

sudo iwlist wlan0 scan

<https://www.linuxjournal.com/content/wi-fi-command-line>

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

#205353

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

On Thu, Feb 14, 2019 at 10:54 PM mett <mett@pmars.jp> wrote:

> On 2019年2月15日 8:23:04 JST, Kenneth Parker <sea7kenp@gmail.com> wrote:
>>
>> On Tue, Feb 12, 2019 at 9:30 AM <tomas@tuxteam.de> wrote:
>>
>>> On Tue, Feb 12, 2019 at 09:10:08AM -0500, Kenneth Parker wrote:
>>> > I occasionally run, what I will describe as "Coffee House Lan Parties".
>>> > That means I connect to the Internet via WiFi, and then supply a "Local
>>> > Ethernet" network (with ipv4), for others to connect with.
>>> >
>>> > Doing this with Network Manager "worked", but only with "loud
>>> complaining"
>>> > by Network Manager.
>>> >
>>> > What I want now, are the "steps" that Network Manager takes, to bring
>>> up
>>> > WiFi, so I can create an "in-demand" Root-level Script that I can run,
>>> for
>>> > the WiFi part.  (The rest works fine, using /etc/network/interfaces).
>>>
>>> Actually ifupdown is perfectly capable of doing the work (well, it just
>>> orchestrates it, but it commes with all the necessary scripts for that).
>>>
>>> Here's my stanza in /etc/network/interfaces (passphrase somewhat
>>> decorated,
>>> to protect the innocent):
>>>
>>>   iface wlan0 inet dhcp
>>>     wpa-ssid dubcek
>>>     wpa-psk XXXXXXXXXXXXXXXX
>>>
>>> That's all it is needed for ifup to set up wlan0, go out with DHCP and
>>> fetch an IP address from our local DHCP server.
>>>
>>> Of course it relies on wpasupplicant and dhclient to do the actual
>>> magic behind the scenes.
>>>
>>
>> What did you have to do, the first time?  When you were determining the
>> Network Name (wpa-ssid)?  (Having to know everything in advance isn't too
>> cool,  when you visit multiple Coffee Houses. And connecting to the wrong
>> ssid could get you into some  *SERIOUS*  trouble!)
>>
>> I am doing my own investigation, by the way, finding general information
>> on a "competing" Distro (Arch):
>>
>>    https://wiki.archlinux.org/index.php/WPA_supplicant
>>
>> This site suggests that wpa_cli gives useful information,  so I will see
>> what that looks like, and then use your interfaces method.
>>
>> Enjoy simple life :-)
>>>
>>> Cheers
>>> -- t
>>>
>>
>> Thanks!
>>
>> Kenneth Parker
>>
>
> sudo iwlist wlan0 scan
>

Many Thanks.  Just what I needed!

<https://www.linuxjournal.comcontent/wi-fi-command-line
> <https://www.linuxjournal.com/content/wi-fi-command-line>>
>

And thanks for the link.  If they're still in business, they are worth my
Subscription!

Kenneth Parker

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

#205357

Hello,

- As a GUI alternative to NetworkManager; Wicd has been mentionned, but
there is also Connman
- the GUI part of NetworkManager (the gnome applet:
network-manager-gnome) is not mandatory: there are TUI (nmtui) and CLI
(nmcli) interfaces included in the NetworkManager base package
(network-manager)
- In my opinion, it would probably be simpler to use only NetworkManager
than NetworkManager and /etc/interfaces in your use case

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

#205237

On 2/12/19 7:10 AM, Kenneth Parker wrote:

> What I want now, are the "steps" that Network Manager takes, to bring up
> WiFi, so I can create an "in-demand" Root-level Script that I can run,
> for the WiFi part.  (The rest works fine, using /etc/network/interfaces).

How about (a non-auto entry from my interfaces file):

# wlan0 -- Get DHCP from Comcast and tidy up a bit
iface wlan0 inet dhcp
	wpa-ssid <SSID>
	wpa-psk <password>
	post-up /etc/sls/comcastRoutes.sh

comcastRoutes.sh is a shell script that fixes the routing table and
resolv.conf to set the default and DNS back to non-comcast IPs and to
enter some routes -- I use this for big downloads from the mirrors, etc.

"ifup wlan0" or "ifconfig wlan0 up" bring it up. And they don't turn off
my T1 Ethernet connection.

-- 
Glenn English

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

#205241 — Glenn -> Re: WiFi without Network Manager

On 2/12/2019 9:46 AM, ghe wrote:
> comcastRoutes.sh is a shell script that fixes the routing table and
> resolv.conf to


Glenn, thanks for this!

Is there much to comcastRoutes.sh and resolv.conf that would require 
scrubbing so that you might be able to share these?

(I'm on comcast as well; and I want to set this up too.)

Thanks

(still installing 9.7 ...)

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

#205248

On 2/12/19 9:15 AM, deb wrote:

> Glenn, thanks for this!

More than welcome.

For your amazement, here's the comcastRoutes.sh from my laptop, running
Buster. This is run just after the WiFi interface has been brought up
and Comcast has scribbled all over my IP files. It looks like maybe I'm
removing the default the twice on the WiFi...

#! /bin/bash

echo 'Adding Comcast routes'
route del default
route add default gw <theDefaultOnMyT1>

# Debian mirrors:
# picosecond
route add -host 184.105.204.138 gw 10.0.0.1 wlan0
# U-CHICAGO
route add -host 128.135.10.29 gw 10.0.0.1 wlan0
# MIT
route add -host 128.30.2.26 gw 10.0.0.1 wlan0
# Georgia Tech
route add -host 128.61.240.89 gw 10.0.0.1 wlan0
# Wikimedia
route add -host 208.80.154.15 gw 10.0.0.1 wlan0
	
route del default wlan0
route del -net 10.0.0.0 netmask 255.255.255.0

cp -a /etc/resolv.conf.sls /etc/resolv.conf

-- 
Glenn English

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

#205279

note: this is why I think top-posting is best.

People don't have to scroll through tons of crap to get to "Thanks" :-)


On 2/12/2019 3:07 PM, ghe wrote:
> On 2/12/19 9:15 AM, deb wrote:
>
>> Glenn, thanks for this!
> More than welcome.
>
> For your amazement, here's the comcastRoutes.sh from my laptop, running
> Buster. This is run just after the WiFi interface has been brought up
> and Comcast has scribbled all over my IP files. It looks like maybe I'm
> removing the default the twice on the WiFi...
>
> #! /bin/bash
>
> echo 'Adding Comcast routes'
> route del default
> route add default gw <theDefaultOnMyT1>
>
> # Debian mirrors:
> # picosecond
> route add -host 184.105.204.138 gw 10.0.0.1 wlan0
> # U-CHICAGO
> route add -host 128.135.10.29 gw 10.0.0.1 wlan0
> # MIT
> route add -host 128.30.2.26 gw 10.0.0.1 wlan0
> # Georgia Tech
> route add -host 128.61.240.89 gw 10.0.0.1 wlan0
> # Wikimedia
> route add -host 208.80.154.15 gw 10.0.0.1 wlan0
> 	
> route del default wlan0
> route del -net 10.0.0.0 netmask 255.255.255.0
>
> cp -a /etc/resolv.conf.sls /etc/resolv.conf


Thank you!

I'll give that a crack!

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

#205282

On Wednesday, February 13, 2019 08:32:22 AM deb wrote:
> note: this is why I think top-posting is best.
> 
> People don't have to scroll through tons of crap to get to "Thanks" :-)

I vary the use of top-posting and "bottom"-posting depending on circumstances.

For thanks and similar, top posting works very well.  In dealing with some 
other groups or "types" of people, top-posting works well (because, in many 
cases, it is what they expect or are used to).

On lists that prefer "bottom"-posting, I try to ususally comply, with 
exceptions.

In either case, I advocate quite extensive eliding of irrelevant parts of a 
post.

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

#205291

 deb wrote:
> note: this is why I think top-posting is best.  People don't have to
> scroll through tons of crap to get to "Thanks" :-)

When I open a message on a mailing list or newsgroup and see nothing but
quoted text I usually just move on to the next message.  On the other
hand I find top-posted responses that remain cryptic until I've scrolled
through a hundred lines of mostly-irrelevant quoted text a bit
irritating too.

It's better not to post "Thanks" to a busy mailing list.  If you must do
so please put "Thanks" in the subject line.

rhkramer writes:
> I vary the use of top-posting and "bottom"-posting depending on
> circumstances.
> ...
> On lists that prefer "bottom"-posting, I try to ususally comply, with
> exceptions.

> In either case, I advocate quite extensive eliding of irrelevant parts
> of a post.

I elide as required and interleave my response.  I recall only one
instance of someone objecting (on Usenet many years ago.)
-- 
John Hasler 
jhasler@newsguy.com
Elmwood, WI USA

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

#205302

On 2/13/19 9:14 AM, John Hasler wrote:
s better not to post "Thanks" to a busy mailing list.  If you must do
> so please put "Thanks" in the subject line.

OR "solved", which is much more useful for the next guy. No need for 
"thanks" as "solved" is the ultimate goal for posterity. It's what I 
look for in a google search to click on. Ric

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

#205284

On 2019-02-13 13:32, deb wrote:
> note: this is why I think top-posting is best.
> 
> People don't have to scroll through tons of crap to get to "Thanks" :-)
<snipped>

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

-- 
Key ID    4BFEBB31

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

#205280 — Swap space choice on a SSD <- Current best practice on?

Hello folks:

Again -- fussing with a full (not from a live .iso) 9.7 install; the 
Debian GUI installer is suggesting a Swap partition on a Kingston SSD.


#1 Given that it's not great to pound the same area of a SSD with 
writes; is it indeed still best practice to go with a swap partition on 
a SSD rather than a swap FILE?

(Or is this a legacy spinning hard disk install suggestion?)


#2 How DO you get the installer to go with a Swap FILE?

Just delete that recommended Swap partition during the install?


I looked; but did not run across any best practice docs for Swap on SSD.


Thank you

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web