Re: Help, please, understanding AHCI error on amd64
It seems that after reading the backblaze and google papers about drive reliability that there is no statistically obvious difference. It's too close to call. Both papers end with hedges and further questions. Even if enterprise drives are more reliable it isn't by more than a single percent and it isn't consistent enough to matter either. Evan Root, CCNA On Thu, Aug 28, 2014 at 1:40 PM, Chris Cappuccio wrote: > Christian Weisgerber [na...@mips.inka.de] wrote: > > > > Now, the real question is whether enterprise drives actually *are* > > more reliable than consumer drives. > > > > For regular hard disks, the answer is definitely, no.
Re: Migrate to SSD
Check out softdep as a fstab parameter. It is equally useful for regular spinning disks but it seems like you may not know about Soft updates. Evan Root, CCNA On Thu, Jan 2, 2014 at 8:27 AM, Jan Stary wrote: > On Jan 02 09:41:14, laurence.rochf...@gmail.com wrote: > > Hello, > > > > I want to migrate my current OpenBSD 5.4 installation to an SSD, which is > > slightly larger than my present rotational drive. > > > > What are people's suggestions for doing this? I was thinking of DDing and > > increasing the size of /home and /usr/local, but surely there's a better > > way? > > Unless your installation is very specific and there is something > precious beside /home and /etc/, just do a dump, install, restore. > > > Also, are there any /etc/fstab options recommended for SSDs? > > None which you wouldn't use for a classical disk as well.
Re: dmassage - openbsd 5.4 build failure
Riccardo, How much memory does the Omni 800 have right now? Evan Root, CCNA On Wed, Jan 1, 2014 at 6:46 PM, Theo de Raadt wrote: > >On Wed, Jan 1, 2014, at 06:17 PM, Theo de Raadt wrote: > >> I think dmassage being unmaintained for 12 years, and this issue just > >> coming up now, probably says a lot about that "type" of person. It's > >> a type of person who can't fix dmassage, and then, sends us a mail. > >> Sorry, but it's the truth. > > > >Very little, if anything, has changed in either the kernel configuration > >procedure or the format of a kernel's dmesg in the last 12 years. So > >this is more a case of "if it ain't broke, don't fix it." > > So glad to have the expert speak.
Re: Is Ext2 stable enough for normal use?
Just so you all know, This thread makes me want to try out Ext on Openbsd reeeaalll bad. I might just be able to provide real answers about how it works here in a couple weeks. Evan Root, CCNA On Sat, Dec 21, 2013 at 1:13 AM, Maurice McCarthy wrote: > On Thu, Dec 19, 2013 at 05:04:32AM -0600 or thereabouts, Shawn K. Quinn > wrote: > > > > I know for a fact that on GNU/Linux, NTFS performance is terrible, > > especially on larger files. True story: once I tried backing up > > something as a large .zip file to NTFS on a GNU/Linux system. The ETA > > would start off saying something reasonable like "3 hours" then, three > > hours later, it would be "about 8 hours" and it would keep going up from > > there. > > > > Shawn Quinn, I take it all back. The performance on ntfs in Ubuntu 13.04 > is atrocious with large files. > > The tar archive of video that I mentioned before had _not finished after > 5:01 hours but took another 5 hours to complete. > > So to verify I tried a plain copy command between two internal hardisks. > After the first 7G transfer had decreased to under 200K per sec. My home PC > has 8G of RAM. > > Regards > Maurice
Re: Is Ext2 stable enough for normal use?
Tekk, The compatibility between linux ext and unix ufs (aka ffs in 4.4BSDs) is terrible. Both the linux kernel developers think ufs is a quagmire and the BSD kernel folks don't use extX so they don't really know if it works. Google Unix File System and hit the wikipedia article which explains how this mess was evolved into being. I have a perverted solution, use fat32. It's failures are very well understood. Evan Root, CCNA On Tue, Dec 17, 2013 at 8:01 AM, Donald Allen wrote: > On Tue, Dec 17, 2013 at 5:10 AM, Shawn K. Quinn > wrote: > > On Mon, Dec 16, 2013, at 05:26 PM, Donald Allen wrote: > >> On Mon, Dec 16, 2013 at 5:48 PM, Tekk wrote: > >> > I've got an ext3 /home partition which I use under linux, how likely > is > >> > it that files will get clobbered if I use the same /home under a dual > >> > boot with openbsd? > >> > > >> > >> Your subject asks about the stability of the ext2 support in OpenBSD, > >> but your message says you have an ext3 partition you want to access. > >> ext2 and ext3 are not the same thing -- ext3 is a journaled variant of > >> ext2 that OpenBSD does not support. See > >> > >> http://www.openbsd.org/faq/faq9.html > >> > >> Don't do it. > > > > My understanding is read/write access is considerably more risky than > > read-only access. If you just need to read that /home under OpenBSD it's > > much less complicated and less risky as you can just mount /home > > read-only and be done with it (even if it's still ext3). > > > > At minimum, if you insist on read-write, you should get rid of the > > journal thus converting ext3 back to ext2. It's a Really Bad Idea to > > mount ext3 as ext2 read-write unless you are extra careful to shut down > > cleanly every time and even then it's dubious. > > > > It *might* be less risky if you format that /home as FFS and access it > > using the Linux kernel's UFS/FFS module. Or, you could simply keep > > separate /home for GNU/Linux and OpenBSD, which to me is perhaps the > > cleanest solution. (I tend to compile a lot of stuff and install it to > > $HOME/bin when I don't want it cluttering up /usr/local/bin which is > > something I will admit a lot of users probably don't do.) > > ext2 is a side line for OpenBSD, not used as much and therefore not as > well-tested as the ffs code. The same is true for Linux, exchanging > ext2 and ffs. I'd be very disinclined to trust a file-system I cared > about to code that hasn't been heavily beaten upon. I learned this the > hard way when I encountered a bug in FreeBSD's ext2 support that > killed the system and damaged the file-system. This was some years > ago, but as I recall, I had to resort to using Linux's fsck to put > things back together. > > The original post implies that he wants write access to the > file-system from both OpenBSD and Linux, so mounting read-only > probably doesn't serve his purpose. It he converts his ext3 > file-system to ext2, then he can mount read-write with OpenBSD, > assuming the OpenBSD ext2 code supports 256-byte inodes, and run the > risk of discovering a bug in the OpenBSD ext2 code. And he loses the > protection of the journal when running Linux. > > I think your suggestion of separate /home file-systems makes the most > sense. > > > > > -- > > Shawn K. Quinn > > skqu...@rushpost.com
Re: PgUp and PgDown on a Serial Console?
Thanks for pointing me in the right direction guys, I am now happily using screen's copy mode for scroll back on my Serial Console sessions. Evan Root, CCNA On Mon, Dec 16, 2013 at 7:00 AM, Christian Weisgerber wrote: > Evan Root wrote: > > > Tmux is a very good idea, I hadn't thought of it before but I'm already > > using screen as the serial console client, > > So why don't you use screen's scrollback buffer? > > -- > Christian "naddy" Weisgerber na...@mips.inka.de
Re: PgUp and PgDown on a Serial Console?
Hi Ville and Christian, Tmux is a very good idea, I hadn't thought of it before but I'm already using screen as the serial console client, I could just use it again "inside" openbsd. Or as you suggest tmux, which I've heard good things about. Evan Root, CCNA On Sun, Dec 15, 2013 at 6:19 AM, Christian Weisgerber wrote: > Evan Root wrote: > > > Does anybody know how to scroll back in a serial line console? > > That's a function of your local terminal. > > > I have a serial line connected to my box and I'm on the ftp site > > at the ftp client's command prompt wondering if anybody else > > has solved the problem of 1) not having a pager 2) trying to look > > at too many files that scroll off the screen and > > ftp> ls . |less > > -- > Christian "naddy" Weisgerber na...@mips.inka.de
PgUp and PgDown on a Serial Console?
Hi list, Does anybody know how to scroll back in a serial line console? I have a serial line connected to my box and I'm on the ftp site at the ftp client's command prompt wondering if anybody else has solved the problem of 1) not having a pager 2) trying to look at too many files that scroll off the screen and 3)using a VT100 or whatever with it's measly 80x24 Thanks Evan Root, CCNA
Re: NFS/Samba Alternative
Hello Byron, Firstly, are they windows 7 pro or enterprise? Most people don't know any difference but one that I have found is that Enterprise included the Microsoft NFS client along with their other Unix interoperability tools. Of course almost no one buys enterprise because it much more expensive. If you have Windows 7 Pro then this is what I have found, even though it's not much to work with. It depends on whether in transit security is important to you. If you can get away without it ftp is your best choice. This is a tough situation that I have tried to find clever solutions to but they are few and far between. Simply sharing files between computers is a nightmare for normal people because in simple situations like yours there isn't really a simple answer. Email and USB sticks are popular not because they're efficient, but because they work without tedious setup. If you are a domain admin then you could also install something like WinSCP and just configure SSH to be available on the box. I've even seen it work where you get the portable exe of a program and you can run it without installing it to a domain connected computer. Putty for example does this. Let me know if you find anything Evan Root, CCNA On Sat, Dec 14, 2013 at 11:56 PM, Byron Klippert wrote: > Hello, > > > I'm looking at options for sharing machine resources > (drives/directories/files) over LAN between OpenBSD server and Windows7 > clients. > > The Windows7 clients already belong to a corporate domain system, and my > lack of experience with Samba is telling me not to converge the two. > > My first choice is NFS, but... Windows7 Pro 64-bit doesn't seem to have > a NFS client built-in. All the alternatives I've tried cost money or > suck (or both). > > > Questions to the list... > > - what, besides ftp/http can I use to get as close to a "shared" disk > over LAN? > > - can I share a drive using Samba without interfering with the existing > domain system? > > > The LAN I'm running the OpenBSD server on is a different subnet and > accessed over WiFi. The Windows7 clients access the domain over > Ethernet. > > > > Thanks, > > -- > Byron Klippert > byronklipp...@ml1.net > c. 867-336-1306
Re: Man page that explains the file format of man pages?
Extended Backus-Naur Form! That is exactly what I was looking for Andreas. Thank you. I really didn't know what this was called or if there was a formal definition or not. Lol, the wikipedia page says that it does not have a single dialect. The IEEE standard is a good reference for quirks of the unix usage of EBNF. I think that if one starts with the wikipedia page and gets the basics and then can use the IEEE 1003.1 ch. 12 Errata page it's actually pretty clear. Thank you again! Evan Root, CCNA 505.226.1319 On Tue, Aug 13, 2013 at 1:40 AM, Andres Perera wrote: > he's not talking about the source level mandoc/man macros > > the subject is about the SYNOPSIS section language for utilities > > e.g. > > in ``grep [ file ]'' the [ ] operator signifies 0 or 1 > > in ``rm file...'' the ... operator signifies 1 or more > > > On Tue, Aug 13, 2013 at 2:58 AM, Jan Stary wrote: > >> On Mon, Aug 12, 2013 at 9:21 PM, Anthony J. Bentley >wrote: > >> > Evan Root writes: > >> > > Hello Misc, > >> > > I tried man 5 man for an explanation of the synopsis section of the > man > >> > > page and it says there isn't a manual for the file format > conventions of > >> > > manual pages. Sometimes I have difficulty with the syntax of the > synopsis > >> > > sections, is there a document I can refer to? > >> > > >> > OpenBSD manuals are written in the mdoc macro language. There is a > page > >> > describing it, in section 7 (not 5). It is mentioned in the "SEE ALSO" > >> > section of man(1). > >> > > >> > man 7 mdoc > >> > > >> > There is also a man(7) page, describing the older "man" macros, but > these > >> > are not used for new manuals in OpenBSD. mdoc has the advantage of > being > >> > a semantic format, unlike the old man language where the commands > mostly > >> > change only the presentation. > > > > On Aug 12 22:19:58, cellarr...@gmail.com wrote: > >> I don't think you understood. I am not looking to write a man page. I > was > >> just wondering if the system came with an explanation of the manual page > >> synopsis section language syntax. > > > > Which is exactly what Anthony pointed you to: > > The mdoc(7) describes the language syntax in great detail. > > > >> Sometimes I get confused by the language > >> and am not sure if I understand the synopsis sections of the man pages. > >> Also I am concerned that people who I might recommend OpenBSD to will > find > >> that an undocumented part of the system is the man pages. > > > > The mandoc people could probably take this as an offence. > > The manual system, as other parts of OpenBSD, is thoroughly documented. > > > >> Even the welcome message from Theo says "This message attempts to > describe > >> the most basic initial questions that a > >> system administrator of an OpenBSD box might have. If you are not > >> familiar with how to read man pages, type > >> "man man" at a shell prompt and read the entire thing." > > > > Well have you? That points you to mdoc(7) in SEE ALSO. > > > > "How to read man pages" in the welcome message refers > > to the the rendered manpages - as presented to the user with man(1). > > You are asking about the language syntax - how the manpages are written. > > > >> I think that this post on stack exchange presents my question better.. > the > >> answers are all pretty short and non-committal though. > >> > http://stackoverflow.com/questions/8716047/is-there-a-specification-for-a-man-pages-synopsis-section > > > > So you _are_ looking to write a manpage; > > mdoc(7) has a section called "MANUAL STRUCTURE" > > with a subsection called "SYNOPIS". Have you missed it? > > > > After you write it, don't forget to 'mandoc -Tlint'.
Re: Man page that explains the file format of man pages?
I don't think you understood. I am not looking to write a man page. I was just wondering if the system came with an explanation of the manual page synopsis section language syntax. Sometimes I get confused by the language and am not sure if I understand the synopsis sections of the man pages. Also I am concerned that people who I might recommend OpenBSD to will find that an undocumented part of the system is the man pages. Even the welcome message from Theo says "This message attempts to describe the most basic initial questions that a system administrator of an OpenBSD box might have. If you are not familiar with how to read man pages, type "man man" at a shell prompt and read the entire thing." I think that this post on stack exchange presents my question better.. the answers are all pretty short and non-committal though. http://stackoverflow.com/questions/8716047/is-there-a-specification-for-a-man-pages-synopsis-section Evan Root, CCNA 505.226.1319 On Mon, Aug 12, 2013 at 9:21 PM, Anthony J. Bentley wrote: > Evan Root writes: > > Hello Misc, > > I tried man 5 man for an explanation of the synopsis section of the man > > page and it says there isn't a manual for the file format conventions of > > manual pages. Sometimes I have difficulty with the syntax of the synopsis > > sections, is there a document I can refer to? > > OpenBSD manuals are written in the mdoc macro language. There is a page > describing it, in section 7 (not 5). It is mentioned in the "SEE ALSO" > section of man(1). > > man 7 mdoc > > There is also a man(7) page, describing the older "man" macros, but these > are not used for new manuals in OpenBSD. mdoc has the advantage of being > a semantic format, unlike the old man language where the commands mostly > change only the presentation. > > -- > Anthony J. Bentley
Man page that explains the file format of man pages?
Hello Misc, I tried man 5 man for an explanation of the synopsis section of the man page and it says there isn't a manual for the file format conventions of manual pages. Sometimes I have difficulty with the syntax of the synopsis sections, is there a document I can refer to? I also looked up the Unix version 1 man pages just for history's sake and found that they are reaaallly simple and easy to understand. Is this just something that has gotten out of hand over time? Evan Root, CCNA
Re: Network appliance recomendation.
I would recommend http://www.mini-itx.com/ and a cheap four port ethernet card. I just did a quick look around google and it looks like all of the four port 100mb cards are pci-x. You also will need a pci riser like here for example http://www.wiredzone.com/Supermicro-RSCR1UUE4R-1U,-UIO-Right-Side-Riser-Card~10022708~0.htm After all that you would have a good working system. But then again after adding up all the parts cost and your time you may still want to go with a vender who builds for you :( Unless you really don't find one. Then this is your choice. Evan Root, CCNA 505.226.1319 On Sat, Aug 10, 2013 at 10:09 PM, Francisco Valladolid H. wrote: > On Sat, Aug 10, 2013 at 5:15 PM, Paul de Weerd wrote: > > On Sat, Aug 10, 2013 at 08:09:02PM +, Stuart Henderson wrote: > > | These can be hard to get via the usual axiomtek reseller channels, but > these are > > | the same thing with a different front plate: > > | > > | > https://shop.bytemine.net/startseitenprodukte/bytemine-openbsd-appliance-6a16e.html > > | > https://shop.bytemine.net/startseitenprodukte/bytemine-appliance-6a16er.html > > > > I have the 6a16e (i.e. the non-rackmountable version) and have been > > very happy with it. Highly recommmend it! > > Thank you Paul. > > This model is very expensive plus the shipping and import duties to > Mexico.. > > Regards > > > > > Paul 'WEiRD' de Weerd > > > > -- > >>[<++>-]<+++.>+++[<-->-]<.>+++[<+ > > +++>-]<.>++[<>-]<+.--.[-] > > http://www.weirdnet.nl/ > > > > > > -- > Francisco Valladolid H. > -- http://blog.bsdguy.net - Jesus Christ follower.
Re: Re : Tux cups
So Stuart, I was looking at the OpenBSD mailing list rules because I wasn't sure about long links and I saw that lines over 72 characters are discouraged, that's were I decided to manually put in line breaks. :/ Although your point about a direct link to something that isn't google is a valid point. Question for everybody that uses console mailers; Does Mutt and the other text based mailers have line wrap enabled by default? or do they go off the edge of the screen? For me I use firefox for mail, even on my OBSD machine. Regards, Evan On Sat, May 11, 2013 at 7:02 AM, Stuart Henderson wrote: > On 2013-05-10, Evan Root wrote: > > Hey Erling, > > Maybe we should figure out where the default file is and > > replace it with this: > > > > http://www.google.com/url? > > sa=i&source=images&cd=&cad=rja&docid=a0cEbvZbg > > RAZYM&tbnid=FtFrLkyNwZjx6M:&ved=0CAgQjRwwAA > > &url=http%3A%2F%2Fwww.stealthcopter.com%2Fblog > > %2F2010%2F04%2Fdell-1320c-colour-laser-printer-mac > > hine-identification-code-microdots%2F&ei=3zKNUZzLG > > 8GgyAHqhIDYCA&psig=AFQjCNHQfMT7uZeIy7hp2a60 > > 2ovnjfOF9Q&ust=1368294495492423 > > > > Note on the above. You will need to remove the newlines > > from that beauty if you want to be able to click it. > > > > Wish this list accepted attachements because I could show > > you a scan of the Mac os x default test page that is the > > same as above. > > It has no logos except the Cups C with 'unix printing system' > > inside it, even though Apple employs Micheal Sweet. > > > > Also what is the etiquette on posting links? The guidelines > > for misc don't mention it. > > No problem including links but it would be better to include a link to > the page itself, rather than to google's redirector. > > And with the forced line-breaks you change it from something that > some people will be able to click on or paste in directly, to > something that everyone will need to edit. > > > http://www.stealthcopter.com/blog/2010/04/dell-1320c-colour-laser-printer-machine-identification-code-microdots/ > > -- Evan Root, CCNA 505.917.7873
Re: Re : Tux cups
Hey Erling, Maybe we should figure out where the default file is and replace it with this: http://www.google.com/url? sa=i&source=images&cd=&cad=rja&docid=a0cEbvZbg RAZYM&tbnid=FtFrLkyNwZjx6M:&ved=0CAgQjRwwAA &url=http%3A%2F%2Fwww.stealthcopter.com%2Fblog %2F2010%2F04%2Fdell-1320c-colour-laser-printer-mac hine-identification-code-microdots%2F&ei=3zKNUZzLG 8GgyAHqhIDYCA&psig=AFQjCNHQfMT7uZeIy7hp2a60 2ovnjfOF9Q&ust=1368294495492423 Note on the above. You will need to remove the newlines from that beauty if you want to be able to click it. Wish this list accepted attachements because I could show you a scan of the Mac os x default test page that is the same as above. It has no logos except the Cups C with 'unix printing system' inside it, even though Apple employs Micheal Sweet. Also what is the etiquette on posting links? The guidelines for misc don't mention it. -Evan On Sat, May 4, 2013 at 2:47 AM, Huy Nguyen wrote: > Printing a masturbating monkey would be a great test job. > > > Le samedi 4 mai 2013 à 08:05, Antoine Jacoutot a écrit : > > > On Fri, May 03, 2013 at 06:01:24PM -0400, Michael W. Lucas wrote: > > > On Fri, May 03, 2013 at 10:41:32PM +0200, Erling Westenvik wrote: > > > > To my astonishment: when printing a test page from cups, it outputs > an > > > > image of Tux!?! > > > > > > > > > > > > > Cups is Linux-ware, ported to OpenBSD. > > > > Used-to be linux-ware. Actually lots of its initial features got moved to > the more linux-centric cups-filters. > > Both upstreams are really easy to work with and accept portability > patches > with pleasure... > > > > But I disgress, the original question was regarding the Tux logo. The > reason > is simple, it's just a default print test page; actually most linux distros > ship with their own modified^branded one. > > Unless someone comes up with a super cool puffy print test page, I don't > see > the point in changing the default; who cares whether you are printing a > penguin or a monkey eating bananas... it's just a test job. > > > > -- > > Antoine > > -- Evan Root, CCNA 505.917.7873
Can't get sftp-internal to work for chroot users
Hello Like the subject says, I can't get sftp-internal to work. I have snips of the relevant config files below so eat your heart out and let me know if you want to see anything else. /etc/ssh/sshd_config: --- PermitRootLogin no Subsystem sftp internal-sftp Match Group sftpusers ChrootDirectory /home/%u Every thing else in the file is vanilla Permissions on the /home directories --- # cd /home # ls -l total 8 drwxr-xr-x 4 dvader sftpusers 512 Apr 8 16:09 dvader drwxr-xr-x 3 evan evan 512 Apr 8 15:11 evan # ls -ld drwxr-xr-x 4 root wheel 512 Apr 8 16:04 . # botton of /etc/passwd evan:*:1000:1000:Evan Root:/home/evan:/bin/ksh dvader:*:1001:1001::/home/dvader:/sbin/nologin botton of /etc/group _iscsid:*:102: dialer:*:117: nogroup:*:32766: nobody:*:32767: evan:*:1000: sftpusers:*:1001: --- So, What am I doing wrong or missing? -- Evan Root, CCNA
Re: Announce: OpenSMTPD 5.3 released
Gilles, How would you recommend a new unix admin learn OpenSMTPD? -Evan
