> On Jan 23, 2025, at 7:30 PM, Mark Millard wrote:
>
> Bakul Shah wrote on
> Date: Fri, 24 Jan 2025 00:15:04 UTC :
>
>> [-9fans, +freebsd-current as 9fans adds a reply-to: 9fans line]
>>
>>> On Jan 23, 2025, at 3:53 PM, Warner Losh wrote:
>>&g
[-9fans, +freebsd-current as 9fans adds a reply-to: 9fans line]
> On Jan 23, 2025, at 3:53 PM, Warner Losh wrote:
>
> I fail to see how putting code in the kernel is better than just using got
> for the few people that are alergic to git. Even if it is only 1000 lines in
> plan 9, but likely m
https://www.youtube.com/watch?v=oHO5a4l_8zY
Kenny Wayne Shepherd - Voodoo Child (Slight Return) - KTBA Cruise 2019
youtube.com
$ git bisect good
b377ff8110e3489eb6e6b920b51a2384dfc4eb0b is the first bad commit
> On Feb 9, 2024, at 8:13 PM, Mark Millard wrote:
>
> Summary:
>
> pcib0: mem 0x7d50-0x7d50930f
> irq 80,81 on simplebus2
> pcib0: parsing FDT for ECAM0:
> pcib0: PCI addr: 0xc000, CPU addr: 0x6000
On Jan 25, 2024, at 8:15 AM, Warner Losh wrote:
>
> What can fdisk and/or disklabel repair that gpart can't?
May be add a section in gpart that shows how to map fdisk &
bsdlabel functionality to gpart? Better still, why not
provide scripts for fdisk/bsdlabel that use gpart underneath?
FreeBSD sh
On Jan 3, 2024, at 11:22 AM, Brooks Davis wrote:
>
> Nothing about dates is centralized in git, but some server side checks
> could be implemented on CommitDate. IMO we should require that
> CommitDate be >= the previous one and less than "now".
Given that git commit objects form a DAG, I don't
o <= 50C the drives become 100% stable.
>
> -Max
>
> On Thu, Dec 7, 2023, 4:07 PM Bakul Shah <mailto:ba...@iitbombay.org>> wrote:
>> On Dec 7, 2023, at 3:59 PM, Warner Losh > <mailto:i...@bsdimp.com>> wrote:
>> >
>> >
>> >
On Dec 7, 2023, at 3:59 PM, Warner Losh wrote:
>
>
> *Overheating caused hang of NVMe controller or PCI bridge on SSD, or
>
> Yes. Most drive's firmware when it overheats resets. There might be something
> that the pci code can do when this happens to retrain the link, reprogram the
> config r
I build{world,kernel} on one machine but install
everything from the target machine, with /usr/obj
and /usr/src from the build machine nfs mounted.
/etc/src.conf (on target and build machines) has
PORTS_MODULES+=graphics/drm-515-kmod to build
this port at the same time. This used to work at
least u
> On Nov 15, 2023, at 7:57 AM, John Baldwin wrote:
>
> On 10/9/23 5:21 PM, Bakul Shah wrote:
>> Any hints on how to use bhyve's -G option to debug a VM
>> kernel? I can connect to it from gdb with "target remote :"
>> & bhyve stops the VM initi
Any hints on how to use bhyve's -G option to debug a VM
kernel? I can connect to it from gdb with "target remote :"
& bhyve stops the VM initially but beyond that I am not sure.
Ideally this should work just like an in-circuit-emulator, not
requiring anything special in the VM or kernel itself.
On Sep 12, 2023, at 11:59 PM, Graham Perrin wrote:
>
> (I'm a tcsh user, I can easily 'sh' before running the command.)
You can switch to zsh. Most of csh/tcsh + sh + many more features.
> baloo is not used in 273669.
It certainly feels like an inotify like use or a file-descr leak.
The bug re
On Sep 11, 2023, at 11:38 PM, Graham Perrin wrote:
>
> Can anything like systat(1) present a count, continually?
How about
while sleep 0.1; do sysctl -n kern.openfiles; done
Or you can write a small program using sysctl(3).
>
> I'd like to monitor, after log in to Plasma (X11), in c
On Aug 21, 2023, at 9:24 PM, Graham Perrin wrote:
>
> In a thread elsewhere, as an example that did not involve src.conf, Mark
> Johnston wrote:
>
>> $ cd /usr/ports/graphics/gpu-firmware-intel-kmod
>> $ sudo make reinstall FLAVOR=kabylake
>
> How might I use /etc/src.conf to achieve much the
On Dec 28, 2022, at 6:21 AM, Dan Mack wrote:
>
> I'm wondering if anyone can help point me at a good way to continously
> capture every inbound and outbound connection made to a freebsd system. I'd
> prefer a way that is native in base if possible. I don't really want to
> record all the pac
This may help? I’ve no experience with it, I just googled it for you. The
comp.sources.misc usenet group in volume 17 issue 23 (in 1991) has an undelete
program that supposedly works with 4.3BSD — probably won’t work with FreeBSD’s
version but if you’re desperate it could be a starting point.
ht
On Jun 28, 2021, at 1:39 PM, O. Hartmann wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
> Hello,
>
> we ran into serious trouble here with an www/nextcloud installation on a
> recent 14-CURRENT
> (FreeBSD 14.0-CURRENT #23 main-n247612-e6dd0e2e8d4: Mon Jun 28 18:08:20 CEST
>
On Jun 19, 2021, at 4:19 PM, Thomas Laus wrote:
>
> On 6/19/21 2:21 PM, Bakul Shah wrote:
>>
>> You may wish to see if Andriy Gapon's method (LOCAL_MODULES_DIR,
>> LOCAL_MODULES)
>> works better for you.
>>
>> I trust Makefile* to do the right t
On Jun 18, 2021, at 7:05 AM, Thomas Laus wrote:
>
> On 6/10/21 11:13 AM, Bakul Shah wrote:
>> This is what I did:
>>
>> git clone https://github.com/freebsd/drm-kmod
>> ln -s $PWD/drm-kmod /usr/local/sys/modules
>>
>> Now it gets compiled every time y
On Jun 15, 2021, at 9:03 AM, John Baldwin wrote:
>
> On 6/10/21 8:13 AM, Bakul Shah wrote:
>> On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote:
>>> The drm-kmod module is the latest from the pkg server. It all
>>> worked this past Monday after the recent drm-kmod
On Jun 10, 2021, at 9:49 AM, Philipp Ost wrote:
>
> On 6/10/21 5:13 PM, Bakul Shah wrote:
>> On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote:
>>> The drm-kmod module is the latest from the pkg server. It all
>>> worked this past Monday after the recent drm-kmod
On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote:
> The drm-kmod module is the latest from the pkg server. It all
> worked this past Monday after the recent drm-kmod update.
This is what I did:
git clone https://github.com/freebsd/drm-kmod
ln -s $PWD/drm-kmod /usr/local/sys/modules
Now it gets c
> On Mar 2, 2021, at 8:18 AM, bob prohaska wrote:
>
> A while back I obtained a buildable source tree for stable/13
> but it hasn't been updated in the last few days. Running
> git remote show origin
> reports in part
>
> Fetch URL: https://git.FreeBSD.org/src.git
> Push URL: https://git.Free
On Feb 22, 2021, at 6:29 PM, Lizbeth Mutterhunt, Ph.D
wrote:
>
> so, it's my great-grandma and has since recent update of the glib package
> the following problem when trying to start the DE or even lightdm, sddm,
> cdm... the reference output of X is:
>
> ld-elf.so.1: /usr/local/lib/libglib-2.
This is on a 13.0-STABLE system but this was also a problem while 13.0 was
-current.
If I warmboot (reboot) the system the axge USB GbE driver fails:
# dmesg|grep axge
Feb 19 15:03:00 motile kernel: axge0 on uhub1
Feb 19 15:03:00 motile kernel: axge0: on usbus0
Feb 19 15:03:00 motile kernel: ax
On Feb 12, 2021, at 4:01 PM, Russell L. Carter wrote:
>
> This reminds me of a question that I had, does a stable/13
> installworld install the bootcode? I am now guessing it
> doesn't, on account of it might be difficult to figure
> out what partition to install it to.
There are just too many
On Feb 11, 2021, at 7:13 PM, Russell L. Carter wrote:
>
> root@terpsichore> gpart show
> => 34 625142381 da0 GPT (298G)
> 341281 freebsd-boot (64K)
>16283886082 freebsd-swap (4.0G)
>8388770 6167536453 freebsd-zfs (294G)
You can do some
> On Feb 5, 2021, at 6:09 AM, George Michaelson wrote:
>
> I have a Lenovo Edge 420 with the ATI/Radeon graphics card.
>
> The "this .ko, that blob" thing is really confusing if you've been out
> of the loop for a while, and with older hardwar (its 8+ year old
> laptop) its not impossible its
On Dec 11, 2020, at 1:55 PM, Chris wrote:
>
> Well FWIW when I've been confronted with the need to perform an "unorthodox"
> upgrade
> path. I always perform a
> cd / && cp -rp /etc /eetc
> *prior* to a mergemaster(8)
> because you never know. ;-)
Just commit every *working* set of files in /et
On Dec 8, 2020, at 10:10 AM, Alban Hertroys wrote:
>
> So I tried again to move to HEAD:
>
> cd /usr/src
> svn up
> make buildworld -j12
> make buildkernel -j12
> make installkernel
> shutdown -r now
>
> mount -u /
> zpool import -Nf system
> On Nov 27, 2020, at 1:47 PM, Bakul Shah wrote:
>
>
>
>> On Nov 27, 2020, at 9:09 AM, Rebecca Cran wrote:
>>
>> On 11/27/20 4:29 AM, Hans Petter Selasky wrote:
>>>
>>> Is the problem always triggered by hald? If you disable hald in rc.co
> On Nov 27, 2020, at 9:09 AM, Rebecca Cran wrote:
>
> On 11/27/20 4:29 AM, Hans Petter Selasky wrote:
>>
>> Is the problem always triggered by hald? If you disable hald in rc.conf,
>> does the system run for a longer period of time?
>
> It turns out that disabling ntpd let the system run f
On Oct 3, 2020, at 3:14 PM, Steffen Nurpmeso wrote:
>
> And still "git fetch" fails with
>
> POST git-upload-pack (chunked)
> error: RPC failed; curl 55 OpenSSL SSL_write: Broken pipe, errno 32
> fatal: the remote end hung up unexpectedly
>
> My config file is
>
> [core]
>repositoryfor
Trying "make -j8 buildworld" with a very recent tree (revision 366156).
This fails with
/usr/src/sys/contrib/openzfs/lib/libspl/include/sys/simd.h:34:10: fatal error:
'cpuid.h' file not found
#include
Could this be related to the flags I am using (in particular not
building CLANG)?
$ cat /etc/
On Sep 18, 2020, at 11:21 PM, Warner Losh wrote:
>
> These are the main ones. The three down sides are lack of $FreeBSD$ support
> and tags in general.
Can a git hook be used for this?
>
> Yes. I've started doing a series of short videos explaining the change, why
> we are doing it and what to
On Mar 10, 2020, at 9:24 AM, Theron wrote:
>
> On 2020-03-10 01:38, Peter Jeremy wrote:
>> Are you running NTP? If so, is NTP maintaining lock and what is the
>> reported PLL frequency (ntpq -c kerni)?
>
> Didn't show any useful difference, "kernel status: pll unsync" when I tested
> this.
Ma
On Sun, 04 Dec 2011 16:42:04 PST Julian Elischer wrote:
> On 12/4/11 3:36 PM, Randy Bush wrote:
> >
> > i suspect that my install pattern is similar to others
> >o custom install so i can split filesystems the way i prefer,
> > enabling net& ssh
> >o pkg_add -r { bash, rsync, emacs-
On Mon, 03 Jan 2011 22:21:51 +0300 Anonymous wrote:
> Bakul Shah writes:
>
> > On Mon, 03 Jan 2011 21:20:42 +0300 Anonymous wrote:
> >>=20
> >> Do you mean perror(1)?
> >>=20
> >> $ perror 5
> >> Input/output error
> >
&
On Mon, 03 Jan 2011 21:20:42 +0300 Anonymous wrote:
>
> Do you mean perror(1)?
>
> $ perror 5
> Input/output error
I prefer mine:
$ errno () { grep "^#.*\\<$*\\>" /usr/include/sys/errno.h }
$ errno 5
#define EIO 5 /* Input/output error */
$ errno EIO
#define EIO
On Tue, 09 Nov 2010 08:45:14 PST Julian Elischer wrote:
> During the discussion at MeetBSD the question came up as to what the real
> limiting factors were with regard to how much RAM a system could have.
> it was put to us that the limit was currently around 512 GB, though no-one
> at teh discus
On Fri, 20 Aug 2010 21:33:08 +0200 =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=
wrote:
> "C. P. Ghost" writes:
> > After all LISP-like syntax is *still* more common and prevalent
> > than Lua, e.g. in Elisp, guile, esh, scsh and a lot of other apps
> > that use it as a small language. So we can expect
On Thu, 19 Aug 2010 20:35:59 +0200 "C. P. Ghost" wrote:
>
> But seriously, the point isn't so much which specific interpreter
> we use (if we go down this road), it's about libraries: most
> sysadmin tasks require some basic networking and I/O,
> and a FFI to seamlessly call out C functions from
On Thu, 19 Aug 2010 18:00:54 +0200 "C. P. Ghost" wrote:
> On Wed, Aug 18, 2010 at 3:43 PM, Andrew Reilly wro=
> te:
> > On Sun, Aug 15, 2010 at 11:15:55PM -0700, Doug Barton wrote:
> >> got any other suggestions?
> >
> > This is very much a "sorry I asked" question, but is none-the
> > less quit
On Tue, 03 Aug 2010 20:21:56 +0200 Gabor Kovesdan wrote:
> Em 2010.08.03. 19:25, poyop...@puripuri.plala.or.jp escreveu:
> > Hi,
> >
> > It seems bsdgrep does not work when piped from tail -f.
> > I'm running r210728.
> >
> > term0$ jot 10> /tmp/1
> > term0$ tail -f /tmp/1 | grep 0
> > [no outpu
On Mon, 31 May 2010 12:33:18 MDT "M. Warner Losh" wrote:
>
> : > It is clear that not everyone has the same view of what the
> : > acceptance criteria might be so publishing it would help
> : > people understand what to expect.
> :
> : nothing changes for the ports, there's an ongoing project t
On Mon, 31 May 2010 09:52:48 +0200 Roman Divacky wrote:
>
> I would like to propose to integrate clang/LLVM into FreeBSD HEAD
> in the near future (days, not weeks).
>
> clang/LLVM is a C/C++/ObjC compiler (framework) which aims to possibly
> replace gcc. It is BSDL-like licensed. The sources a
> > Is fsck really that memory heavy so that it needs swap?
>
> Yes, if you have a huge FS.
>
> The problem is that the checking of the CG bitmaps during an fsck
> require that you have all the bitmaps in core
Hmm
For a one TB FS with 8KB block size you need 2^(40-13) bits
to keep track of b
> > UFS is the real problem here, not fsck. Its tradeoffs for
> > improving normal access latencies may have been right in the
> > past but not for modern big disks.
...
> Sorry, but the track-to-track seek latency optimizations you
> are referring to are turned off, given the newfs defaul
> You talk like I have a choice :-)
> I cannot change ufs/ffs and even if I could the clients wouldn't go for
> it.
What about changing the size of block size or cyl grp size?
Do they change things much?
> The problem space is
>
> Fsck of UFS/FFS partitions is too slow for 200GB+ filesystems.
>
> Now, before we go off and design YABFS, can we just get real for
> a second ?
I leave it to others to design YAFS, I just wanted to
complain about this one :-) Every few years I seriously look
at speeding up fsck but give up. I remember even asking
about it a few years ago on one of these grou
UFS is the real problem here, not fsck. Its tradeoffs for
improving normal access latencies may have been right in the
past but not for modern big disks. The seek time & RPM have
not improved very much in the past 20 years while disk
capacity has increased by a factor of about 20,000 (and GB/$
ev
> Since it works with 4.7-STABLE it must(?) be a current problem
> more than a XFree86 problem. Or?
I had the same problem -- something to do with files left
over from the original 4.7 installation. Cured by
deinstalling XFree86-* ports, renaming /usr/X11R6 to
something else (in case something wa
> Interesting The SunOS output exactly matches random(3)
> behavior from 4.3BSD! In fact random() remained the same for
> 4.3BSD-Reno, -Tahoe, 4.4BSD-Alpha and Net2.
>
> 4.2BSD random() behavior is different from all of the above.
> There was real bug-fix between 4.2BSD and 4.3BSD.
>
> I do
> Last 10 digits.
>
> FreeBSD Redhat SunOS
> 660787754660787754645318364
> 3275486913275486911583150371
> 2009993994 2009993994 715222008
> 1653966416 1653966416 1349166998
> 1074113008 1074113008 566227131
> 2142626740 2142626740 1382825076
> 15177758
> > another suggestion: why not fold your algorithm change in
> > that function? For example,
> >
> > initstate(seed, "RC4", 3);
> >
> > changes the algorithm to RC4. Yes, this is a change in the
> > interface but one I am sure most people can live with.
>
> No. Evil interface change. #ifd
> Since you keep talking about random(), I must conclude you're
> knee-jerking, since we're not discussing that function. Please stay
> on-topic :-)
Read through the thread. In particular see Mark's message
<[EMAIL PROTECTED]> where he
says
Good point. We can re-implement random() internall
> Would you prefer that we defined random() as
>
> int
> random(void)
> {
> static int retval = 0;
>
> return retval++;
> }
No because that would be a change from the exisiting random()
behavior :-)
As I indicated in my earlier email random() is not broken,
srand() is (as corrected
> a restriction on the OS. If FreeBSD makes random2() using RC4 to avoid
> changing rand() or random(), will people then start relying on random2()'s
> behaviour, and when someone finds a problem in RC4, then the next will be
> random3()?
What I am suggesting is to leave random() as it is and
> Maybe I missed something, but why cannot you just rip random() from libc,
> rename it to bakul_shah_random() and use that in your testing code? Then you
> are safe from any changes to random(), and indeed have a portable RNG if your
> host OS changes.
Yes, *I* can do it but I don't work at eve
> RC4 is _utterly_ repeatable, given a particular seed/key.
May be but it is not the same as the current random(). Also,
I know you will want to change it the next time some one
points out a problem with RC4.
> Yes. And it breaks, and we have a complainant.
So create a new function! Or use a d
> As I said, I don't know how big a concern this is. But last time
> it was enough of a concern to make us keep rand() as it was.
[I know you are talking about rand() but Mark Murray's
earlier email about wanting to re-implement random() really
concerned me so I want to make sure my point gets ac
> Good point. We can re-implement random() internally with arc4rand().
>
> Objections?
Guys, please realize that random() is also used in generating
simulation inputs (or timing or whatever). If you go change
the underlying algorithm or its parameters one can't generate
the same sequence from th
> Technically, the compiler doesn't need prototypes at all; they
> are merely a band-aid for the compiler vendors, who did not want
> to have to deal with changing object file format.
IMHO the value of prototypes is in documenting a function
interface rather than for the vendors. Compilers of
lan
> > I can't see what actual error is avoided by this warning.
s/actual/potential/
>
> If a named prototype clashes with something in global scope,
> isn't it still a shadowing issue? They should probably never
> be *in* scope.
Nothing is being shadowed. Paramater names in a function
prototype
> Julian Elischer writes:
> > I don't know about the protection with a '_'.
> >
> > It's not standard and usually the name matches that used in the actual
> > function.
>
> When the prototype parameter name matches a local variable, the C compiler
> (and lint) whine about clashes between names in
> Brooks Davis wrote:
> > This isn't going to have an effect on the ability to use kernel ppp for
> > other things. The tty orientation of pppd and the outdated, unmodular
> > design on ppp(4) have taken care of that. This patch gives people
> > the functionality they want (pppd just working) wit
> Here's a new patch that gives the user more of a hint at how to add PPP
> support and only loads the module if they are actully root. How's this
> look?
I still don't like it. How to explain
I don't think it is pppd's responsibility to muck with
modules. It is like mount kldloading a dis
> > Until pppd is taught to create the interface if one doesn't
> > exist, this information needs to be in /usr/src/UPDATING.
>
> pppd doesn't need to be taught to create the interface. Rather it needed
> to learn to check for ppp support in a non-stupid way. The following
> patch should do it a
> On Fri, Oct 25, 2002 at 06:15:55PM +, Dave Evans wrote:
> > Is anyone using pppd on CURRENT. somewhere between may and October it
> > seems to have broken. My KERNEL is GENERIC, my sources are dated cvs
> > -D2002-10-20, but I now get a message about needing facilities in the
> > kernel. Ho
If the ldconfig_insecure flag is set in /etc/rc.conf,
ldconfig doesn't do anything useful at startup time except
complain. The following patch should fix it.
diff -ur /usr/src/etc/rc ./rc
--- /usr/src/etc/rc Tue Sep 17 21:02:01 2002
+++ ./rcSun Sep 22 16:49:19 2002
@@ -692,9 +692,10
> Yes. we are aware of the work and we are pleased that it is hapenning, but
> few of us have even SEEN any bluetooth stuff yet..
> certainly in the US it's not yet being marketted a lot.
Fry's Electronics in the SF bayarea has a bunch of bluetooth
gadgets. Go to www.outpost.com and search for
> You are blowing this out of proportion and not actually reading
> what people are proposing. So far, the comments are about
> removing a.out support from the base compiler and offering
> a.out binutils and gcc _as ports_.
A port is fine -- but this was proposed much later in the
thread.
> > U
> > > Where exactly does GCC fit into the mix, making this impossible?
> >
> > They compile Lisp (etc) to a C file, which they compile (with gcc) to
> ^^^
> actually with as(1), because gcc is only generates assembler file,
> which is
I said:
> my guess is John Gilmore originally created gnu tar from
> reading of the man page. If so, that would explain the
> difference. I don't have the V7 sources so can't check but
> given that companies with the Unix licence (and the orig.
> sources) all do the same I believe the V7 man pag
> Well, OK, now I am really confused. So what should we be bound to? To
> the POLA (old GNU tar in 4.6-release and downward was not fully
> preserving permissions unless -p is specified, even when invoked by
> root)? Or to what other systems do? Bruce, what do you think?
Okay, I did some more res
My recollection matches what Bruce says (and I have been
using unix since when version 7 was the latest and greatest).
At least the SUN OS 5.6 man page I could locate online says
this:
The o function modifier is only valid with the x function. p
Restore the named files to their original modes,
> Yes, that code is very broken indeed. It probably was supposed to
> call __rpc_setconf("udp") and not getnetconfigent("udp"), but that
> seems to pick up an ipv6 address. I think the best plan is to go
> back to the way that part of the code was before revision 1.10.
>
> Could you try the follo
TCP mount of nfs seems to be broken.
# mount bar:/usr /mnt
[tcp] bar:/usr: RPCPROG_NFS: RPC: Unknown protocol
I tracked this down to lib/libc/rpc/rpcb_clnt.c. Seems like
the problem is in __rpcb_findaddr_timed().
diff -r 1.9 rpcb_clnt.c
--- rpcb_clnt.c 22 Mar 2002 23:18:37 - 1.9
+++
Try this:
$ csh
% su
Password:
% stop $$
Suspended (signal)
%fg
At which point you will lose you login shell.
Prior to KSE one could switch between an su'ed shell and a
normal shell at will by using stop $$ and fg.
Is this breakage considered a bug or a feature?
To Unsubscribe: send mail to
> That there could be a real error in that code surprises me, since
> Peter really knows what he's doing, even if that low in the
> hardware, there are undocumented interactions that even Intel's
> errata doesn't seem to know about.
Turns out the workaround is to use DISABLE_PG_G.
Two things mad
> I believe setting DISABLE_PSE in the config file and rebuilding
> will make this go away.
Terry, thanks for the suggestion but that didn't do it.
Time to review recent changes and single step the kernel.
BTW, how do you stop the kernel before it panics? It
panics so early that there is no time
I've run into a very similar bug -- the kernel panics almost
right after it is started by the loader. With remote gdb
I've traced it to this point so far:
(kgdb) target remote /dev/cuaa0
Remote debugging using /dev/cuaa0
pmap_set_opt () at /usr/src/sys/i386/i386/pmap.c:449
449
$ dmesg | head | tail -4
CPU: AMD Athlon(tm) XP 1700+ (1466.51-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x662 Stepping = 2
Features=0x383f9ff
AMD Features=0xc048<,AMIE,DSP,3DNow!>
$ ./pt
Testing PAUSE instruction:
Register esp changed: 0xbfbff860 -> 0xbfbff824
To Unsubscribe:
> BGP is a better idea (of course).
>
> You might also consider using BGP.
>
> And have I mentioned BGP? 8-) 8-).
Whether to use BGP/OSPF is orthogonal to multipath use. Both
OSPF and BGP allow you to install multiple next hops. Adding
multipath support requires, at a minimum, changing struc
> the trick nicely (but is too ``complicated'', and I'd still like
> having a tool that allows userland to call stat/fstat(2):
You are not alone; a number of stat(1) commands seemed to
have popped up over the years. My friend @ SGI told me IRIX
also has such a command. I liked its options so I
> $ stat -a stat
Oops! A few lines got eaten!
$ stat -a stat
May 19 00:24:42 2002|48|May 19 00:24:42 2002|291846|-|bakul|0|262301|1|May 19 00:24:42
2002|rwxr-xr-x|1095744|23996|-|bakul|stat
$ stat -a -n stat
1021793082|48|1021793082|291846|0|1001|0|262301|1|1021793082|755|1095744|23996|10|
> Paul Herman <[EMAIL PROTECTED]> wrote:
> > On Sun, 19 May 2002, Dima Dorfman wrote:
> >
> > > How about fixing ls(1) to output the numeric mode if asked to?
> >
> > That's good, but while you're at it you'd probably want to get
> > *everything* out of (struct stat) and print it numerically (de
Your questions belong to freebsd-questions!
> I created a separate partition for /usr/src (around 420MB) and cvsup ran
> out of space. Can someone give me a rough idea of how big it is? Also,
> I should be able to use growfs (after booting off of a floppy) to increase
> the size of the partitio
> well this is th idea, because I think that bcopy is probably a safe
> operation
> on the volatile structures if the driver knows that they are presently
> owned by it.. (e.g. mailboxes)
*probably* safe? For truly volatile memory bzero & bcopy are
*not* safe. Anyone remember the origial 6800
> > $ size scheme
> >textdata bss dec hex filename
> > 6134244763480 69298 10eb2 scheme
>
> Is that statically-linked? I'm curious to know the size of the bootloader
> forth footprint. The loader is about 150k, so I'm sure you could probably
> fit a nice Schem
> > I doubt if the bootloader will ever change from FORTH, but if it
> > does, I suggest LISP as the preferred choice on a short-list of
> > potential replacements.
>
> Show us a suitable LISP interpreter, then.
I don't know what size constraints the bootloader has to have
but the smallest two l
> > So it seems to me the _use_ of a "" target symlink
> > (in all but the final path component position) is exactly
> > equivalent to the use of a "/" target symlink. When used in
> > the final path component position, you get either the symlink
> > or ENOENT. The POSIX excerpt Garrett quoted s
> NetBSD committed essentially this patch 4 years ago (as part of rev.1.23).
> I like it, except it seems to be incompatible with POSIX.1-200x.
> The bug that stat(2) on a null symlink classifies the target of the symlink
> as a directory is caused by resolving the pathname to "" and then not
> r
I upgraded my system from the -current sources as of Aug-1 to
Nov-4 and find that now the mouse pointer skips while
dragging -- the pointer tracks mouse motion fine for a while,
then freezes and then jumps to a new location quite a few
pixels away. The same thing happens under X as well as on a
v
> Do we really need 5 year old history?
That really depends on your point of view.
"Those who cannot remember the past are condemned to repeat it"
-- Santayana
"The only thing we learn from history is that we learn nothing from history."
-- Hegel
I am with Hegel
> I think we should layout a plan of everything that everyone is working
> on
> and try find a natural inflection point. I reallu thing that IPV6 is too
> important to make a release with it "half" implemented.
What would be nice is a table of features versus release in
which they appear. Somet
> So, would having a kernel config utility help us get better
> reviews? I was thinking about something like an explorer-type
> thing that was divided into two panes. On the left would be
> LINT. Here, we would have icons representing the various
> devices. For example, we could ahve an icon r
> With the FreeBSD 4.0 code freeze fast approaching, are there any
> compelling reasons to keep enigma (src/usr.bin/enigma) in the
> source tree?
How dare you be so anti-bloat, living so close to Redmond?:-)
[But otherwise a nice place, Seattle. I used to live there]
Enigma is just a format co
Running rvplayer crashes the system. Catting a small .au
file works but a large one panics the system so I think the
problem may just be the drq difference. I know a number of
people in the FreeBSD crowd have this system (a Toshiba
Equium 6200M -- a `good' buy 15 months back) so this can't be
an
99 matches
Mail list logo
