Re: OT - UML, can someone state that it works ?
I think the UML the OP is referring to is Unified Modeling Language and Rational Unified Process. On Wed, May 5, 2010 at 2:25 PM, Lars Nooden wrote: > On 05/05/2010 10:08 PM, Christiano F. Haesbaert wrote: >> >> Sorry for such an out of topic thread, hear my pain: >> >> I'm really sick of hearing about UML/RUP and all this boulshit about >> software engineering in my university. > > User Mode Linux works ok, you should probably try asking over on one of > the linux kernel lists found at the wiki: > >http://uml.jfdi.org/uml/Wiki.jsp > > I'm surprised it's a big deal at your university. VirtualBox is much higher > profile and allows others guest and host sytems. qemu / kqemu is available > in ports. > > :P > > /Lars
Re: pfctl - show port numbers
Although that solution will make upgrading more difficult without the change being made in-tree (you'll have to rebuild pfctl after each upgrade). On Dec 3, 2007 1:24 PM, MikeM <[EMAIL PROTECTED]> wrote: > On 12/3/2007 at 7:06 PM Henning Brauer wrote: > > |* MikeM <[EMAIL PROTECTED]> [2007-12-03 14:53]: > |> On 12/3/2007 at 7:32 AM Girish Venkatachalam wrote: > |> |> > Is there a way for me to tell pfctl that I want to see > |> |> > > |> |> > port = 25 > |> |> > > |> |> > instead of > |> |> > > |> |> > port = smtp > |> |> > > |> |> > ? > |> |> > |> |> short of hacking pfctl source, no. > |> |> > |> | > |> |As per your request I have added the "-P" switch to pfctl to > display > |> |numeric port numbers instead of service names for those who desire > the > |> |same. > |> | > |> |Please find attached the diff. > |> | > |> |I have modified the man page as well. > |> | > |> |Now, if you desire numeric ports display you have to use the -P > option > |> |in addition to other options. Everything else works as before. > |> = > |> Wow, thank-you! :) > | > |I don't think this is a worthwile addition tho. > = > > > It's obviously not my choice, I'm just much more comfortable with using > port numbers instead of protocol names. netbios-dgm means little to > me but 138 does, and correlates with what I see displayed should I > follow the instructions in the pf manual > (http://www.openbsd.org/faq/pf/logging.html#logfile): > >To view the log file: ># tcpdump -n -e -ttt -r /var/log/pflog > > > > Though for consistency with other commands that have an option to > toggle between symbols and numbers (e.g., -n for netstat or tcpdump) it > may be helpful as well. That's the main reason why I originally though > I was overlooking a simple option flag, I couldn't believe this ability > wasn't already present. ;) > > But as I mentioned, it's not my decision. I'll just hack the source > code to get what I need.
password echo turned off when performing sudo auth checks via ssh
Hi, I don't think this question is really OpenBSD specific per-se but rather an OpenSSH command. I'm using public key authentication between my OpenBSD systems (running ssh-agent) so that I can ssh/sftp between my systems (both are 4.1) without having to enter a password. As part of some IPSec performance testing I'm doing, I'm copying ipsec.conf files between the systems and applying them using ipsecctl -f which of course requires root privileges. I'm scripting this with perl since I'm testing 24 different IPSec policies at a time. What I've noticed is that when sudo (on the remote machine) periodically asks me to reauthenticate myself prior to executing a sudo command, the password prompt for the remote machine does not turn off echo. This also happens if I ssh into my other machine with any command that requires me to enter a password (such ssh host su). Any ideas as to why this happens? A few minutes of googling didn't pull up any useful hits as to why this happens. Thanks, Walter
Re: A prototype of suggested OpenBSD manual
Hi, I just finished upgrading a 3.8 system to 4.1 and performing a fresh install on a system that previously had Linux installed on it. Naturally while performing these upgrades I had to occasionally consult the OpenBSD documentation (FAQs on installation/upgrading). The existing documentation worked fine (i.e. I never felt a need to go find another set of guides). I personally have never found any of these other 'guides' that are maintained outside of the OpenBSD project useful, mainly because of a fear that the information will be stale due to the fact it is not maintained by a developer. As for your prototype specifically, I can understand what you are doing, but in order to make sure you capture all the info that is covered in the FAQ for install/upgrade (http://openbsd.org/faq/faq4.html), your guide would quickly grow much larger. Plus, the FAQ is hyperlinked into different topic areas so one can jump around easily, whereas your guide is linear. HTH, Walter On 11/3/07, Karel Kulhavy <[EMAIL PROTECTED]> wrote: > The OpenBSD has very good documentation when it comes to the manpages, but > with > the web guides there is one thing I don't like: one is presented information > he > doesn't need at the moment, which consumes time and increases likelihood of a > mistake. > > So I wrote an example prototype of a guide how I imagine it. It has only few > paragraphs since it doesn't make sense to put work into it if you think it > shouldn't be done this way. > > http://ronja.twibright.com/openbsd/ > > I have noticed that the 4.1 guide doesn't seem to officially exist anymore. Is > it really so? > > CL<
Re: A backwards approach to upgrading.
On 4/4/07, Walter Goulet <[EMAIL PROTECTED]> wrote: On 4/4/07, Peter Fraser <[EMAIL PROTECTED]> wrote: > Quoting from http://www.openbsd.org/faq/upgrade41.html > > Upgrading is a convenient way to bring your OpenBSD system up to > the most recent version. However, the results are not intended to > precisely match the results of a wipe-and-reload installation. > Old library files in particular are not removed in the upgrade process, > as they may be required by older applications that may or may not be > upgraded at this time. If you REALLY wish to get rid of all these old > files, you are probably better off reinstalling from scratch. > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Walter Goulet > Sent: Wednesday, April 04, 2007 2:33 PM > To: misc@openbsd.org > Subject: Re: A backwards approach to upgrading. > > What problem with the existing upgrade procedures is solved with your > new approach? > > I guess I have to ask again, what is the *problem* you are trying to solve? Why is having older library files around that are needed for compatibility with older applications (as mentioned in the FAQ), a problem? You stated at the beginning of your procedure that disk space is cheap these days, so the problem cannot be the disk space occupied by the older libraries. I'm just worried that some newbie is going to see your procedure and attempt to run in (inevitably mucking something up in the process) and run back to the list complaining about a broken upgrade. Suggest this privately to the maintainer of the upgrade FAQ and get their inputs first. Walter Forwarding to misc
Re: A backwards approach to upgrading.
What problem with the existing upgrade procedures is solved with your new approach? On 4/4/07, Peter Fraser <[EMAIL PROTECTED]> wrote: I use an approach to upgrading that I have not seen written anywhere. It does need additional space in the root partition but with disks these days that is not normally a problem. First copy away the "important parts" of the root partition onto another partition. What is the "important parts" is up to you, but should include any changes that you have made to the root partition. I use the ROOTBACKUP code in /etc/daily which copies the root partition to another partition on a separate disk, so that is done automatically. Now do an install of OpenBSD, but using only one partition (plus the swap partition). Do not change your disk partitioning in any manner, Do not use the install to mount any other partitions. All of OpenBSD will now reside in one partition. Which is why you need more disk space in the root partition. Note that all the other partitions will be untouched by the install. Once the new system comes up, you can now mount the partition that you saved away your "important parts", If you saved them previous under say /home mount what was /home under a different name. Merge your changes to "/etc" and others into the new root partition. Mount each of the old partitions that would have contained information set by an install (such as /usr) under a different name. Merge the new files from what is now in the root partition just installed into the correct place in the old partition. Merging what was in the old /etc into the new /etc, will of course update /etc/fstab which when the system is booted will end up mounting the old partitions into their correct places. Boot the system. The updated /etc/fstab will now mount the partitions in their correct places. The /usr and /home and other from the install are now inaccessible and have been replaced by ones defined in /etc/fstab. Packages can be installed at any time during this process, you just have to make sure that if you add packages while you are operation in the one partition that files added by the packages are also copied to the right place in the old partitions.
Re: 3.7 install script - dhcp
Well I installed via FTP onto my Zaurus about a month ago. The change documenting resolv.conf.tail in that manpage was made after the 3.7 release. Regardless, the installation shouldn't remove resolv.conf.tail. Frank Bax wrote: Thanks for the clarification, but I'm thinking your man pages must be -current, because I can find no mention of resolv.conf.tail in any man pages on my 3.7 (cdrom) system. The -current man pages on openbsd.org website appear to confirm the behaviour already present in cdrom release. At 01:25 PM 7/12/05, Walter Goulet wrote: man resolv.conf(5) The resolv.conf.tail file is used to pass extra options to the resolver. dhclient effectively appends the options in resolv.conf.tail to the resolv.conf file. On 7/12/05, Frank Bax <[EMAIL PROTECTED]> wrote: > I just installed 3.7 twice - once with dhcp and once with static ip address > - just to see what the differences were so I could make the transition > manually if/when necessary. I notice that the dhcp install left two extra > files on the system not found on the static ip install. > Should a couple of 'rm' commands be added to install script to remove these > files? > /etc/resolv.conf.save > /etc/resolv.conf.tail > Does anybody care about such nit-picky details? > > Frank
Re: 3.7 install script - dhcp
man resolv.conf(5) The resolv.conf.tail file is used to pass extra options to the resolver. dhclient effectively appends the options in resolv.conf.tail to the resolv.conf file. On 7/12/05, Frank Bax <[EMAIL PROTECTED]> wrote: > I just installed 3.7 twice - once with dhcp and once with static ip address > - just to see what the differences were so I could make the transition > manually if/when necessary. I notice that the dhcp install left two extra > files on the system not found on the static ip install. > Should a couple of 'rm' commands be added to install script to remove these > files? > /etc/resolv.conf.save > /etc/resolv.conf.tail > Does anybody care about such nit-picky details? > > Frank
Re: heal the world, and misc@ [strictly coffeetime reading]
Bram Van Dam wrote: I quite frankly don't give a rat's arse about how frustrated some of you are by seeing n00bs post on the list. So what if someone didn't read man page XYZ? At least tell them to read it. The only thing more disgusting than people not willing to learn, is people not willing to help others learn. Share the knowledge. Either that, or shut your trap. You missed my point entirely. I too am a new OpenBSD user. My point is that people who attempt to perform installations which directly contradict published OpenBSD guidelines (use GENERIC), then complain about the problems they encountered aren't helping new users. If anything, they are teaching new users bad habits. If you don't follow the instructions, you deserve to get yelled at because: 1) You waste developers time and piss them off 2) You are not providing useful information to new users. I'm glad that you obtain some entertainment value from the list, but new users don't come to misc for entertainment, we come for useful information to solve our issues and identify new issues that haven't been encountered before. Walter
Re: heal the world, and misc@ [strictly coffeetime reading]
Hate to keep this thread going, but I have to strongly disagree with the original poster's assertion on the attitude of the list. I have been treated well on the list. Additionally, I've been very happy at how receptive the developers are to discussing issues if you simply do your homework and provide patches to indicate you've really thought about the issue. My only complaint is that the signal to noise ratio is getting more and more out of hand. As a new OpenBSD user, I have to wade through all the useless complaints about how 'newbies' are treated and pointless 'feature requests' to find the answers I need. Can't your pointless 'heal the world' rants be taken to another list? You're not changing anything, just pissing off overburdened developers and frustrating new users. - walter Rick Barter wrote: -f wrote: dear list, a nice cup of coffee in front of me, and as a big fan of robert x., let me reflect a bit on the phenomenon called "misc@openbsd.org"... will try to keep it short. You failed to keep it short. a couple of days ago, there was a quite big thread about optimized kernel builds. the caller had a point (all of us do, no matter how insignificant) but some of the answers were rude, childish and much more trollish than the actual post itself. that thread made me quite disgusted of misc@, the way people treat each other here. i am a teacher. i have a degree in "teaching computer science". when you learn to be a teacher, you must sign up to basic psychology classes. obviously. teachers are role models. obviously. i don't teach at the moment, and i am not sure i will. Then you're not a teacher. i have found the fact that some of the kids will form habits, opinions, god-knows-what-else based on my personality quite scary and too big a responsibility. for now anyway. Please don't ever teach. If this is a legitimate fear for you, you'll do much more harm than good if you actually try to educate anyone. Everyone is a role model. If you don't think kids have already formed habits and opinions based on your personality, you're mistaken. but i am also what some might call nerd/geek (blech) and am very familiar with the social implications of that. > what people here mostly fail to realize is, how impersonal the internet really is. 99% of you don't know how old i am, how do i look like, what's my life like. same is true from my side towards you. Exactly. It doesn't matter who you are, how old or young you are, how you look. So why bring it up? my point is, that you could be affecting(flaming) a developing personality, a 13 year old kid who just happens to be very intelligent, just installed the system and hurries off to the mailing list to satisfy his knowledge hunger without realizing all the mailing list nuances we see everyday (top posting, long signatures, not reading the documentation beforehand, posting the "taboo" questions). you just never know. (well, except darren reed ;-) You know what? This is the number one problem with the world today; people like you trying to protect the young, innocent, whatever from themselves and others. Since when is it *MY* job to police everyone else's kids and feelings? I hope I do affect developing personalities. I hope they learn that the world doesn't revolve around them and that if you ask a stupid question, you get a stupid answer. And, if posting to misc@ and getting flamed makes them cry, they had better develop a thicker skin than that because the world is a big, scary place. it's all about experience. there is a baby born every second, and no one was born wise. Right. So? Who gives a crap. How do you think experience is gained? By being handed information and never getting yelled at? No. Most experience is gained through failure and disappointment. Don't sell people short. Let them take a few hard knocks in life. They'll be better people for it. It builds character. everyone who uses email for more than 5 years knows just how elusive this form of communication is. how easy it is to misunderstand, misinterpret even a clearly worded email. 1. if a mail makes you angry, never respond rightaway. in the best case, sleep on it. in the worst case, go do something else, come back in an hour, read it again carefully and then respond. 2. if a mail makes you angry, in 85% of all cases, you should just delete it, and forget about it. i am quite amazed how hard it is for people to ignore stuff. you must exercise your ignore muscle. saves awful lot of time and energy. (i know, this mail is the opposite of this advice, but i slept on it ;-) Fuck you. Get angry. More people should get angry about things. Lack of anger and isolation from adversity are the things that are killing the world. If someone was beating you with a stick, would you just ignore it? If someone is making laws taking away our freedom, should we just ignore
Re: ssid vs. nwid in ifconfig
Hi, I'm including a patch to ifconfig(8) to indicate that nwid is synonymous with ESSID. Thanks, Walter Index: ifconfig.8 === RCS file: /cvs/src/sbin/ifconfig/ifconfig.8,v retrieving revision 1.107 diff -u -r1.107 ifconfig.8 --- ifconfig.8 7 Jun 2005 23:12:17 - 1.107 +++ ifconfig.8 8 Jun 2005 03:39:59 - @@ -530,6 +530,7 @@ .It Cm nwid Ar id (IEEE 802.11 devices only) Configure network ID for IEEE 802.11-based wireless network interfaces. +Note that network ID is synonymous with extended service set ID (ESSID). The .Ar id can either be any text string up to 32 characters in length, [EMAIL PROTECTED] wrote: hi, On Tue, Jun 07, 2005 at 02:33:35AM -0500, Walter Goulet wrote: One minor point that befuddled me at first was the fact that ifconfig and wicontrol use different terms when referring to the SSID. Specifically, if you use ifconfig to set the SSID, you have to use the 'nwid' option. However, if you use wicontrol, the man page has a seperate option 'q' used to set the SSID. please don't use wicontrol anymore. most of it's functionality except some dubious buttons have been added to ifconfig. - Change ifconfig's interface to replace 'ssid' with 'nwid' at the risk of breaking existing scripts etc (Note that NetBSD changed 'nwid' to 'ssid' to resolve this issue). breaking scripts for nonsense? uhh... ssid is a wrong, but commonly used, term and the essid (extended service set id) is the IEEE name for the "network id". we're fine with nwid because it's a generic name which also applies to non-802.11 protocols and it's less cryptic. - Change ifconfig's manpage to indicate that nwid is really the same as the ssid. you mean the ESSID ;-). a hint in ifconfig(8) is probably the better idea. I personally think the second option is the better option; I'd be glad to submit a patch once I finish building userland. I'd like to get some opinions before I move forward with this effort. no. we won't replace nwid with neither ssid nor essid. same for nwkey. Thanks, Walter reyk
ssid vs. nwid in ifconfig
Hi, As a relatively new user to OpenBSD on my zaurus, I've spent a bit of time configuring my prism based wireless network card to work correctly with my AP using wep etc. One minor point that befuddled me at first was the fact that ifconfig and wicontrol use different terms when referring to the SSID. Specifically, if you use ifconfig to set the SSID, you have to use the 'nwid' option. However, if you use wicontrol, the man page has a seperate option 'q' used to set the SSID. I see a few options: - Get over it; who cares it's a stupid semantic issue! - Change ifconfig's interface to replace 'ssid' with 'nwid' at the risk of breaking existing scripts etc (Note that NetBSD changed 'nwid' to 'ssid' to resolve this issue). - Change ifconfig's manpage to indicate that nwid is really the same as the ssid. I personally think the second option is the better option; I'd be glad to submit a patch once I finish building userland. I'd like to get some opinions before I move forward with this effort. Thanks, Walter
Re: Minor patch to afterboot manpage
On Tue, May 31, 2005 at 10:41:38PM -0500, Walter Goulet wrote: >> Hi, >> >> I've recenly installed OpenBSD 3.7 on my Zaurus C3000. While perusing >> the afterboot manpage to figure out how to configure my system, I >> noticed that the manpage indicated that the /etc/rc.conf.local file was >> referred to before the manpage stated that the user had to create this file. >> >> So this patch adds a small paragraph instructing the user to create this >> file immediately after the root password and system date are set. I >> think this makes the page read better and avoids the user referring to >> this file before it is created. >> > hi, i did not take the patch, but decided to put the sections of > afterboot(8) into a more logical order (i hope). > thanks for the report though. please use unified diffs (diff -u) next > time. > jmc Hi, I took a look at the updated manpage; I agree that it now reads more logically and avoids the issue I noticed. Thanks for the quick update! Walter [demime 1.01d removed an attachment of type application/x-pkcs7-signature which had a name of smime.p7s]
Minor patch to afterboot manpage
Hi, I've recenly installed OpenBSD 3.7 on my Zaurus C3000. While perusing the afterboot manpage to figure out how to configure my system, I noticed that the manpage indicated that the /etc/rc.conf.local file was referred to before the manpage stated that the user had to create this file. So this patch adds a small paragraph instructing the user to create this file immediately after the root password and system date are set. I think this makes the page read better and avoids the user referring to this file before it is created. *** afterboot.8 2005-05-31 22:31:25.0 -0500 --- afterboot.8 2005-05-31 22:33:43.0 -0500 *** *** 134,139 --- 134,147 .Pp Set the time zone to Atlantic Standard Time: .Dl # ln -fs /usr/share/zoneinfo/Canada/Atlantic /etc/localtime + .Ss Create local system startup configuration file + Create a file + .Pa /etc/rc.conf.local + with the same user, group and + permissions as the + .Pa /etc/rc.conf + file. This file + will contain site-specific values for configuration variables used by the system startup scripts. .Ss Check hostname Use the .Ic hostname *** *** 479,485 .Pa /etc/rc.conf . Again this script should not be changed by administrators: site-specific changes should be made to - .Pq freshly created if necessary .Pa /etc/rc.conf.local . .Pp Any commands which should be run before the system sets its --- 487,492 Walter
