I'm running Salix lxde after installing from the v13.1.1 live CD. For connectivity dialup is my option, and got that going as expected with pppsetup. Connects and pings the the remote IP fine and 127.0.0.1 fine. This lxde bundle has the Midori v0.2.7 browser. I find this will not load any pages over the wire with <unable to resolve hostname> the message. HTML files from HDD display fine. I thought Midori could have an offline mode like other browsers, yet do not find such in the menus or preferences. I switched the proxy preference from auto to none back to auto, to no avail.
Is there some simple thing that got by me here? Do Midori and dialup not mix? Midori v0.3.3 works for Bodhi Linux on this same box.
Marj
midori hostname fail on dialup
Re: midori hostname fail on dialup
You probably need this for /etc/resolv.conf:
http://www.salixos.org/wiki/index.php/U ... d_dialling
http://www.salixos.org/wiki/index.php/U ... d_dialling
Re: midori hostname fail on dialup
Thanks, that got me looking in the right place, and I blundered through the rest. Midori does not figure into it at all; this became apparent when
slapt-get --update
choked, again owing to hostname not resolved. I'd already posted the forum before that attempt.
When I originally worked through the pppsetup utility, I lacked the nameserver info (my ISP not timely telling this) so I left it blank. The script only wrote /etc/resolv.conf (no /etc/ppp/resolv.conf found) which just has three comment lines generated by dhcpcd. Of course that was a no go. Fixed it by looking at the resolv.conf in Bodhi (that works) and writing those values into /etc/resolv.conf and /etc/ppp/resolv.conf.
All is now jolly. Though it did take a few hours for
slapt-get --upgrade
to pull down 58M. Aren't modems great? Not really you say? No matter, had it do the job while I was on the town
Marj
-----edit---
For the other two people on dialup, there is another gotcha. I learned the OS overwrites /etc/config when you start your computer again.
Contents were the following lines:
# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line
To be ready for this in future, I created /etc/resolv.conf.head containing
search ISP_URL
and also created /etc/resolv.conf.tail containing
nameserver first_ISP_IP_number
nameserver second_ISP_IP_number
That way, when dhcpcd rewrites resolv.conf, it just puts back the stuff I needed anyway. If you do this, substitute the IPs and URL of your provider, and you should be all set.
slapt-get --update
choked, again owing to hostname not resolved. I'd already posted the forum before that attempt.
When I originally worked through the pppsetup utility, I lacked the nameserver info (my ISP not timely telling this) so I left it blank. The script only wrote /etc/resolv.conf (no /etc/ppp/resolv.conf found) which just has three comment lines generated by dhcpcd. Of course that was a no go. Fixed it by looking at the resolv.conf in Bodhi (that works) and writing those values into /etc/resolv.conf and /etc/ppp/resolv.conf.
All is now jolly. Though it did take a few hours for
slapt-get --upgrade
to pull down 58M. Aren't modems great? Not really you say? No matter, had it do the job while I was on the town
Marj
-----edit---
For the other two people on dialup, there is another gotcha. I learned the OS overwrites /etc/config when you start your computer again.
Contents were the following lines:# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line
To be ready for this in future, I created /etc/resolv.conf.head containing
search ISP_URL
and also created /etc/resolv.conf.tail containing
nameserver first_ISP_IP_number
nameserver second_ISP_IP_number
That way, when dhcpcd rewrites resolv.conf, it just puts back the stuff I needed anyway. If you do this, substitute the IPs and URL of your provider, and you should be all set.