Re: TeXmacs port
On Fri, 7 Feb 2003, Giorgos Keramidas wrote: > On 2003-02-06 17:37, Michael Graffam <[EMAIL PROTECTED]> wrote: > > > > Who is maintaining the GNU TeXmacs port to FreeBSD? > > > > The port is somewhat out-of-date: 1.0.1 is the current stable release, > > the FreeBSD port is 1.0.0. > > You should first try contacting the existing port maintainer. Of course, thats why I asked :) > Looking > from the Makefile of /usr/ports/editors/texmacs, this would be: > > MAINTAINER= [EMAIL PROTECTED] Ahh.. thanks :) > You are always welcome to contact [EMAIL PROTECTED] or submit > patches that update the port. Courtesy requires though that before > making any widespread changes to the port, you should try to contact the > existing port maintainer. Indeed. At the very least I'd like to try to help out getting any required FreeBSD patches merged into TeXmacs properly. I don't mind if the TeXmacs port lags behind TeXmacs-stable, but I'd like to at least be able to compile the new development versions on my FreeBSD laptop like I do my Linux desktop. Thanks for the info.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
TeXmacs port
Who is maintaining the GNU TeXmacs port to FreeBSD? The port is somewhat out-of-date: 1.0.1 is the current stable release, the FreeBSD port is 1.0.0. I tried building TeXmacs from the source, but it has some problems. I'm going to work on it over the weekend and see if I can get it working. I'll be submitting any changes to Joris (the main TeXmacs developer) so future versions should be tip-top on FreeBSD right out of the tarball. I use TeXmacs quite a lot and have some 1.0.1 documents that I need to continue working on. I am active in the TeXmacs user community (I wrote the Octave <-> TeXmacs link and other sundries) and I always stay current on the stable releases, and usually try quite a few development snapshots too. So I am in an ideal position to maintain this port for FreeBSD since I need the latest releases anyhow for further Octave/TeXmacs development. That I'm in a position to help the FreeBSD project as well is a happy state of affairs, and I'd love to pounce on the opportunity. So, is there someone specific I should email about all this? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: PCMCIA NIC for use w/ FreeBSD?
On Thu, 6 Feb 2003, Greg 'groggy' Lehey wrote: > Hmm. This will be difficult. If you can at least install a minimum > system by some other means, it will make life easier. Not difficult at all! FreeBSD 4.7 worked like a champ. All I had to do was insert two floppies and smoke cigarettes :) Thanks for your help! The install is done, and I'm typing this to you on the fresh install on the first boot up. If you want some extended info on this NIC or anything to help with the 5.0 effort, just tell me what you need and I'll send it off to you. Thanks again. .. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: PCMCIA NIC for use w/ FreeBSD?
On Thu, 6 Feb 2003, Greg 'groggy' Lehey wrote: > You might possibly find 4.7 easier in this case. 5.0 has completely > rewritten PC Card drivers, and it may be more difficult to get it to > work there. Hmm, ok -- I'll try giving 4.7 a shot then. > No, you won't have /var/log/messages during installation. dmesg will > be available via the Alt-F4 shell. Do you need the card at install > time? It's easier to debug later. Unfortunately, yes .. I am hoping to do a network install. > Understood. We call them BSD, not *BSD. Ok, understood. Apologies, all :) > OK, this is looking like an identification problem. I suspect we can > fix it if you install 4.7. I'm downloading now. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: PCMCIA NIC for use w/ FreeBSD?
On Thu, 6 Feb 2003, Greg 'groggy' Lehey wrote:
> Hmm, this could be a simple problem to solve. What version of FreeBSD
> are you using?
None yet :(
I'm trying to install 5.0 -- but I'd settle for 4.x
> What appears in dmesg and /var/log/messages?
I don't think these are around in install floppy image, but I'll make up
a new floppy set and see.
> > I suspect that *BSD would work if it correctly identified the card as NE2K
> > compatible and just tried to do it.
>
> We call it FreeBSD or BSD, not *BSD.
Well, I meant the entire BSD family {Net,Open,Free}BSD -- none of them
actually work; though all notice the card is there, they just don't know
what driver to use.
Granted, though -- I should have said "them" and not "it."
> > Any way I can force that?
>
> Depends on the version you're running. I suspect I know a way if
> you're running 4.x.
I'll try 4.x if it'll help.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
Re: PCMCIA NIC for use w/ FreeBSD?
On Thu, 6 Feb 2003, Greg 'groggy' Lehey wrote: > > I wish it were so. I have an NE2K compatible NIC > > Heh. I was going to suggest exactly that. :) Yeah, NE2K compatible NICs have always done right by me. But this one is pretty obscure: its an 'Argosy EN-210' NIC. > What problem do you have with (Free)BSD? Well, I boot the laptop and it lists off the devices in the PCMCIA slots; it correctly identifies a 16MB ATA flash disk, and a 3com PCMCIA nic that I lost the dongle to, along with a two different modems. So I'm sure the PCMCIA hardware is being used OK. It just doesn't configure the NE2K pc card -- doesn't assign an ethernet device to it, but it does so for the 3com. > > I guess I'll try a clearance Xircom I saw and cross my fingers. > > Don't do that until you know what the problem is. I suspect that *BSD would work if it correctly identified the card as NE2K compatible and just tried to do it. Any way I can force that? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: PCMCIA NIC for use w/ FreeBSD?
On Thu, 6 Feb 2003, Greg 'groggy' Lehey wrote: > On Wednesday, 5 February 2003 at 0:44:36 -0500, Michael Graffam wrote: > > I _REALLY_ want to get FreeBSD installed on my laptop, and I'm > > willing to bite the bullet and just buy a new NIC. > > Just about any 16 bit NIC will work. > > Greg I wish it were so. I have an NE2K compatible NIC that just doesn't work with *BSD, but it works ok with Linux. I guess I'll try a clearance Xircom I saw and cross my fingers. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
PCMCIA NIC for use w/ FreeBSD?
Can anyone suggest an inexpensive 16-bit PC card NIC (non-Cardbus) for use with FreeBSD, and where I might find one? I _REALLY_ want to get FreeBSD installed on my laptop, and I'm willing to bite the bullet and just buy a new NIC. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
FreeBSD, and PCMCIA NE2K NIC
Hello all, I am trying to do a net install of FreeBSD onto an old laptop (no cdrom). I have an NE2K compatible PCMCIA NIC which Linux can successfully use, but which no *BSD can. I figure the problem is essentially one of recognizing this particular card as NE2K compatible since other NE2K PCMCIA ethernet cards are supported. I was hoping to be able to cat some info out of Linux /proc to give enough information for the FreeBSD developers to recognize the card so that I can install FreeBSD in the future. So, here goes: `cardctl ident 1`: Socket 1: product info: "PCMCIA LAN", "Ethernet", "A", "004743118001" function: 6 (network) /proc/bus/pccard/01/exca: 82 7f 90 6b 00 08 41 02 00 03 1f 03 00 00 01 00 d0 00 d0 80 30 7f 01 00 d1 00 d1 00 2f 7f 80 f8 00 00 01 00 00 00 00 00 00 00 01 00 00 00 81 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
subscribe
subscribe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
