Re: RELENG_4_3 calls itself -RELEASE?
On Fri, Aug 03, 2001 at 09:54:02AM -0400, Bob K wrote: > > I like -BEET. It's short, means nothing, and is red. What more could > you ask for? :P Suggest -FOO has a long standing meaning of nonsense in computer lingo. Or -FOOBAR. -- David Kelly N4HHE, [EMAIL PROTECTED] = The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: moving to XFree86-4
I always install FreeBSD without X and make XFree86-4 from ports. xf86cfg cores. I just hack the output of XFree86 -configure tho, so it's no big deal. James. -Original Message- From: Richard Glidden [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 02, 2001 1:14 PM To: James Satterfield Cc: [EMAIL PROTECTED] Subject: RE: moving to XFree86-4 Come to think of it, I did have xf86cfg dump core on me once, when I already had XFree86 3.3.6 installed and then installed the XFree86 4.1 port without removing 3.3.6 first. I haven't tried 4.1 on other machines. However, I have run the XFree86 4.0 port's xf86cfg without problems on 3 other machines which did not have 3.3.6 installed. These were machines running FreeBSD 4.3-RELEASE with nVidia and ATI video cards (GeForce, and Mach64) Perhaps there is some piece of an old configuration sitting around that is confusing xf86cfg? Or maybe there is something wrong with the 4.1 port (I haven't tried it enough to be sure) - Richard On Thu, 2 Aug 2001, James Satterfield wrote: > I've had xf86cfg core on every machine I've tried it on. Perhaps I'm missing > something? > > James. > > -Original Message- > From: Richard Glidden [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 02, 2001 11:10 AM > To: Antoine Beaupre (LMC) > Cc: [EMAIL PROTECTED] > Subject: Re: moving to XFree86-4 > > > > On Thu, 2 Aug 2001, Antoine Beaupre (LMC) wrote: > > > Unfortunatly, from what I can tell, -configure just creates a config > > file based on your hw configuration, and does not ask basic stuff as > > "what resolution do you want". :) > > > > I really, really, really miss XF86Setup. Really. > > Am I missing something? What was so great about XF86Setup? > > I haven't had any problems configuring XFree86 4, using the included > tools. The "xf86cfg" program included with XFree86 4 seems to do the job > very well, and even uses the "XFree86 -configure" command as a starting > point, rather than guessing at 'safe' defaults like XF86Setup did. Plus, > it has support for new features of XFree86 4. > > - Richard > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: RELENG_4_3 calls itself -RELEASE?
On Fri, Aug 03, 2001 at 10:00:49AM -0400, Antoine Beaupre (LMC) wrote: > Go for RUTABAGA. It's cute. > > Besides, Debian does it and everybody likes it. It allows us to pick > names in honor of dead people. Yay. ;) I like this, and vote for -POUL for this branch, to forever pay homage to a recently departed writer. > We should scrap -STABLE for a more meaningless name, but I won't get > into this. > > Is it me or this thing comes up about twice a month? Yup. Conversely, that doesn't make it less of an issue, but I am .not. going down that path. :) Jamie > A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: moving to XFree86-4
I found that pkg_delete -a and make install of all necessary ports is an extremely healthy activity as it removes a extremely big load of crap (read: useless/unused software). Just reinstall it all. You probably don't need that much anyways. ;) For the record, I don't any easy way. A. j mckitrick wrote: > If I have backup up my old /usr/X11R6, is there an easy way to move my apps > to XFree86-4? Or do I need to 'make reinstal' all of my X ports? > > jm > -- Antoine Beaupré Jambala TCM team Ericsson Canada inc. mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Yet again changing branch names? (Re: RELENG_4_3 calls itself -RELEASE?)
Garance A Drosihn wrote: > At 7:07 PM -0700 8/2/01, Chad R. Larson wrote: > >> On Fri, Aug 03, 2001, Andrew Boothman wrote: >> > I prefer -SECURITY, because it makes it clear this is the >> > branch dedicated to security fixes and nothing else. >> >> Yes, but then the newbies would think this was some special >> release with extra security features. And complain when they >> get rooted. We go through "why isn't -STABLE really stable" >> three or four times per year. ?? s/year/month/ ! >> I'd rather a tag that didn't imply some kind of promise. >> >> But I agree, it should be something other than -RELEASE. > > I agree it should change, and should not be -SECURITY or -SECURE. > In the interest of keeping it simple and yet nondescript, I would > prefer something like -RELEASE+ or -RELEASE-PLUS > > While something like BEET or RUTABAGA is also nondescript, I think > that's a little too silly for this branch. I know several sysadmin's > who have been very happy to have this branch around. I could see > changing the *stable* branch to a name like beet, rutabaga, or maybe > rawcarrot (which is then "cooked" for release... :-). Maybe that > would finally get rid of the confusion of people who read too much > into the name "stable". Yah. -stable is really great, but it's gotta go. We have to *force* people to read the doc. It's the bottom line. When I discovered Debian, I heard of Potato, Slinky and stuff like that. I had no clue of what the heck they were talking about. I read. I learned. :) > For that matter, perhaps we should name the "security-fixes" branch > as -stable, and then change the branch we currently call stable to > be -kitchen, and change -current to be -frontier or -scarymovie. hmm... Here's what I think: 1. The security breanch could just be named what it is: -SECURITY_FIXES or -SECFIX. 2. "-stable" gotta go. Any fruit, household item, room, whatever name will fit. The problem we'll find is with the doc and the infrastructure (this list) that we can't change to follow changing names. 3. "-current" should also be renamed. "Evil dark overlord planning to take over the earth" could be a better name (but it might attract too much people). I suggest "-crap". That'll keep wanderers away. :) Not that we don't want people to use -current, we don't want people to use -current without knowing what they're doing. 4. And how about naming our releases? I know there are a lot of them (3/4 a year), but I like the idea of dedicating releases or naming them to funny names. :) > [really, any naming scheme is fine by me personally. I'd just like > to see if we could come up with something so we didn't have to debate > some branch-name every three or four months. So, I hope that by > tossing several disparate ideas out, maybe something will make sense. > Note: 'disparate', not 'desperate' :-) ] Here too. I could stay just like that. But I can't bear the freaking noise of having this thing over and over again. -- Antoine Beaupré Jambala TCM team Ericsson Canada inc. mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
moving to XFree86-4
If I have backup up my old /usr/X11R6, is there an easy way to move my apps to XFree86-4? Or do I need to 'make reinstal' all of my X ports? jm -- "Investigators have discovered the cause of the TWA 800 explosion was a frayed wire. The wire became frayed when it was struck by a missile." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
oh my god ... again, no diskless boot ...
Hello. Well, yesterday I ran into trouble after installing the newest sources of FBSD 4.3-STABLE. We lost our diskless X-terminals because they won't boot after that update. Yesterday night I copied /etc/ of the diskless root from etc.bak back to etc and was wondering that all X terminals booted again. Today, I did a cvsupdate again and I read to late that the code is in a kind of 'wobbing' status (slushy or something else, don't care). All of our servers running FBSD 4.3-STABEL run stable and offered nothing suspicious until now. Only the diskless systems crashes - and the kind of crashing is funny! After powering the terminal on it searches for its DHCP (isc-dhcp2), it finds it and then I see the status message when the kernel gets loaded (rotating slash and several hex numbers). But this is to short to watch, immediately after that I see a lot of squared pixels, flashing, nice coloured and remembers me to the time of the C64. It seems that the graphical interface or/and the whole system crashes immediately after trying to start the kernel. Technical data: Our diskless terminals use a AMD K7-DURON 700 MHz, a DFI AK74-EC motherboard, 64 MB PC133-3 RAM, a Intel EtherExpress 100+ NIC and a GigaByte GA660+ Riva TNT2 based graphics accelerator. The terminals boot via PXE/DHCP. I write this message from another terminal I was working from this morning on and loaded with the old kernel. Can anyone tell my what happened to the diskless stuff? Why are the diskless systems involved? The only difference is that they use MFS (all other servers do not use MFS due to the fact that in the past MFS produces on SMP systems many harsh problems). Thanks, oliver -- MfG O. Hartmann [EMAIL PROTECTED] IT-Administration des Institut fuer Physik der Atmosphaere (IPA) Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: PERC 3 Dell 2500 and FreeBSD 4.3 stable
> Hope this helps others on Dell, it would be great to get Dell to > offers these controllers instead of those crappy PERC controllers, but > these I guess are too expensive??? There's not much more subjective than RAID controllers, except perhaps text editors. 8) I'm glad you're happy with the DPT controllers, but the other Adaptec controllers you're bashing are actually quite widely liked, and when they're working, they do perform noticeably better... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: moving to XFree86-4
I'm having the same toubles with freetype2-2.0.3_1 which is actually at 2.0.4 in the packages ftp sites (and mirrors). In fact Mesa-3.4.2_1 also has the same hangup, but I'm not sure if its in its required list. Somehow I think this points back to the older problem with the INDEX file in the ports tree? Well thats my assumption. My work around has been to use the ports, but it would be nice to get it going on packages. Jorge On Thu, 2 Aug 2001 [EMAIL PROTECTED] wrote: > On Thu, Aug 02, 2001 at 02:35:32PM +0100, j mckitrick wrote: > | Any caveats I should look out for moving to version 4? > > My only issue with it, is that ports seems to be rather confused about > where to register dependencies for X programs. > > If you have XF86 v4 installed and try to install a window manager for > instance, ports will try to register the dependency with > Xfree86-3.3.6_9 which is obviously wrong. Now, if you set > XFREE86_VERSION=4 in your /etc/make.conf, ports will for some reason > try to register a dependency with imake-4.1.0, freetype2-2.0.3_1 and > XFree86-4-libraries-4.1.0, which isn't quite right either when the > package you have installed is called XFree86-4.1.0_4. > > Ok, so this isn't a problem with X but rather a ports issue. > Nitpicking, probably, but I thought I'd mention it. :-) > > Version 4 has otherwise been working flawlessly for me, both at home > and at work, for some time now. :-) > > Jo > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Bridge?
Rémi Guyomarch wrote: > > On Thu, Aug 02, 2001 at 06:48:42AM -0400, Ted Sikora wrote: > > I have stable on both cable and dsl. The following message (rpc.statd: > > invalid hostname to sm_stat: ^X÷ÿ¿^X÷ÿ¿^) > > has been a mainstay in stable for some time. I have 2 nic cards in the > > machines. Do I need the 'options BRIDGE' in the kernel? I just set up a > > firewall and that did not eliminate the messages. > > Someone is trying the Linux rpc.statd remote root exploit on your > machine. AFAIK it's harmless on your FreeBSD box. How can I protect my Linux machines? The messages have appeared there occasionally too. > > If you have implemented a firewall, be sure to use the "default-deny" > method (ie deny everything and only let pass the things you actually > use). I bet you don't want to provide NFS services to everyone on the > earth... > That's what I did. /kernel: IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging limited to 100 packets/entry by default -- Ted Sikora [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Intel 82562ET Kinnereth
Hello, Does anyone know if the Intel 82562ET Kinnereth (NIC) will function properly under FreeBSD? It's integrated on the Intel D815EEA motherboard. Greetings, Eric To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Beware of WindRiver Systems!
I don't know if this thread is really relevant to this list, but assuming it is, my $.02. Mine came way late only after multiple emails with windriver. Once alerted they responded quickly. I wasn't sure how soon after a RELEASE was announced to start nagging them (anyone want to answer that?). While I waited, all sorts of trouble began happening related to version shear (ports stopped building because fetch was looking for older versions of sources, could not ftp some packages from stable mirrors, etc). Biggest of these problems was the 4.2 kernel wasn't able to deal with the new computer I had bought and for a while, I was running a 4.3 kernel on an otherwise 4.2-RELEASE system (at 56k a kernel is all I'm prepared to download). -r >Date: Thu, 2 Aug 2001 13:53:02 -0600 >From: Paul <[EMAIL PROTECTED]> >Subject: Re: Beware of WindRiver Systems! > >ditto. My 4.3-RELEASE cd's came late. I don't really care, though. I >rarely use the pressed CDs. I have a subscription because I'm a long-time >FreeBSD user/administrator, and I wish to contribute something to the >FreeBSD project. Since I don't code, I pay for a subscription, and try to >turn as many new people onto FreeBSD as possible, and help newcomers learn >the basics. Regardless, though, my 4.3 CD did come, albeit a bit late. > >Once upon a time, Tony Landells <[EMAIL PROTECTED]> scribed: >> Hi Gerd, >> >> Maybe I'm just lucky, but I haven't had any problem. My 4.3 CDs >> arrived without any "intervention" on my part. Maybe a bit more >> slowly than I might have liked, but I don't need them at the moment >> so I don't really care. >> >> But then, they do say that Australia is "the lucky country" ;-) >> >> Tony >> -- >> Tony Landells<[EMAIL PROTECTED]> >> Senior Network Engineer Ph: +61 3 9677 9319 >> Australian Clearing Services Pty Ltd Fax: +61 3 9677 9355 >> Level 4, Rialto North Tower >> 525 Collins Street >> Melbourne VIC 3000 >> Australia > >Regards, >Paul ><[EMAIL PROTECTED]> >http://www.tribble.net/ > >"A free society is one where it is safe to be unpopular." >-- Adlai Stevenson > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: RELENG_4_3 calls itself -RELEASE?
Antony T Curtis <[EMAIL PROTECTED]> wrote: >"Antoine Beaupre (LMC)" wrote: >> >> Go for RUTABAGA. It's cute. > >We cannot use -APPLE, -APRICOT, -CHERRY nor -ORANGE or some company >would get very sour... > >But there is -BANANA, -PEAR, -GRAPE, -NECTARINE, -TOMATO, -MELON, >-STRAWBERRY, -RASPBERRY... > >Or maybe more exotically, -DUREN, -LYCHEE, -RUMBUTANG, -STARFRUIT... I think as long as we specifically avoid -LEMON things will be fine. Personally I think the idea of all this name changing is silly. I was one of those newbies to this list not very long ago and I once asked those questions "why is stable not stable?" If we go mucking about with the names, we're certain to be asked questions like "Okay, is -RAISIN the patched -GRAPE?" and "Why do you call it -BANANA? Why not just call it -RELEASE?" I think a version of FreeBSD which incorporates only patches that can be applied BOTH by CVSup and by simply adding patches one at a time, which seems to me is what the RELENG_4_3 branch is trying to do, is the same as applying any other system patch, and doesn't deserve a rename of the base OS. All that will do is for certain confuse scripts that use 'uname -a' to determine the installed OS. -- The idea that Bill Gates has appeared like a knight in shining armour to lead all customers out of a mire of technological chaos neatly ignores the fact that it was he who, by peddling second-rate technology, led them into it in the first place. - Douglas Adams (1952-2001) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: USB question
> Date: Fri, 03 Aug 2001 04:10:51 -0700 > From: Mike Smith <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > > I was attempting to install my new MS optical Intellimouse on the USB port > > instead of the PS/2 port, but I am getting the following when I do a 'dmesg' > > after recompliing my kernel with the correct usb drivers: > > > > uhci0: at device 7.2 on pci0 > > uhci0: Invalid irq 255 > > uhci0: Please switch on USB support and switch PNP-OS to 'No' in BIOS > > > > PNP is turned off in the bios, and the intellimouse works on the USB port in > > when I'm changing the bios (so I know it's not hardware) > > You're stuffed until Warner gets the PCI interrupt routing code into > -stable. Welcome to the Plug and Play universe. 8/ If you want to live a bit dangerously, Warner has patches for stable available now. They are working for several people (and not working for others). http://people.freebsd.org/~imp/pcic-stable.diff.15b (the version is subject to change and may be different by now.) R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Fat kernel, needs dieting (again :-)
> Someone said on [EMAIL PROTECTED]: > >> The other day a guy (sorry I forgot who) says that > > That was me, <[EMAIL PROTECTED]>, see also > >http://www.freebsd.org/cgi/query-pr.cgi?pr=29272 > > and the copy of the earlier message below. > But [EMAIL PROTECTED] (Carlo Dapor) questions this: > >And top(1) just works fine ? When I gzip(1)ed kernels in the past, everything >worked just fine, except for top(1) and IIRC ps, which could not access some >structure - sorry for being very vague here, it has been some time. > > We are refering to a kgziped LOADER (/boot/loader) not kernel! The > loader on the boot floppy can be kgzip-ed safely and the pr=29272 > above has the one-line patch enclosed. Maybe [EMAIL PROTECTED] who > was working on this might incorporate this patch too, saving us > another 60k on boot floppies? I was actually referring to a gzip(1)'d /boot/kernel/kernel. I just tried it out and it works fine with top(1) and ps(1). Ciao, derweil, -- Carlo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: moving to XFree86-4
On Thu, Aug 02, 2001 at 02:35:32PM +0100, j mckitrick wrote: | Any caveats I should look out for moving to version 4? My only issue with it, is that ports seems to be rather confused about where to register dependencies for X programs. If you have XF86 v4 installed and try to install a window manager for instance, ports will try to register the dependency with Xfree86-3.3.6_9 which is obviously wrong. Now, if you set XFREE86_VERSION=4 in your /etc/make.conf, ports will for some reason try to register a dependency with imake-4.1.0, freetype2-2.0.3_1 and XFree86-4-libraries-4.1.0, which isn't quite right either when the package you have installed is called XFree86-4.1.0_4. Ok, so this isn't a problem with X but rather a ports issue. Nitpicking, probably, but I thought I'd mention it. :-) Version 4 has otherwise been working flawlessly for me, both at home and at work, for some time now. :-) Jo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: moving to XFree86-4
Chuck MacKinnon wrote: > Why not just run xf86cfg. Then you can set up the screens and resolutions > etc. Not too hard to figure out. Sorry people, I didn't know about xf86cfg. :) I *will* try it out. I still have glitches with my old config anyways. I'm definitly getting this thread OT, however. A. -- Antoine Beaupré Jambala TCM team Ericsson Canada inc. mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: upgrade
so.. by doing cvsup, my OS from FreeBSD4.2-STABLE will change automatically to FreeBSD4.3-STABLE ? Thanks. --- Mike Meyer <[EMAIL PROTECTED]> wrote: > klein brock <[EMAIL PROTECTED]> types: > > i want to upgrade my FreeBSD4.2-STABLE to > > FreeBSD4.3-STABLE > > > > can anybody help me ? or give me some suggestion > which > > doc should i read ? > > If you're running 4.2-STABLE - and not -RELEASE - > you're already most > of the way there. Updating your source tree again, > and reinstalling > the world should do the trick. The handbook covers > this at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html > > and following. > >-- > Mike Meyer <[EMAIL PROTECTED]> > http://www.mired.org/home/mwm/ > Independent WWW/Perforce/FreeBSD/Unix consultant, > email for more information. __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: RELENG_4_3 calls itself -RELEASE?
On Fri, Aug 03, 2001 at 12:51:30PM -0500, Mike Meyer wrote: > David Kelly <[EMAIL PROTECTED]> types: > > On Fri, Aug 03, 2001 at 09:54:02AM -0400, Bob K wrote: > > > I like -BEET. It's short, means nothing, and is red. What more could > > > you ask for? :P > > Suggest -FOO has a long standing meaning of nonsense in computer lingo. > > Or -FOOBAR. > > It's not a nonsense word, it's a placeholder. If you do that, I can no > longer talk about tracking -FOO (or -FOOBAR) when I want to talk about > tracking any of the branches. OK, then back to the fruits and vegetables, which rot when left sitting around and need to be replaced before then. I propose -TOMATO as its the favorite of rotten fruit throwers. Or -EGG for that which isn't ready to hatch yet (isn't that what we are really talking about, that iffy place between -STABLE and -RELEASE?) and then we could say of the one who broke it, has -EGG on his face? I'm getting too silly for -STABLE. -- David Kelly N4HHE, [EMAIL PROTECTED] = The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: SMBFS panic: malloc: wrong bucket (was: 4.3-20010721-STABLE)
On Wed, 25 Jul 2001, Tim Zingelman wrote:
> This is a known bug, but not fixed. I worked with the maintainer, Boris
> Popov on it a little, but in my case it took some time between the mount
> and the panic, and I was not able to give him login access to the
> machines involved. As a result it remains unfixed. If you have a case
> that panics immediately and can work with him, I think he would be
> interested in getting this fixed. (I know I would :)
Please try the attached patch. It fixes a nasty buffer overflow
which may cause this panic.
> > I'd recommend contacting the smbfs maintainer. It seems the kernel
> > module for smbfs is now integrated into the main sources, but you
> > still need to install a port. So I'm guessing it's now in some sort of
> > transitional status (and thus quite unstable).
Hear, hear :) All userland code for smbfs was planned to be
included before 4.4 comes out. But, life is life - it has its own plans,
and I hope to finish import after 4.4...
--
Boris Popov
http://www.butya.kz/~bp/
Index: smb.h
===
RCS file: /home/ncvs/src/sys/netsmb/smb.h,v
retrieving revision 1.1.2.1
diff -u -r1.1.2.1 smb.h
--- smb.h 2001/05/22 08:32:33 1.1.2.1
+++ smb.h 2001/08/03 13:32:25
@@ -68,7 +68,7 @@
*/
#defineSMB_SIGNATURE "\xFFSMB"
#defineSMB_SIGLEN 4
-#defineSMB_HDRMID(p) (*(u_short*)((u_char*)(p) + 30))
+#defineSMB_HDRMID(p) (letohs(*(u_short*)((u_char*)(p) + 30)))
#defineSMB_HDRLEN 32
/*
* bits in the smb_flags field
Index: smb_crypt.c
===
RCS file: /home/ncvs/src/sys/netsmb/smb_crypt.c,v
retrieving revision 1.1.2.1
diff -u -r1.1.2.1 smb_crypt.c
--- smb_crypt.c 2001/05/22 08:32:33 1.1.2.1
+++ smb_crypt.c 2001/08/03 13:32:25
@@ -120,7 +120,7 @@
int len;
len = strlen(apwd);
- unipwd = malloc(len * sizeof(u_int16_t), M_SMBTEMP, M_WAITOK);
+ unipwd = malloc((len + 1) * sizeof(u_int16_t), M_SMBTEMP, M_WAITOK);
/*
* S21 = concat(MD4(U(apwd)), zeros(5));
*/
Index: smb_rq.c
===
RCS file: /home/ncvs/src/sys/netsmb/smb_rq.c,v
retrieving revision 1.1.2.1
diff -u -r1.1.2.1 smb_rq.c
--- smb_rq.c2001/05/22 08:32:33 1.1.2.1
+++ smb_rq.c2001/08/03 13:32:25
@@ -238,7 +238,7 @@
bcnt = rqp->sr_rq.mb_count;
if (bcnt > 0x)
SMBERROR("byte count too large (%d)\n", bcnt);
- *rqp->sr_bcount = bcnt;
+ *rqp->sr_bcount = htoles(bcnt);
}
int
