On Sat, Nov 5, 2016 at 6:13 PM, Andras Simon wrote:
> On Nov 5, 2016 20:41, "Michael B Allen" wrote:
>> Can someone tell me how to disable this "helpful" behavior?
>
> Maybe the second half of this post:
>
> https://blog.onetechnical.com/2012/06/19/disab
I have two files:
SUM-12_schematic.pdf
VMware-Workstation-Full-10.0.1-1379776.x86_64.txt
Doing:
# ls SUM
works as expected and completes the filename but doing:
# sh -f VMw
does not work. The filename is not completed.
Clearly someone is trying to "help" me and not complete a file that sh
is
On Sat, Nov 5, 2016 at 7:11 AM, Louis Lagendijk wrote:
> It is a best practice to leave .local for mDNS. Even Microsoft
> recommends now against using .local https://en.wikipedia.org/wiki/.loca
> l offers some good information on the subject.
>
> And for DNS-domains you better use only officially
On Fri, Nov 4, 2016 at 8:54 PM, Michael B Allen wrote:
> The wireless routers use .local. I know for
> a fact the Verizon ones do and have for a long time.
Actually I have to retract this. I'm not sure routers use .local. Mine
is configure for .local but I may have just changed that
On Fri, Nov 4, 2016 at 8:39 PM, Matthew Miller wrote:
> On Fri, Nov 04, 2016 at 05:34:32PM -0400, Michael B Allen wrote:
>> Does anyone have a recommended work-around?
>
> AFAIK the only workaround would be in the program itself -- it would
> have to know to wait for somethin
On Fri, Nov 4, 2016 at 5:53 PM, Samuel Sieb wrote:
> On 11/04/2016 02:40 PM, Michael B Allen wrote:
>>
>> I don't think this was a MS thing. I recall .local being used a
>> lng time ago. It used to be that .local was absolutely the
>> recommended method
On Fri, Nov 4, 2016 at 5:02 PM, Rick Stevens wrote:
> On 11/04/2016 12:58 PM, Michael B Allen wrote:
>> I never understood these logical meta languages. Pam is another
>> example. It's basically just an obscure way of writing code so it's
>> not obvious to me why t
On Fri, Nov 4, 2016 at 5:13 PM, Tom H wrote:
> On Fri, Nov 4, 2016 at 10:38 PM, Michael B Allen wrote:
>> On Fri, Nov 4, 2016 at 4:24 PM, Samuel Sieb wrote:
>>> On 11/04/2016 12:58 PM, Michael B Allen wrote:
>>>>
>>>> Of course my local network is a .lo
I have been using this external editor command for the Sylpheed mailer:
gnome-terminal --disable-factory -x vim '%s'
This allows launching a terminal with vi so that I can capture shell
command output, edit things with vi and insert files and such. This is
a very powerful and important feature.
On Fri, Nov 4, 2016 at 4:24 PM, Samuel Sieb wrote:
> On 11/04/2016 12:58 PM, Michael B Allen wrote:
>>
>> Of course my local network is a .local domain so it seems at least in
>> my case mdns cannot really be used effectively.
>>
> Well, that right there is your prob
On Fri, Nov 4, 2016 at 2:36 PM, Rick Stevens wrote:
> On 11/04/2016 11:09 AM, Tom Horsley wrote:
>> On Fri, 4 Nov 2016 13:03:41 -0400
>> Michael B Allen wrote:
>>
>>> Is mDNS supposed to coexist with DNS?
>>
>> I have no idea what is "supposed"
Is mDNS supposed to coexist with DNS?
I have a proper DNS server but if I just try to ping an FQDN it tries
mDNS UDP 5353 which fails.
OTOH I just installed my printer and I'm guessing mDNS helped with
that so maybe mDNS is something I need?
I have no experience with mDNS but I am assuming that
On Thu, Nov 3, 2016 at 7:47 PM, stan wrote:
> On Thu, 3 Nov 2016 15:31:48 -0400
> Michael B Allen wrote:
>
>> I just tried to install F24 and everything went smoothly but after
>> reboot I just get "No bootable devices found".
>
> I think if this is a recent
I just tried to install F24 and everything went smoothly but after
reboot I just get "No bootable devices found".
I've been using Linux as my primary machine since kernel 2.0.35 and my
instinct tells me this looks like the bootloader wasn't installed
correctly.
Is this a known problem?
When I "r
I just got a Dell Latitude E7470. Mostly works with the latest Fedora live.
However, attaching an external monitor to the HDMI port hangs the
machine. I've been using Linux as my primary machine long enough to
know that it smells very much like a driver issue and that the only
way I'm going to get
On Thu, Oct 13, 2016 at 10:08 PM, Michael B Allen wrote:
> I'm trying to boot the latest Fedora Live iso on a brand new Dell and
> I'm getting:
>
> Selected boot device failed
>
> What is the trick to getting this to boot?
>
> I just dd'd the iso on the US
I'm trying to boot the latest Fedora Live iso on a brand new Dell and
I'm getting:
Selected boot device failed
What is the trick to getting this to boot?
I just dd'd the iso on the USB drive. Do I need to make it bootable or
some such?
I updated the BIOS to the latest. I verfied everything wo
17 matches
Mail list logo
