Linux emu question
I noticed some people talking about the linux emulation and how good/bad it can be and I just wondered, does anybody here have any experiences with the vmware for linux software? I have been thinking of buying this, for those one or two windows programs that I need to use now and then. Just wondering, James. --- ICQ #19675056 Public key available at: http://www.dreamscape.com/halstead/jh.asc --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux emu question
I was asking this yesterday as well ... /usr/ports/emulators/vmware2 is a pretty new port as far as I can make out. I had to upgrade to 4.0-STABLE to make it work on my machine, but it does work, network, sound and all. Seems stable to me. You also *need* the linuxprocfs port installed and mounted for the thing to work. Currently I have it running Win 98. Thanks to everyone who put in the work to make this work! Colman [I've cc'ed this to -questions in the vague hope that future searches of the mail archive will pick it up ... I only worked this out by looking on freshports!] I noticed some people talking about the linux emulation and how good/bad i t can be and I just wondered, does anybody here have any experiences with th e vmware for linux software? I have been thinking of buying this, for those one or two windows programs that I need to use now and then. Just wondering, James. --- ICQ #19675056 Public key available at: http://www.dreamscape.com/halstead/jh.asc --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message PGP signature
Re: file creation times ?
Such editors are broken. What if the file is a symlink ? IMHO open() write() write() write() ftruncate() close() is the only way. If that is the only way, then emacs is of course broken. (And I disagree - I use emacs every day...) Now there's an argument waiting to happen :-) So if you create a file and make it writable by me and I edit it, it becomes mine ? Good ol' emacs ! I would guess that in real life it *must* be smart enough not to do this (I don't have access to emacs from here right now). Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: file creation times ?
Such editors are broken. What if the file is a symlink ? IMHO open() write() write() write() ftruncate() close() is the only way. If that is the only way, then emacs is of course broken. (And I disagree - I use emacs every day...) Now there's an argument waiting to happen :-) So if you create a file and make it writable by me and I edit it, it becomes mine ? Good ol' emacs ! I would guess that in real life it *must* be smart enough not to do this (I don't have access to emacs from here right now). emacs is of course much smarter, and it's also customizable. I was just reacting to the blanket statement that "open() write() write() write() ftruncate() close() is the only way". Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
ncurses.h and #define trace _nc_trace
The following change to /usr/include/ncurses.h which adds a
#define trace _nc_trace
causes problems with our Wine port and probably further software:
1.1.1.3 (vendor branch) Wed May 24 10:44:45 2000 UTC by peter
CVS Tags: v5_0_19991023, HEAD; Branch: NCURSES
Bring in the fix for the trace/_nc_trace issue, without breaking the
vendor branching. The author has fixed this also so we can do this
safely.
1.1.1.2.2.1 Tue May 23 13:42:17 2000 UTC by ache
Branch: RELENG_4
MFC: trace - _nc_trace
For example, consider the following snippet:
void _nc_trace() { }
#define trace _nc_trace
main() {
long trace=0;
if( trace != _nc_trace )
printf("Okay\n");
}
As another example, consider Wine, where this change causes:
../libwine.so: undefined reference to `__GET_DEBUGGING__nc_trace'
due to a new interaction with the TRACE macro in debugtools.h.
http://cvs.winehq.com/cvsweb/wine/include/debugtools.h?rev=1.9 has
the source of that Wine include file.
In my opinion, we either have to show that the code in Wine is in
violation of ANSI/ISO C, or find a way to fix ncurses.
How about adding a stub instead of a #define? Performance really
shouldn't be an issue in this case!
Gerald
--
Gerald "Jerry" [EMAIL PROTECTED] http://www.dbai.tuwien.ac.at/~pfeifer/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: review request: truncate(1)
Thus spake Johan Karlsson ([EMAIL PROTECTED]): However, the man page does not mention that one have to also specify the wanted size of the file. Oooops :-) *correcting* Alex -- I need a new ~/.sig. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: review request: truncate(1)
Hi again,
I found your updated version and I look good.
However, I just realised that I would get ride of the modeset variable by
moving the default assignment of mode to the begining.
/Johan K
--- truncate.c.orig Fri May 26 10:34:54 2000
+++ truncate.c Fri May 26 10:37:52 2000
@@ -46,8 +46,9 @@
int fd;
int optch;
mode_t mode, *modp;
- int modeset = 0;
+ mode = S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH;
+
while ((optch = getopt(argc, argv, "hm:")) != -1)
switch (optch) {
case 'h':
@@ -59,7 +60,6 @@
umask(0);
mode = getmode(modp, 0);
free(modp);
- modeset = 1;
break;
case '?':
default:
@@ -74,8 +74,6 @@
usage();
exit(1);
}
- if (!modeset)
- mode = S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH;
size = atol(*argv++);
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Dell-7500 + Atapi CD-R wierdness
I have an atapi CD-R drive in my laptop. under windows I created a disk, using the Adaptec CD-DIRECT software. (UDF-1.50) now I'm using it as a sample of a UDF 1.50 filesystem fo my UDF code. however I've hit something rather puzzling: if I do dd if=/dev/acd0c of=stuff and analyse that file, I get different results than if I access the drive directly. in a similar vein, when I randomly access block 108362, I get block 108362, but when I access the disk sequentially, I find that data at block 108366, 4 blocks away. Does anyone have any clues? Specifically I've heard stories of CDrom devices having very 'approximate' seeking, but this is a bit much, and I thought that was only when in audio mode.. -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000 --- X_.---._/ presently in: Perth v To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: file creation times ?
Peter Jeremy writes: On 2000-May-25 19:03:56 +1000, Brian Somers [EMAIL PROTECTED] wrote: Of course access timestamps are usually useless anyway as most (?!!) people will back up their system from time to time OOPS ! I never realised before now - dump *doesn't* update the access time. This is because dump bypasses the filesystem (it reads the underlying device). Therefore the filesystem doesn't see the access. Other backup tools (tar, pax, cpio etc) access the files through the FS amd therefore alter the access time. Some have the ability to reset the access time afterwards - but that updates the change time, which is probably worse. This is probably good justification for a O_NOTACCESS (ie, this isn't a real access) flag on open(2) to request that the access time isn't updated. I check it in FreeBSD 4.0-R open do not change atime. In general, access time is probably the least important of the timestamps. This is reflected in the treatment of access time updates - unlike all other inode updates, they are not written synchronously (non-softupdates) and don't affect soft-updates write-ordering (so atime updates can be lost). As I see it, the major use of access times would be for a true hierarchical storage manager (which transparently migrated un- referenced files to a tape-library or similar). It's also good for things like deleting `old' files in /tmp. See ports/18813: new port: misc/deleted this daemon uses access times [skip]. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
fatal trap 12: page fault while in kernel mode
Hello, I posted a message to -questions yesterday about a machine that had the /dev directory somewhat corrupt. I could ls -la /dev/wd0* but when I was in the /dev director when I did an ls it was not showing any of the files. Now, today the machine was rebooting over and over again, freezing with this message: fatal trap 12: page fault while in kernel mode fault virtual address = 0xc33a3c6d fault code = supervisor read, page not present Instruction Pointer = 0x8:0xc022798F Stack Pointer = 0x 10: 0xc5dc6988 code segment = base 0 x0, limit 0xf type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL =0 current process = 5 (init) interrupt mask = trap number = 12 panic: page fault syncing disk 1 1 1 1 1 1 1 1 1 giving up rebooting in 15 seconds It does this over and over again. i am running 3.3-R..Is it a memory problem? Thanks for any help or hints. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RTLD_NODELETE, RTLD_NOLOAD dlopen mode flags
hi, there! Are there any plans to implement RTLD_NODELETE and RTLD_NOLOAD mode flags for dlopen? from Solaris 2.6 man 3X dlopen: The following modes provide additional capabilities outside of relocation processing: RTLD_NODELETE The specified object will not be deleted from the address space as part of a dlclose(). RTLD_NOLOAD The specified object is not loaded as part of the dlopen(), but a valid handle is returned if the object already exists as part of the process address space. Addi- tional modes can be specified and will be or'ed with the present mode of the object and its dependencies. The RTLD_NOLOAD mode provides a means of querying the presence, or promoting the modes, of an existing dependency. /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ncurses.h and #define trace _nc_trace
On Fri, May 26, 2000 at 10:42:07AM +0200, Gerald Pfeifer wrote: How about adding a stub instead of a #define? Performance really shouldn't be an issue in this case! Yes, #define was a quick solution. We need either to add a stub or to import ncurses author fix (removing all trace function from production library). Latest is better IMHO, but I left to choose best way to Peter. -- Andrey A. Chernov [EMAIL PROTECTED] http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Unexpected reboot.
I posted this awhile back I didnt get much response. Basically, I have a machine with FreeBSD 4.0-RELEASE. Every couple of days it reboots for now reason. When I looked at the logs, it shows regular log data, then the next line reads "/kernel: Copyright (c) 1992-2000 The FreeBSD Project. Then the standard kernel stuff gets listed. At the end of the kernel data is says WARNING: / was not properly dismounted. There is nothing before the kernel data about shutting down or rebooting. I have an Intel PRO/100+ network card, U2W scsi. Has anybody encountered something like this? This same hardware configuration has no problems with other versions of FreeBSD, could it be a 4.0 problem. Any help would be great. Thanks. -john von essen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Unexpected reboot.
This to make the memory settings more conservative. I had that too earlier, and after I changed that the machine became much more stable: 5:01pm up 62 days, 20:10, 4 users, load averages: 2.31, 2.12, 1.86 (nfs-buildworld/ports server) Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Unexpected reboot.
On Fri, 26 May 2000, Essenz Consulting wrote: I posted this awhile back I didnt get much response. Basically, I have a machine with FreeBSD 4.0-RELEASE. Every couple of days it reboots for now reason. When I looked at the logs, it shows regular log data, then the next line reads "/kernel: Copyright (c) 1992-2000 The FreeBSD Project. Then the standard kernel stuff gets listed. At the end of the kernel data is says WARNING: / was not properly dismounted. There is nothing before the kernel data about shutting down or rebooting. I have an Intel PRO/100+ network card, U2W scsi. Has anybody encountered something like this? This same hardware configuration has no problems with other versions of FreeBSD, could it be a 4.0 problem. Any help would be great. Thanks. -john von essen I John, I've experienced simulair problems , and tracked it down to hardware. (sorry no debugging, just switched some components..) At this moment i've runnig lot's of boxes 4.0 whithout any problem at all.. suggestion: for me it was in bogus memory.. grtz patrick -- Patrick Barmentlo [EMAIL PROTECTED] - pgp key ID 0x8E372335 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Unexpected reboot.
Essenz Consulting writes: I posted this awhile back I didnt get much response. Basically, I have a machine with FreeBSD 4.0-RELEASE. Every couple of days it reboots for now reason. When I looked at the logs, it shows regular log data, then the next line reads "/kernel: Copyright (c) 1992-2000 The FreeBSD Project. Then the standard kernel stuff gets listed. At the end of the kernel data is says WARNING: / was not properly dismounted. There is nothing before the kernel data about shutting down or rebooting. I have an Intel PRO/100+ network card, U2W scsi. Has anybody encountered something like this? This same hardware configuration has no problems with other versions of FreeBSD, could it be a 4.0 problem. Any help would be great. Thanks. I see it on 3.3-R and 3.4-R, it is rare on 4.0-R and almoust absent on FreeBSD badaxe.duty.ru 4.0-STABLE FreeBSD 4.0-STABLE #0: Sun May 7 21:12:08 MSD 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/badaxe i386 but still occur sometimes : ahc0: Adaptec 2940 Ultra SCSI adapter port 0x6c00-0x6cff mem 0xe042-0xe0420fff :irq 11 at device 8.0 on pci0 : ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs and : xl0: 3Com 3c905-TX Fast Etherlink XL port 0x7400-0x743f irq 9 at device 10.0 on :pci0 : xl0: Ethernet address: 00:60:97:5d:a2:7d : miibus0: MII bus on xl0 : nsphy0: DP83840 10/100 media interface on miibus0 : nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto : xl0: supplying EUI64: 00:60:97:ff:fe:5d:a2:7d with : CPU: AMD-K6(tm) 3D+ Processor (400.91-MHz 586-class CPU) : Origin = "AuthenticAMD" Id = 0x591 Stepping = 1 : Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX : AMD Features=0x8800SYSCALL,3DNow! AMD-K6-III processor and : pcib1: VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge at device 1.0 on pci0 : isab0: VIA 82C586 PCI-ISA bridge at device 7.0 on pci0 : atapci0: VIA 82C586 ATA33 controller port 0x6400-0x640f at device 7.1 on pci0 : chip1: VIA 82C586B ACPI interface at device 7.3 on pci0 VIA MVP3 chipset on PA-2013 mainboard but I now noticed that PA-2013 have special revision to work with AMD-K6-400 I have not. there is sometimes Apr 8 17:53:29 cicuta /kernel: (da0:ahc0:0:0:0): data overrun detected in Data-in phase. Tag == 0xb. Apr 8 17:53:29 cicuta /kernel: (da0:ahc0:0:0:0): Have seen Data Phase. Length = 8192. NumSGs = 1. Apr 8 17:53:29 cicuta /kernel: sg[0] - Addr 0x58ed000 : Length 8192 messages in addition to locks. I have no troubles at all with this hardware and 2.2.7-RELEASE -- @BABOLO http://links.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux emu question
James, You can download a fully functional 30-day evaluation version of VMWare and see for yourself (make sure you tell them that your "distribution of Linux" is FreeBSD). There are two ports in the FreeBSD ports collection -- /usr/ports/emulators/vmware1 and vmware2, which make installation a lot easier. I haven't tried VMWare2, because VMWare1 does everything I need and I don't want to fix what ain't broken. NT4.0 works very well in a virtual machine (with VMWare tools installed), just a bit slower than running on the actual hardware. Make sure your graphics adapter supports DGA (I have Matrox G200), and your disks are fast (mine are Ultra66 DMA). You also need to mount linprocfs, and install the rtc device (also in ports). Alex P.S. BTW, questions about Linux emulation should be sent to freebsd-emulation. James Halstead wrote: I noticed some people talking about the linux emulation and how good/bad it can be and I just wondered, does anybody here have any experiences with the vmware for linux software? I have been thinking of buying this, for those one or two windows programs that I need to use now and then. Just wondering, James. --- ICQ #19675056 Public key available at: http://www.dreamscape.com/halstead/jh.asc --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD kernel as a replacement for Linux kernel
Duncan Barclay wrote: I have in my archives some code from the "person" who usually brings up the logical name stuff (the code implements them). However, there is also this snippet: PS: if you need the changes to namei() for variant symbolic links, ask me nicely, and I will disentangle them from my other changes to namei() for layering fixes, Unicode, and alternate namespace support (used by a modified (CIFS enhanced) Samba server which needs to have the DOS short name remain constant across directory searches). So who wants to ask him for them? The funny thing is... I'd have more trouble identifying the author of a snippet from a mail by my own mother than that snippet above. :-) (otoh, that's not funny... that' scary! :) -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "Sentience hurts." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
4.0 - Isa devices not being probed
My 4.0 system doesnt probe ISA devices on my system. Whats the trick? Is there a config requirement with old-style drivers? Dennis To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: fatal trap 12: page fault while in kernel mode
On Fri, 26 May 2000, Greg Skouby wrote: Hello, I posted a message to -questions yesterday about a machine that had the /dev directory somewhat corrupt. I could ls -la /dev/wd0* but when I was in the /dev director when I did an ls it was not showing any of the files. Now, today the machine was rebooting over and over again, freezing with this message: fatal trap 12: page fault while in kernel mode fault virtual address = 0xc33a3c6d fault code = supervisor read, page not present Instruction Pointer = 0x8:0xc022798F You have to post more information. For example, what is at the location pointed at by the instruction pointer? Get a stack trace, if possible (from the debugger), and any other relevant info., most of which is explained in the Handbook. -- Bosko Milekic * pages.infinit.net/bmilekic/index.html * www.technokratis.com [EMAIL PROTECTED] * [EMAIL PROTECTED] * [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Needed: suid library calls [or pkey's?]
At 6:01 PM -0700 5/25/00, Kris Kennaway wrote:
On Thu, 25 May 2000, Garance A Drosihn wrote:
It was called program keys, or 'pkey's. When a program
was running, there was this pkey attribute (in addition
to uid and gid). The pkey was a 16-character value (if
I remember right). Each executable had a pkey associated
with it, and that value became the current pkey when the
program started to execute. Users could change the pkey
There's an inherent security weakness to beware of in this
system under UNIX: (non-set[ug]id) processes are inherently
untrustable things - for example you can attach to the
running program with a debugger and make it run your own
code no matter what was already there. [...]
Indeed. The same was true on the OS this comes from. I was
worried my message was getting too long, so I skipped over
some of the details that come up when implementing this.
The alternative is to prevent attaching debuggers to any
process which runs with one of these extended credentials,
like we do for set[ug]id binaries (this is probably the
sensible solution).
That's basically how we handled it.
Such a system could probably be implemented fairly easily
within the framework of the "extended attributes"/ACL system
already in FreeBSD along with what's being developed for
TrustedBSD. Specifically, you'd store a credential ("pkey")
as an extended attribute on a binary, and have an ACL system
which knows about these credentials as well as whatever other
access policies you want (POSIX.1e ACLs, traditional UNIX file
permissions, etc).
When I wrote my message, I really was just wandering down
memory lane to talk about a feature I missed from my earlier
systems-programming days. The more I think about it, the more
it sounds like this is something which really COULD be done
for FreeBSD (at least as an option). I'll have to think about
this some more, as it really would be nice to have this. I
guess I first have to learn more about the extended-attributes/
ACL system in freebsd or TrustedBSD...
(so many projects, so little time...)
---
Garance Alistair Drosehn = [EMAIL PROTECTED]
Senior Systems Programmer or [EMAIL PROTECTED]
Rensselaer Polytechnic Institute
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: getdirentries() and /proc
The man page for getdirentries() says: int getdirentries(int fd, char *buf, int nbytes, long *basep) "The nbytes argument must be greater than or equal to the block size associated with the file, see stat(2). Some filesys- tems may not support these functions with buffers smaller than this size." So ... what are we supposed to use for this? For special filesystems like /proc, is any old value that is sufficiently large enough to hold a few struct dirent's considered to be OK? Should I not use 'getdirentries()', and opt instead for 'opendir()' and 'readdir()'? Any advice is appreciated. I also had this problem (when I created a readdir equivalent for a port of a non-libc using compiler). I checked libc, and libc always seems to use 1024 bytes (constant called DIRBLKSIZ) for nbytes. But I didn't try to search /proc yet. Also keep in mind that using getdirentries you could get duplicate entries (libc readdir sorts and removes duplicates first). I however don't know if this is just because of hardlinks (which most people don't use afaik) or also for regular filehandling. Marco van de Voort ([EMAIL PROTECTED] or [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: file creation times ?
That's not justification for putting a creation time into the UFS. Different filesystems store different information - depending on what the FS developers saw as important. You could just as easily point out the deficiencies of NTFS based on it's inability to support all the metadata in NFS. I know very little of filesystems, but I know that NTFS is extensible (and supports several file strains). So probably that is not a limitation of NTFS, but of the NT implementation of it. E.g. Mac stuff is stored in an extra strain, extra attributes can be stored in the MFS etc etc. One could write a *nix NTFS driver that supported NFS metadata. Marco van de Voort ([EMAIL PROTECTED] or [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Linux Module problems
On my -CURRENT machine, FreeBSD jehovah 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat May 13 15:11:13 EDT 2000 root@jehovah:/usr/src/sys/compile/JEHOVAH i386 (obviously a little out-dated), I have recently noticed unusual problems with the linux module which, by the way, is of the same date. The first problem I discovered first came up while building the StarOffice5 port. After checking the dependency for linux's libc5, it _spontaneously_ reboots. No panic(), hence no debugger. I've never seen this sort of behavior before and have no idea what could have caused it. However, I noticed a related incident, which I can reproduce. What I did was, for kicks, kldunload linux, and then make install the staroffice5 port, and this time, I got a page fault and panic() from within malloc, which was trying to move something located at an address on an unmapped page to a register. I can reproduce this easily at the moment, with the following: #!/bin/sh while true; do kldload linux; kldunload linux; done A quick kldunload linux followed by a quick kldload linux does it on the first iteration. What's more odd is that now, after panic()ing the machine a couple of times with the above, I can reproduce the spontaneous reboot easily too, by just starting up linux Netscape! At the moment, I cvsup-ed new sources, and am rebuilding world and a fresh new kernel, at which point I'll try to reproduce this again. I remember seeing this in earlier -CURRENT, too, just never got around to playing with it. Anyone? -- Bosko Milekic * pages.infinit.net/bmilekic/index.html * www.technokratis.com [EMAIL PROTECTED] * [EMAIL PROTECTED] * [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux Module problems
Bosko Milekic [EMAIL PROTECTED] écrivait (wrote) : What's more odd is that now, after panic()ing the machine a couple of times with the above, I can reproduce the spontaneous reboot easily too, by just starting up linux Netscape! I had the same problem with all statically linked Linux binaries, including rpm. I guess that loader does not recognize as Linux, launch them as FreeBSD static and one of the syscall is mapped to halt() (for example if dont launch rpm as root, i have "Segmentation violation" instead of a reboot). As explained in /usr/src/UPDATING, you have to rebrand them: brandelf -t Linux static-binary The first candidate (and i think this explain you problem) if of course /compat/linux/sbin/ldconfig. -- Alain Thivillon -+- [EMAIL PROTECTED] -+- Hervé Schauer Consultants To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Kernel threads (RE: alphaworks 1.3 linux port)
(I CC:'d to -hackers, perhaps someone can enlighten us wrt. the availability of kernel threads..) On Fri, 26 May 2000, Koster, K.J. wrote: Has anyone had a look at this? Reports are that it's a big improvement over the BDown stuff. Anyone had a play yet? 1.3 is a big improvement over 1.2.2 performancewise, at least on Windows. it works great under linux (redhat 6.1) but i wasn't able to get it to run under linux emulation of freebsd 4.0. if anyone figures it out, i'd love to hear how they did it. Could you elaborate on your attempts to get it running? Any error messages or irregular behaviour? What version of the linux port were you using? As I wrote about two weeks ago, I tried to get it running on relatively up-to-date 5.0-CURRENT. Alphaworks JVM uses native threads on Linux, which (as far as I understand) are impossible to have right now, either under Linux emulation or otherwise. The error message was: sigaltstack: Cannot allocate memory, which after looking up in the manpage led me to believe that perhaps Linux doesn't add MINSIGSTKSZ by default to the stack size. Added it to linuxulator in appropriate places (in linux_signal.c:linux_sigaltstack()), and it stopped complaining, but started eating 100% CPU. At which point I gave up... Obviously, the matter is more complicated than that - that is, it was shooting in the dark. I know I don't have kernel threads, I was just curious where it would bomb out.. :-) Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux Module problems
On Fri, 26 May 2000, Alain Thivillon wrote: I had the same problem with all statically linked Linux binaries, including rpm. I guess that loader does not recognize as Linux, launch them as FreeBSD static and one of the syscall is mapped to halt() (for example if dont launch rpm as root, i have "Segmentation violation" instead of a reboot). I just re-cvsuped and rebuilt everything, and I am still having the same problem. In fact, I've noticed something else: After the reboot, the _time_ (not the date, though) is modified to, generally +4 hours. I have no idea why this would be happening. As explained in /usr/src/UPDATING, you have to rebrand them: brandelf -t Linux static-binary The first candidate (and i think this explain you problem) if of course /compat/linux/sbin/ldconfig. Am giving it a shot. -- Alain Thivillon -+- [EMAIL PROTECTED] -+- Hervé Schauer Consultants -- Bosko Milekic * pages.infinit.net/bmilekic/index.html * www.technokratis.com [EMAIL PROTECTED] * [EMAIL PROTECTED] * [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux Module problems
As explained in /usr/src/UPDATING, you have to rebrand them: brandelf -t Linux static-binary The first candidate (and i think this explain you problem) if of course /compat/linux/sbin/ldconfig. Am giving it a shot. This worked. Thanks! -- Bosko Milekic * pages.infinit.net/bmilekic/index.html * www.technokratis.com [EMAIL PROTECTED] * [EMAIL PROTECTED] * [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: truss(1) with support for fork(2) and friends
Arun Sharma scribbled this message on May 20: I just implemented the "-f" flag in truss, to trace across fork(2), rfork(2) and vfork(2) (the last one is not tested). [...] I'm guilty of running indent against the source, before I did this work. So I can't generate a clean patch yet. But if I get good feedback on this work, I'll clean it up and produce a patch that can be commited. well, has another committer expressed intrest in this work? I was looking at committing your code, but it's both for an out of date version of truss, and run though ident... if you could provide the changes to the -current source (w/o ident) I'd greatly appreciate it.. -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking"I say all sorts of useless things." -- cmc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: file creation times ?
[.] I check it in FreeBSD 4.0-R open do not change atime. Indeed, but it sets a bunch of flags that can be referred to later by the driver. This would be a good flag - perhaps limited in the same way that touching the file is (owner only). [.] -- @BABOLO http://links.ru/ -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: truss(1) with support for fork(2) and friends
On Fri, May 26, 2000 at 01:51:48PM -0700, John-Mark Gurney wrote: well, has another committer expressed intrest in this work? I was looking at committing your code, but it's both for an out of date version of truss, and run though ident... if you could provide the changes to the -current source (w/o ident) I'd greatly appreciate it.. Sean Eric Fagan did. But he'd like me to go - "single truss many processes with select" way. I'm not sure if I have the time to implement that - but yes, I'll work on coming up with a clean patch against -current. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux emu question
I noticed some people talking about the linux emulation and how good/bad it can be and I just wondered, does anybody here have any experiences with the vmware for linux software? I have been thinking of buying this, for those one or two windows programs that I need to use now and then. To add to the other responses I run OpenBSD-current under VMware2 (on my FreeBSD-current laptop) and also run NT4 when I need to read lotus scrotes mail at work. It's very stable (bar the recent module changes which are probably now fixed with the latest vmware2/Makefile update). Mark Knight (cc'd) runs FreeBSD-current in a vmware2 box under NT very successfully up until about a week ago (he's having some nasty panics with currents built within the last week). Julian Elischer runs FreeBSD-current under vmware? on a FreeBSD-current box with no complaints afaik. Just wondering, It's worth the $99 in my book ! James. --- ICQ #19675056 Public key available at: http://www.dreamscape.com/halstead/jh.asc --- -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
