On 10/02/2016 5:51 AM, Jeremy Boy wrote:
Hello list,
please CC me in replies to this mail, since I am no subscriber to this list.
For safety reasons, we enclose user input to shell commands in quotes. Until
today, the resulting command for ifconfig(8) looked like this:
ifconfig ue0 inet "192
On Wed, Feb 10, 2016 at 12:23 AM, Eugene Grosbein
wrote:
> On 10.02.2016 04:51, Jeremy Boy wrote:
> > Hello list,
> >
> > please CC me in replies to this mail, since I am no subscriber to this
> list.
> >
> > For safety reasons, we enclose user input to shell commands in quotes.
> Until today, th
On 10.02.2016 04:51, Jeremy Boy wrote:
> Hello list,
>
> please CC me in replies to this mail, since I am no subscriber to this list.
>
> For safety reasons, we enclose user input to shell commands in quotes. Until
> today, the resulting command for ifconfig(8) looked like this:
>
>> ifconfig u
Hello list,
please CC me in replies to this mail, since I am no subscriber to this list.
For safety reasons, we enclose user input to shell commands in quotes. Until
today, the resulting command for ifconfig(8) looked like this:
> ifconfig ue0 inet "192.168.2.176 netmask 255.255.255.0"
As we