trouble shooting print errors
I am getting "Broken Pipe" and or "Scheduler not responding" when attempting to print from a laser desk printer directly attached to usb. OpenBSD 6.0 recognizes the printer in dmesg and when plugged into the usb port. I have been running OpenBSD for several years but never tried to attach a printer. I also have downloaded a cups ppd driver for the printer and placed it in the cups ppd directory. If someone can just point me where to research these errors I should be able to determine the cause and maybe get the brother HL2140 directly attached usb printer working. I see no error messages in dmesg which relate to printing. Thanks in advance.
people manager
I use abook . Fast simple easy to configure and works with mutt. :)
Re: text-mode gui
On Tue, Dec 22, 2015 at 11:04:28AM +0100, Christoph R. Murauer wrote: > > You are a normal user and have full disk encryption. You must have > > read the man page on how to do that? > > I was curious and asked my favourite search engine for *openbsd full > disc encryption* and got results like > http://www.bsdnow.tv/tutorials/fde, readed them and found the needed > commands. Yes, after that I looked in the man page what the people > there had done. > > > Found the installer option did you. > > Don't know, what you exactly mean. > > > I have read several books on openbsd and all the man pages I could > > find and didn't find out how to do it anywhere else other that how to > > webpages. > > Really, *Absolute OpenBSD - Unix for the practical paranoid, second > edition* page 166 *Encrypted Disk Partitions*, page 167 the bioctl > command including required switches. > > IMHO you wrote on 2015-12-21 (taken from marc.info) *I can do that. [ > ... ] Easy Peasy!* - the community and the developers will judge you > based on your words. If you don't hold your promise, you have earned > the virtual kick in the ass. > > I can't understand why anyone especially those who profess to have accomplished this or that in (C) Class or working towards a degree, assisting a professor or software engineer would suggest such non-sense. OpenBSD is the simpliest installer I've seen. If I want to do more beyond the standard install, post install information is easy to understand. I can re-install (about 3 min) and make the adjustments that I didn't think of earlier. A product of "common core" Hear Hear Schz! Can someone put a fork in this subject! (dungeon quest) Ha!, I like it!
Re: text-mode gui
On Sun, Dec 20, 2015 at 04:29:37PM +0200, li...@wrant.com wrote: > On Sun, 20 Dec 2015 10:51:20 + Tati Chevron > wrote: > > > On Sat, Dec 19, 2015 at 05:34:59PM -0600, Luke Small > > wrote: > > > > > >If installer GUIs are bad, maybe features like full-disk encryption > > >could be accomplished via lynx-like text -based HTML and/or > > >JavaScript that could write to cookies that the installer could > > >parse into commands? > > > > There are much better ways to implement text-based menu systems than > > using... > > Mentioning menu systems is an incorrect idea too, read bellow. > > First, what is this mythical "text-mode gui"? A text mode garbled user > interface, a new oxymoron of textual and graphical interfaces in the > same definition, or another gaseous non oxygen based substance? > > Probably, global usability inheritance, right? > > Usability means then it should be not only humans but also programs > who are able to interact with the installer. So, since stream editors > know nothing about this seasons' (or Luddite's) line drawing symbols, > and users barely see the information between these on another terminal > capability controlled device, just and only: > > plain line oriented interface works > > Meaning, this has been one unnecessary (if not totally ridiculous) > suggestion to begin with, followed by another one such "gold" nugget. > > Current installer is the gold standard in usability and the addition of > automatic installation & upgrade capabilities proved that already. > > http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/autoinstall.8 > > Totally agree :)
no mail/reports following power failure
Hi Folks New here. Running ver 5.8 on an ibme330 sever. Usually get daily reports for disk usage etc vial mail system on server. Following a power interruption I get no more local mail as user or as Root. Have checked the mail files in etc/mail and run newaliases as root. The mail files appear to be ok according to the man pages for related files in /etc. I have shut the server down and restarted with still no mail delivery locally on lo0 Is there something to re-start in the daily scheduling system cron? .or. can someone point me in a general direction for docs to look at. Thanks in advance
Re: Because Theo and various users told them that the projects GnoBSD and Comixwall were worthless and that they weren't contributing to OpenBSD?
On Sat, Oct 17, 2015 at 06:59:32AM -0700, français wrote: > I always find it amusing how OpenBSD is "audited", yet there's not one audit > report on the OpenBSD website. The closest answer I've been able to find on > the mailing list is to review all of the CVS commit logs. Yeah, that's not > opaque in the slightest... > > The bigger problem with OpenBSD is it's community. In the FreeBSD world, you > have PC-BSD and pfsense, both of which are generally welcomed by the > community. With OpenBSD, there were two sister projects that tried to target > a similar audience: GnoBSD and Comixwall. Comixwall was the equivalent of > pfsense for easy router/firewall management and GnoBSD was an attempt to > make an easy-to-use desktop. Both, however, ended up shutting down after > Theo and various users told them that their projects were worthless and that > they weren't contributing to OpenBSD. > > Because Theo and various users told them that their projects were worthless > and that they weren't contributing to OpenBSD? > > > > -- > View this message in context: > http://openbsd-archive.7691.n7.nabble.com/Because-Theo-and-various-users-told-them-that-the-projects-GnoBSD-and-Comixwall-were-worthless-and-t-tp280374.html > Sent from the openbsd user - misc mailing list archive at Nabble.com. > > Well maybe!. Why don't you write some code instead of expressing an opinion here that won't get you a cup of coffee. No matter what, "OpenBSD" has been providing the world a free BSD for a long timeDosen't that speak for itself ? Do you use it? Fine contribute...If not, why waste your time here...??? my humble opinion.. :)
Re: CD's arrived
Arrived in Texas USA today
httpd
Swapped over from Apache to httpd recently. Nice simple, easy to set-up httpd.conf file. The system works very well with our virtual static sites. Thanks Developers :)
Re: issue with pf syntax parser
On Fri, Sep 04, 2015 at 05:49:34PM -0600, Theo de Raadt wrote: > > > --- /usr/share/man/man5/pf.conf.5 Wed Mar 5 16:22:58 2014 > > > +++ var1/man5/pf.conf.5 Thu Sep 3 16:19:21 2015 > > > @@ -63,7 +63,7 @@ A method for detecting a host's operating system. > > > Some example rulesets. > > > .El > > > .Pp > > > -The current line can be extended over multiple lines using a backslash > > > +The current line can be extended over multiple lines using a > > > backslash-newline > > > .Pq Sq \e . > > > Comments can be put anywhere in the file using a hash mark > > > .Pq Sq # , > > I would recommend: > > The current line can be extended over multiple lines using a backslash > > without trailing white space. > > > > I agree with later posts that nothing needs to be done to the parser. I > > have experienced the same error and wished it would give me the line > > number, but somehow I managed to find the mistake. > > The sh man page, for instance, does not mention the problem with spaces > either: > > A backslash in the input line causes the shell to prompt for further > input. > > Yet millions of people have gotten by with reading and writing shell > scripts. > > The same situation in for C. > > So maybe we should wait until the exact same "improvement proposals" > arrive for the shell, the C language, and all the other programs that > behave in the same way? > > Or the OP should admit they simply don't know unix. Yes, unix is > something you have to learn. There is not different from anything > else in life. I think it is pretty outrageous to suggest a few extra > words (term I use is "over-documentation") would have avoided this grief > in the first place. That is rewriting history; I am certain the OP > only is complaining after the fact. > > This is not OpenBSD folk being mean. Very few people learn to ride a > bicicle without a scrape or two. Stop whining, and get back on the > bike. > > The documentation is sufficient. > > Yep, and all I have in learning OpenBSD is scrapes and scratches, and bloody bruises. But, it is the way to learn!, besides like mentioned earlier (estimate 99.9+) of BSD users are already used to the parser, or the way it behaves in other nix process's. No change needed would be my 2 cents. :)
Re: IPKVM or ...?
Wouldn't "ILO" technology which is standard on hp or ibm commercial server's do the trick ? On 07/13/2014 01:28 PM, frantisek holop wrote: hmm, on Sun, Jul 13, 2014 at 06:38:52PM +0200, Mxher said that Le 13/07/2014 18:11, frantisek holop a ?crit : i am looking for a device that would let me reboot my remote server in case it becomes unresponsive. the server is hosted at a private company far-far away. we are talking about off-the-shelf, "noname" pc servers, so i am not looking for anything fancy. seeing the console is a plus, but i can live without that. and of course it should work with openbsd :] any success stories more than welcome. -f A KVM/IP could do the trick but in some case, for example kernel panic, you will be stuck I think. is it not possible to reboot if ddb.panic=1 ? Another solution available (if you have two servers near by) could be to redirect consoles to serial ports nope, just one box Intel AMT / vPro could help too but I guess this "noname" server doesn't have that kind of technology. i am also looking into IPMI, as my current server is rather old, and i may end up buying a new machine. Maybe you could take a look at something which seems called "Network AC Power Controller". very interesting but looks rather pricey. -f
