Re: Donations
Ingo, you have been very kind and thoughtful in all of your replies; for this I thank you. I guess I'm used to projects I like actually wanting help from the community. The OpenBSD model baffles me. For a long time I have had a great love for the project. I think I started during 2.6 and bought several CD sets and posters. I switched to Linux at some point, but I always highly respected the OpenBSD project. I even sent some books via snail mail to Canada as a donation. I started using it again exclusively about a month ago, and have enjoyed it immensely. I can give a little cash, if that's all they want. I'll stop trying to offer my unwanted talents and find somewhere else to spend those.
Donations
I see there are two types of donation receivers, the project and the foundation. What is the difference between how the money is spent between the two. The foundation from what it looks like goes to paying the bills for the infrastructure, how about donations to the project. I've already many times over stated my willingness to donate time; but it took a while to find a niche. I am also an artist and a poet. Perhaps I could work on an OpenBSD related poetry chapbook. I remember you used to have songs for every release. I want to donate money but I just want to see where it goes so I can tailor my choice of which. -- Google doesn't need to know every time I fart.
Re: How to break and smash things
Thanks, I read through but didn't follow on a computer but I'm making a Post-It now to read more about afl. It seems I'll need to learn a bit about gdb, which I know very little about. I think I read a chapter about it maybe five or ten years ago. I appreciate the link, this seems like a good landing place for me.If you want you can private mail me your Paypal and I'll buy you a beer or a coffee.--Google doesn't need toknow every time I fart.On Oct 26, 2023, at 12:22, Janne Johansson wrote:Den tors 26 okt. 2023 kl 07:51 skrev Maria Morisot <maria.mori...@icloud.com>:But I really want to help the project. I like the idea of trying to break things and get them to malfunction in order to expose bugs that have been overlooked. I have a pretty good understanding of randomness and know about the concept of fuzzing. I've done testing in my software courses and know a little about writing code for explicit bad cases. But my schooling was very lax and was easy to get A's so I didn't put much effort in. https://undeadly.org/cgi?action="">-- May the most significant bit of your life be positive.
Re: How to break and smash things
I can't use Amazon services and products. I got in trouble a while back for using my credit card from a Kyrgyzstan IP, and didn't have the motivation to go through customer service and explain that I was an American citizen living here. But I have access to O'Reilly. I used to make my own audiobooks of C code taken from Robert Sedgewick's Algorithms in C; try that, it's fun having to read semicolons and curly braces out loud.I have family. I lost four kids, have one who survived. Been divorced. Have problems with my sister's family who hate me for my Catholic beliefs and even had me thrown into a mental ward for teaching my son that angels and demons are not friends.I've been a professional painter with exhibitions in Europe and America and seen a taste of fame and splendors.I may be young at heart but I carry a lot of experience and wisdom.Anyways, I have my life in order, and I'm quite happy and content with the majority of my personal activities. I have perhaps 6 hours unaccounted for most days that I would like to devote to OpenBSD. Is that a bad dream and aspiration to have?I love the project immensely ever since I read about Theo speaking out against the war in Iraq publicly. That took guts in a time when America was warmongering with their mantra of WMD. I have a huge respect now for Theo and his project, which I had already liked to begin with in the days of Sushi and Ramblo.You work on DNS.I write poetry.Your motives I don't know. I don't know what drives you to take care of your project. I hope it is love. Love for not only the code and the system, but deep love for your users and the community of people you work with.I love the OpenBSD community, and spend an hour praying for you each afternoon; even though I don't really know any of you.When you put love into a project, it becomes something more than just bytes and arrays. It is like planting seeds in a field to grow a lush forest of trees, where life can flourish.I lost four children.I just bought my remaining one a 7.3 OpenBSD shirt to wear; which he is very happy with.Have you ever lost a child? It makes you really contemplate purpose and meaning in life.DNS is great. Networked systems are great. But AI can one day handle all of that perhaps. What AI cannot do is pray for The de Raadt.--Google doesn't need toknow every time I fart.On Oct 26, 2023, at 12:22, Janne Johansson wrote:Den tors 26 okt. 2023 kl 07:51 skrev Maria Morisot <maria.mori...@icloud.com>:But I really want to help the project. I like the idea of trying to break things and get them to malfunction in order to expose bugs that have been overlooked. I have a pretty good understanding of randomness and know about the concept of fuzzing. I've done testing in my software courses and know a little about writing code for explicit bad cases. But my schooling was very lax and was easy to get A's so I didn't put much effort in. https://undeadly.org/cgi?action="">-- May the most significant bit of your life be positive.
How to break and smash things
Hi, I've been frustrated in trying to find a way to help the project and thanks to several people's replies I've been considering what I like to do with the operating system. My needs are simple, as far as personal usage goes; give me an offline system with vi and hard drive access and I'll happily write poetry to my heart's content in my favorite café. But I really want to help the project. I like the idea of trying to break things and get them to malfunction in order to expose bugs that have been overlooked. I like to smash things. Does anyone know of any good resources for this, or recommended software in ports that I should study and learn? I have an O'Reilly subscription, so and book recommendations from on there I should have access to. Blogs are great too. I have a pretty good understanding of randomness and know about the concept of fuzzing. I've done testing in my software courses and know a little about writing code for explicit bad cases. But my schooling was very lax and was easy to get A's so I didn't put much effort in. Thanks again to everyone who has tried to help me find my path here in the community, I know that I am a tough pill to swallow, that is why I generally play alone. -- Google doesn't need to know every time I fart.
xfce
I know for a fact that something is broken in either xenocara or the main system, I can reproduce a kernel panic by running xfce, I've enountered it many times. But I don't know how to trap it before it faults in order to see what is going on. My solution was just to ignore it and run cwm but I want to try to fix it. I don't know how though. -- Google doesn't need to know every time I fart.
Re: my first patch
I thought xenocara was kind of incorporated into the OpenBSD project. Thanks for responding. I think when I started out a month ago, my main issue was having hangups in the kernel from running xfce. I've since migrated to cwm and am much happier than when using xfce on Linux. I have high energy, doctors call it mania; my peers call it aptitude for prolific output. I just need someone to steer me in a direction. What needs work and what do I need to learn. I am technically disabled with mental illness, so I have income and don't need to work. I have near mensa intelligence. I've read computer books for 20 years on various topics, but it's scattered. If nobody will give me direction then I'll keep plugging away at my own fancy and probably annoy everyone on the list until I finally get kicked off. /story of my life. -- Google doesn't need to know every time I fart. > On Oct 25, 2023, at 14:04, Stuart Henderson wrote: > > On 2023-10-25, Maria Morisot wrote: >> Basically I just changed all instances of strcpy and sprintf to use strlcpy >> and snprintf, because the compiler said to. >>> >>> This sort of change should go upstream rather than in ports. Be careful >>> that you're using correct lengths though, it is possible to get things >>> wrong and break programs. >> >> What does upstream mean, in the main source tree? I would have guessed that >> such changes were already implemented in the main system. > > If you're looking at code directly in an OpenBSD CVS repository and it > still has strcpy/sprintf, it almost certainly does not originate from > OpenBSD itself, rather comes from another origin, and often updated from > time to time. Examples of this include most of the xenocara tree for > X, some of the toolchain used to produce binaries (compilers, linkers > and so on) and a few other parts of the system. Making changes like > this to such code in the OpenBSD tree makes it difficult to update to > newer versions; if done at all, it's usually done "the other way round" > - changed in the origin, and then synced across as part of a later update > to OpenBSD. > > Similarly for software in the ports tree, carrying patches for things > like this often makes it difficult to update to a newer version. > They're usually quite intrusive and affecting large parts of the source > distribution. > > And while they can be simple, strcpy/sprintf/similar conversions still > need careful review, to make sure that there aren't off-by-1 calculation > errors in string length, or to make sure that actual string lengths are > used and not e.g. size of a char * pointer. > > Generally I'd suggest that someone new to this finds problems/niggles in > their use of the system, looks at how it works and figures out what's > going on and what changes could be made to improve that. There's a lower > risk of accidentally introducing problems if you're looking at code > which you actually use rather than in a big sweep of the source tree, > and probably better for gaining understanding. > > Also if there's some code which interests you, you might like to try > seeing how it changed over time, how problems were fixed, etc (i.e. read > the commit history - this may be simpler by using the mirror on github > than cvs, as you can see changes grouped together as a whole commit, > which can include changes to multiple files at once). A big part of > working on software like this is understanding the history and why > things were done. > > > -- > Please keep replies on the mailing list. >
strlcpy & pointers
I opened xenocara/lib/libX11/src/xlibi18n/lcPrTxt.c and strcpy operates on a buffer passed in through a pointer, so I don't think there's a way to calculate the buffer length. I'm not very good at C, so I don't know what to do here. Do I just leave strcpy in place or does the calling code need to be reworked. -- Google doesn't need to know every time I fart.
Re: CVS checkout
got it now, thanks. I'll start editing; but I still don't know how to submit changes. Since I'm new I can't imagine anyone giving me write access; so what is the process for uploading changes to the source tree for someone just starting out? -- Google doesn't need to know every time I fart. > On Oct 25, 2023, at 12:44, Otto Moerbeek wrote: > > On Wed, Oct 25, 2023 at 11:13:44AM +0600, Maria Morisot wrote: > >> I've been trying now for a month to download source via CVS as per >> instructions on openbsd.org; I get operation timed out every time. I get no >> ping from anoncvs.ca.openbsd.org >> >> I want to help work on the project in any way I can; I love OpenBSD. > > See https://www.openbsd.org/anoncvs.html: Choose the Anonymous CVS > server you are going to use from the list of servers > (https://www.openbsd.org/anoncvs.html#CVSROOT) > > > Some examples use anoncvs.ca.openbsd.org, but that server is no longer > operational. > > Pick one fomr the list mentioned. > >-Otto
Re: my first patch
I'll check out SoX's --ignore-length option and see if I can figure out what they are doing there. What I'm more concerned with than the implementation is which behavior seems more correct; to try to play at the specified rate or to just ignore and play at the default settings. -- Google doesn't need to know every time I fart. > On Oct 25, 2023, at 02:42, Jan Stary wrote: > > On Oct 24 22:09:02, a...@caoua.org wrote: >> faad -w file.m4a | cat >file.wav >> results in a file with zero-size data chunk (because faad couldn't >> seek to the beginning of the file to fixup the header). aucat, >> audacious, audacity and sox can't play it; mpv, and ffplay can > > SoX's play --ignore-length can play it. >
CVS checkout
I've been trying now for a month to download source via CVS as per instructions on openbsd.org; I get operation timed out every time. I get no ping from anoncvs.ca.openbsd.org I want to help work on the project in any way I can; I love OpenBSD. -- Faith in Jesus is like going off a high dive platform for the first time.
Re: my first patch
> SoX's play --ignore-length can play it. > SoX's --ignore-length appears in a few formats, as far as the wav format goes, the code comments suggest it is implemented to handle 32-bit wav files greater than 2GB. It seems you just found a happy side effect.
Re: my first patch
> that you're using correct lengths though, it is possible to get things > wrong and break programs. I was careful to look at the buffer lengths being written and to match them in strlcpy and snprintf. I peeked at the source for instances of strcpy and found a lot in xenocara; less in the main source tree. I'm willing to change these but I need to know how to submit the altered files and since it's my first time contributing, I'd love if someone could double check a bit of my work.
Re: my first patch
Basically I just changed all instances of strcpy and sprintf to use strlcpy and snprintf, because the compiler said to. > > This sort of change should go upstream rather than in ports. Be careful > that you're using correct lengths though, it is possible to get things > wrong and break programs. What does upstream mean, in the main source tree? I would have guessed that such changes were already implemented in the main system. I just want to be a productive member and my programming experience is limited. If someone can point me to work that makes a difference doing menial tasks, I'd be more than happy to be a code janitor.
Re: my first patch
I don't have a test machine and I'm trying to keep my installation as simple as possible, but if anyone wants to try piping a wav file into mplayer or ffplay, I'd be interested in the results. Does it work?
Re: my first patch
> You're right. The .wav headers require to lseek(2) within the file > which doesn't work on a pipes. It could work on certain files which > headers are placed in a way lseek(2) doesn't need to move the file > pointer. > You could try to modify aucat to skip the lseek(2) calls if it > wouldn't change the file pointer. Possibly call read(2) and discard > few bytes when the file pointer moves forward by few bytes only (iirc > .wav needs data to be aligned). Forgive me if I'm dense, but I'm a better artist than I am a programmer. I'm trying to follow you though. I understand why you cannot seek in a pipe, but I do not understand why that affects playback of a MS Wav file through a pipe. Aren't the headers kept in the front, and my understanding is maybe you can grab enough bytes to check if a header is present. I thought wav is just a raw sample with a small header. I'd think a quick check for header wouldn't upset playback for raw samples without one.
Re: my first patch
It is my understanding that wav files contain the headers necessary for a program to adjust the audio settings for play, or to do the software process necessary to reformat the input to the audio device. It doesn't make sense to have the wav headers if they aren't going to be used. Tell me if I'm wrong. I'm not very good at C but I'm willing to try to fix aucat to adjust wav output in response to the headers if that's something that seems like it's broken. But I did find an alternate solution. I just "-o /dev/audio0" in faad, and use "-f 2" (raw pcm); this works and seems to play at 44100 because it sounds good to me. Not sure how to check default playrate or change it via command line, so this works out of the box: gethsemane$ faad -f 2 -o /dev/audio Tori_Amos/The_Beekeeper/03*.m4a -- Code is poetry. > On Oct 24, 2023, at 21:03, Alexandre Ratchov wrote: > > On Tue, Oct 24, 2023 at 05:10:53PM +0600, Lucretia wrote: >> >> a bit off-topic, but: >> gethsemane$ faad -w Tori_Amos/The_Beekeeper/03* | aucat -i - -h wav >> makes Tori sound like Minnie Mouse. How can I fix this? >> > > you've make faad and aucat use the same data format, ex: > > faad -d -f2 -w foobar.m4a | aucat -e s16 -i - > > possibly use the -r option if the rate is not 48kHz (which is aucat > default). Alternatively, output in a temporary .wav file and play it > after it's decoded
X11 crashing
I installed the patch for X11 (October 3rd), then rebooted, now X is crashing every time I log in on xenodm, sometimes I get a blue screen with debug messages, other times I get a square on my screen with a black background, and it is otherwise completely frozen, and I can't ctrl-alt-Fn into a terminal. I can do this before I try logging in though, and I tried reverting the patch but to no avail. My wm is xfce, and when I remove my .xsession everything works normal without crashing. I'm far from a novice user but I don't know much about how to properly report issues or what steps I need to take to isolate where the problem is.
Re: Problems with HD
> On Thu, Oct 05, 2023 at 04:08:34AM +0000, Maria Morisot wrote: > > > I have an Asus Vivobook (1400EA), > > and the hard drive is not recognized > > by OpenBSD. I have the same problem > > on some distros of Linux, but on others > > it shows up fine. > > > My Asus ZenBook had a similar issue, which was resolved > by diving into the BIOS "Advanced" section and setting the > storage controller to something other than the pseudo-RAID > mode. It may we worth checking whether there is such an option > available. I went into the BIOS and can't see anything about disabling RAID; and the disk itself says there is no RAID on the drive. But I did get into the BIOS info for the drive itself so I'll post that in case someone finds it useful. Port: 1.0 Model Number: Micron_2450_MTFDKBA256 Serial Number: 214532CBCA77 Size 238.4GB Controller Type: NVMe Controller Interface: PCIe
Problems with HD
I have an Asus Vivobook (1400EA), and the hard drive is not recognized by OpenBSD. I have the same problem on some distros of Linux, but on others it shows up fine. The official Windows driver is here: https://www.asus.com/supportonly/f1400ea/helpdesk_download/ Intel Rapid Storage Technology (IRST) Driver I didn't see any lines in the dmesg about it when booting up the install disk. I love OpenBSD! It's my favorite O/S, so if I could get it installed it would be great! Right now the only thing I think that I could do is get a removable USB drive to install on.
