Hello freebsdquestions
Hello freebsdquestions i havent seen anything work as well as this on the first try http://bitly.com/13C7n5L quit your nine to five in three weeks or less guaranteed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Organic SEO: Freebsd.Org : MT
div dir=ltrp style=color:rgb(34,34,34);font-family:arial;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px span style=font-size:14ptDear Freebsd.Org Team,/span/pp style=color:rgb(34,34,34);font-family:arial;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px span style=font-size:14ptI thought you might like to know some of the reasons why you are not getting enough Organic search and engine Social Media traffic forspan /spanspanFreebsd.Orgb./b/span/span/p p style=color:rgb(34,34,34);font-family:arial;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin-left:0.5in span style=font-size:14ptspan1.span style=font-style:normal;font-variant:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:#39;Times New Roman#39;span /span/span/span/spanspan style=font-size:14ptYour website Freebsd.Org is not ranking top in Google organic search for many competitive keywords./span/p p style=color:rgb(34,34,34);font-family:arial;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin-left:0.5in span style=font-size:14ptspan2.span style=font-style:normal;font-variant:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:#39;Times New Roman#39;span /span/span/span/spanspan style=font-size:14ptYour website profile needs to have regular update in major Social Media sites./span/p p style=color:rgb(34,34,34);font-family:arial;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;margin-left:0.5in span style=font-size:14ptspan3.span style=font-style:normal;font-variant:normal;font-weight:normal;font-size:7pt;line-height:normal;font-family:#39;Times New Roman#39;span /span/span/span/spanspan style=font-size:14ptYour site has less number of Google amp; Yahoo back links, this can be improved further./span/p p style=color:rgb(34,34,34);font-family:arial;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px span style=font-size:14ptThere are many additional improvements that could be made to your website, and if you would like to learn about them, and are curious to know what our working together would involve, then I would be glad to provide you with a detailed analysis in the form of a bWEBSITE AUDIT REPORT for FREE/b./span/p p style=color:rgb(34,34,34);font-family:arial;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px span style=font-size:14ptOur clients consistently tell us that their customers find them because they are at the top of the Google search rankings. Being at the top left of Google (#1- #3 organic positions) is the best thing you can do for your company#39;s website traffic and online reputation./span/p p style=color:rgb(34,34,34);font-family:arial;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px span style=font-size:14ptOur packages are designed for a complete advance SEO experience which includes SMO, Brand management, Reputation management, SEO etc. in order to beat your competitors./spanspan style=font-size:14pt/span/p p style=color:rgb(34,34,34);font-family:arial;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px span style=font-size:14ptSounds interesting? Feel free to email us or alternatively you can provide me with your phone number and the best time to call you./span/pp style=color:rgb(34,34,34);font-family:arial;font-size:small;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px span style=line-height:21px;font-size:14pt--WBRbr/spanspan
Updating broken link from your page: http://www.freebsddiary.org/polls.php
Hello, I have bumped into your site while seeking for software and found your website very interesting :) Just a quick note, http://www.phpwizard.net/ is no longer active, and you are linking to it from page - http://www.freebsddiary.org/polls.php I was wondering if you don't mind updating the link to the updated website en.DownloadAstro.com (http://en.downloadastro.com/) - A great download site with more than 300K software and games, including professional reviews and user ratings. We are now in a process of updating the links in websites all around the world and I will appreciate your cooperation. I am sure your users will find it useful. Thanks, Lurie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dig
On Thu, 22 Aug 2013 11:14:04 +1000 Colin House articulated: On 22/08/2013 9:34 AM, Doug Hardie wrote: There appears to be a problem with dig and the +trace option in 9.2. I believe its also in 9.1. The command: dig freebsd.org +trace Only yields a dumb response. No useful information is provided. Running the same command on FreeBSD 7.2 yields a complete trace with lots of useful information. Have you tested against another NS? I ran into a similar problem when setting up unbound as a local recursor recently on a 9.1-STABLE (r251985) box. dig +trace domain would return (next to) nothing. dig +trace domain @8.8.8.8 worked as expected. I found it was the access-control configuration of unbound. Changing my access-control: ::1 allow to access-control: ::1 allow_snoop restored the +trace functionality. I'm not sure how this translates with bind.. Perhaps the defaults have changed between the versions that you're running (if you're running the base versions on 7.2 and 9.1) or your recursive server isn't allowing it on 9.2? Fwiw, in unbound, allow allows recursive lookups, allow_snoop allows both recursive and non-recursive lookups. $ dig freebsd.org +trace ; DiG 9.6.-ESV-R7-P2 freebsd.org +trace ;; global options: +cmd ;; Received 12 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms $ drill freebsd.org +trace ;; -HEADER- opcode: QUERY, rcode: NOERROR, id: 28341 ;; flags: qr rd ra ; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;; +trace. IN A ;; ANSWER SECTION: +trace. 10 IN A 69.16.143.110 +trace. 10 IN A 66.152.109.110 ;; AUTHORITY SECTION: ;; ADDITIONAL SECTION: ;; Query time: 34 msec ;; SERVER: 209.18.47.62 ;; WHEN: Thu Aug 22 06:35:54 2013 ;; MSG SIZE rcvd: 56 I was surprised at the difference between the output of the two commands. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setup HP Laserjet 1120m over network with LPD
finally my printer responds with this command: nc 192.168.1.105 9100 output.xqx but I have no idea how to get it running through the normal LPD spooling system. output.xqx file I generate first with the foo2xqx-wrapper filter and it accepts only postscript i tried this printcap entry: HP|lp|Printer:\ :lp=9100@192.168.1.105:\ :sh:\ :mx#0:\ :sd=/var/spool/hp:\ :if=/usr/bin/foo2xqx-wrapper:\ :lf=/var/log/lpd-errs: but in the Status file i have: waiting for 9100@192.168.1.105 to come up btw: gsed package was not mentioned as dependency for foo2xqx-wrapper in the Installation Notes ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setup HP Laserjet 1120m over network with LPD
El día Thursday, August 22, 2013 a las 03:43:46PM +0300, Juris Kaminskis escribió: finally my printer responds with this command: nc 192.168.1.105 9100 output.xqx I can't imagine that LPD port 515 is not supported by the printer; what telnet 192.168.1.105 515 gives? If this is timing out, I would rather think in firewall issue; if you really need to print raw to port 9100, with CUPS you would just configure it through CUPS' web inteface as socket://192.168.1.105:9100/?waiteof=false or on command line with # lpadmin -U root -p myprinter -D '' -L '' -E -v \ 'socket://192.168.1.105:9100/?waiteof=false' -P file.ppd HIH matthias -- Sent from my FreeBSD netbook Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ f: +49-170-4527211 UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setup HP Laserjet 1120m over network with LPD
I can't imagine that LPD port 515 is not supported by the printer; what telnet 192.168.1.105 515 gives? telnet 192.168.1.105 515 Trying 192.168.1.105... Connected to NPI2B483C. Escape character is '^]'. port 515 is not accepting file directly, when I tried the output.xqx to this port nothing happened, only 9100 accepts If this is timing out, I would rather think in firewall issue; if you really need to print raw to port 9100, with CUPS you would just configure it through CUPS' web inteface as How in CUPS i will be able to use foo2xqx-wrapper, plus I am planning to add smart apsfilter from ports on top . I would like that all print jobs are converted first by apsfilter into postscript, then foo2xqx-wrapper makes them compatible for HP and finally I ship this data over network to my printer generally i would prefer to stick with the native freebsd printing system which is LPD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setup HP Laserjet 1120m over network with LPD
On Thu, Aug 22, 2013, at 8:19, Juris Kaminskis wrote: generally i would prefer to stick with the native freebsd printing system which is LPD As you should! CUPS is horrible... I also use apsfilter. I can print almost any file I want just by doing lpr filename apsfilter's generated config required some hand tweaking by me, but here's an example I'll drop for you: /etc/printcap: netlaser|netlaser;r=600x600;q=medium;c=gray;p=letter;m=auto:\ :lp=9100@netlaser:\ :if=/usr/local/etc/apsfilter/basedir/bin/apsfilter:\ :sd=/var/spool/lpd/netlaser:\ :lf=/var/spool/lpd/netlaser/log:\ :af=/var/spool/lpd/netlaser/acct:\ :mx#0:\ :sh: /etc/hosts: 192.168.94.5 netlaser /usr/local/etc/apsfilter/netlaser/apsfilterrc: # # don't delete these settings # PRINTER='PS' PAPERSIZE='letter' METHOD='auto' QUALITY='medium' COLOR='gray' RESOLUTION='600x600' # apsfilter as jukebox # important if audio playback device is a network print queue # INTERFACE='network' INTERFACE='network' And then I think I just had to create /var/spool/lpd/netlaser with ownership root:daemon and 755 After that I think restarting lpd and it just works? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setup HP Laserjet 1120m over network with LPD
not sure what exactly did the trick either restart of LPD, or removing Hplip and CUPS packages, but now my printer responds via: lpr test.ps Success! Thank you very much to everyone! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Finding exactly which commands, and in which order, rc is running at startup
Greetings again. After doing a freebsd-update, my system is starting up differently than it was before. I want to figure out why before I come here and say it's broken. Is there a way to say show me all of the commands you are running during startup? It would be grand if I could say tell me what you would do next time (dry run), but what did you do last time is OK too. --Paul Hoffman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Setup HP Laserjet 1120m over network with LPD
On Thu, 22 Aug 2013, Juris Kaminskis wrote: finally my printer responds with this command: nc 192.168.1.105 9100 output.xqx Okay, that's a good start. but I have no idea how to get it running through the normal LPD spooling system. output.xqx file I generate first with the foo2xqx-wrapper filter and it accepts only postscript That is considered normal for Unix printers. If you want the complexity of a filter that autodetects input type, save adding that for later. i tried this printcap entry: HP|lp|Printer:\ :lp=9100@192.168.1.105:\ :sh:\ :mx#0:\ :sd=/var/spool/hp:\ :if=/usr/bin/foo2xqx-wrapper:\ :lf=/var/log/lpd-errs: but in the Status file i have: waiting for 9100@192.168.1.105 to come up Do not use IP addresses. lpd really, really, *really* wants a resolvable hostname. Entering it in /etc/hosts is enough, then use that name above. btw: gsed package was not mentioned as dependency for foo2xqx-wrapper in the Installation Notes Depending on where those notes are, that should be mentioned to the author of the notes or the port maintainer. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dig
On 21 August 2013, at 18:14, Colin House co...@restecp.com wrote: On 22/08/2013 9:34 AM, Doug Hardie wrote: There appears to be a problem with dig and the +trace option in 9.2. I believe its also in 9.1. The command: dig freebsd.org +trace Only yields a dumb response. No useful information is provided. Running the same command on FreeBSD 7.2 yields a complete trace with lots of useful information. Have you tested against another NS? I ran into a similar problem when setting up unbound as a local recursor recently on a 9.1-STABLE (r251985) box. dig +trace domain would return (next to) nothing. dig +trace domain @8.8.8.8 worked as expected. I found it was the access-control configuration of unbound. Changing my access-control: ::1 allow to access-control: ::1 allow_snoop restored the +trace functionality. I'm not sure how this translates with bind.. Perhaps the defaults have changed between the versions that you're running (if you're running the base versions on 7.2 and 9.1) or your recursive server isn't allowing it on 9.2? Fwiw, in unbound, allow allows recursive lookups, allow_snoop allows both recursive and non-recursive lookups. After a bunch of testing, I have determined that the problem is the routers. If I use my local DNS servers or remote ones, then it works on all three systems. Three different routers block it somehow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
kern_jail_set() Error Scenario Question
We ran into the following scenario in an application recently and were
wondering if the behavior of kern_jail_set() is as expected here.
This was an application bug where we were in, say, the JID 1 context
and tried to call jailparam_set() with the flags (JAIL_CREATE |
JAIL_UPDATE) and the jid param set to 1. The basic idea was to
create or update JID 1 with some params, but the error was we were
already in the JID 1 context. So, our understanding is this shouldn't
work since JID 1 already exists and you can only modify it from a
proper ancestor.
However, rather than getting an error back from jailparam_set(), it
ended up creating a second prison with JID 1, so there were two
prisons existing with JID 1 at that point. This is based on 8.2.0
code, but, at first glance, it looks like the logic causing this may
be the same in head.
Looking at kern_jail_set(), what happens here is:
1. We find a prison with JID=1, however since it's not a proper child
we set pr = NULL in line 1024:
1011 pr = prison_find(jid);
1012 if (pr != NULL) {
1013 ppr = pr-pr_parent;
1014 /* Create: jid must not exist. */
1015 if (cuflags == JAIL_CREATE) {
1016 mtx_unlock(pr-pr_mtx);
1017 error = EEXIST;
1018 vfs_opterror(opts, jail %d
already exists,
1019 jid);
1020 goto done_unlock_list;
1021 }
1022 if (!prison_ischild(mypr, pr)) {
1023 mtx_unlock(pr-pr_mtx);
1024 pr = NULL;
1025 } else if (pr-pr_uref == 0) {
2. Since pr is NULL, we create a new prison. Since the jid is not
zero, we insert it in the list and set its pr_id. At this point, we
have two prisons with a JID of 1 and the same parent prison.
1166 /* If there's no prison to update, create a new one and
link it in. */
1167 if (pr == NULL) {
...
1185 pr = malloc(sizeof(*pr), M_PRISON, M_WAITOK | M_ZERO);
1186 if (jid == 0) {
...
1212 } else {
1213 /*
1214 * The jail already has a jid (that did
not yet exist),
1215 * so just find where to insert it.
1216 */
1217 TAILQ_FOREACH(tpr, allprison, pr_list)
1218 if (tpr-pr_id = jid) {
1219 TAILQ_INSERT_BEFORE(tpr,
pr, pr_list);
1220 break;
1221 }
1222 }
...
1229 pr-pr_parent = ppr;
1230 pr-pr_id = jid;
We wanted to see if this is per design or a situation that should
avoid creating the second prison and return an error.
Thanks,
Matt
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ipfw confusion
On 08/20/13 12:41, Dan Lists wrote: You might turn on logging and post the logs of what is being blocked. Sometimes things are being blocked by rules you do not expect. Thanks for the suggestion. I was seeing refusals from named and mistakenly interpreting them as ipfw issues. On Mon, Aug 19, 2013 at 4:18 PM, Gary Aitken vagab...@blackfoot.net wrote: On 08/19/13 00:36, Jason Cox wrote: Are you sure that your DNS requests are over TCP? DNS primarily uses UDP to serve requests. TCP is used when the response data size exceeds 512 bytes (I think), or for tasks such as zone transfers. I know a few resolver implementations use TCP for all queries, but most I have used not. You might want to add rules to allow UDP as well. There are identical rules included for udp: 21149 allow udp from any to 12.32.44.142 dst-port 53 in via tun0 keep-state 21169 allow udp from any to 12.32.36.65 dst-port 53 in via tun0 keep-state One of the requests which is being refused is a zone transfer request from a secondary which is a tcp request. Others are probably udp. On Sun, Aug 18, 2013 at 11:06 PM, Gary Aitken vagab...@blackfoot.net wrote: I'm having some weird ipfw behavior, or it seems weird to me, and am looking for an explaination and then a way out. ipfw list ... 21109 allow tcp from any to 12.32.44.142 dst-port 53 in via tun0 setup keep-state 21129 allow tcp from any to 12.32.36.65 dst-port 53 in via tun0 setup keep-state ... 65534 deny log logamount 5 ip from any to any tail -f messages Aug 18 23:33:06 nightmare named[914]: client 188.231.152.46#63877: error sending response: permission denied 12.32.36.65 is the addr of the internal interface (xl0) on the firewall and is the public dns server. 12.32.44.142 is the addr of the external interface (tun0) which is bridged on a dsl line. It appears that a dns request was allowed in, but the response was not allowed back out. It seems to me the above rules 21109 and 21129 should have allowed the request in and the response back out. It's possible a request could come in on 12.32.44.142, which is why 21109 is present; although I know I am getting failures to reply to refresh requests from a secondary addressed to 12.32.36.65 What am I missing? Is there a problem if the incoming rule is for tun0, which gets passed to named since 12.32.44.142 is on the physical machine running named, but named pumps its response out on 12.32.36.65, relying on routing to get it to the right place, and that fails to match the state tracking mechanism which started with 12.32.44.142? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
hugin?
Is anyone using the current port of hugin successfully on 9.1? I've never used it before but an attempt to start it crashes: $ hugin /usr/local/share/hugin/data/plugins/top_five.py CAT:Control Points NAM:keep 5 CPs per image pair /usr/local/share/hugin/data/plugins/woa.py CAT:Control Points NAM:Warped Overlap Analysis /usr/local/share/hugin/data/plugins/shooting_pattern.py CAT:initial distribution NAM:6-1-1 Shooting Pattern /usr/local/share/hugin/data/plugins/crop_cp.py CAT:Control Points NAM:Crop Control Points Segmentation fault: 11 (core dumped) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
