Support for USB devices out-of-the-box in -current?
Hello, By the time -current turns into -release later this year will FreeBSD have support in sysinstall and in the GENERIC kernel and have all the right settings so that systems which only have USB keyboards and USB mice can work out-of-the-box even during installation from the CDROM? I don't know if it is really considered an issue or not but an increasing number of systems ship with USB keyboards these days and it would be nice to be able to use it during sysinstall if no PS/2 keyboard is found. Thanks for any information about whether this will be a reality in 5.0-RELEASE. Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Binutils fixed in -current?
I read recently on this list that the problem with the -current binutils on Alphas had been fixed, did this also fix the problem on i386 which caused ports such as imlib, imlib2 and gnomelibs to behave weirdly as many of their binaries would segfault during configuring/linking/executing? I only ask because I would like to stop having to update my -current tree and then having to copy an old binutils over it so that things will work. Any information is appreciated. Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Support for atapi cdrw as scsi in -current?
Garrett Wollman wrote: On Sat, 02 Feb 2002 20:10:20 +, [EMAIL PROTECTED] said: I noticed a patch on freebsd-scsi a while back that added a not very complete form of atapi as scsi support to the freebsd kernel. Are there plans to complete this and add it to -current sometime before -current turns into 5.0-RELEASE? Thanks for any information. I've been using it somewhat actively in the past week or so in -current. The patch as it exists needs a few changes to fit in current -current. $ camcontrol devlist TDK CDRW241040B 57S4 at scbus0 target 0 lun 0 (cd0,pass0) LITEON CD-ROM LTN526D YSR5 at scbus0 target 1 lun 0 (cd1,pass1) I don't think that ATAPICAM works well enough to use it entirely in place of the atapi-cd driver; for example, I get the following errors: atapicam0: READ_DISK_INFO - ILLEGAL REQUEST asc=0x20 ascq=0x00 error=0x04 atapicam0: READ_TOC - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 However, it works well-enough to run cdrdao, which is what mattered to me, for both reading and writing on both of the afore-mentioned ATAPI devices. -GAWollman Is there a place where I can find this updated patch which will work for me in the current -current? Thanks. Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Problems setting up TCP/IP in 5.0-CURRENT...
me which option is causing this so that I may turn it back off. I would really like to try and get this working exactly as I have in Linux, Solaris, FreeBSD 4.5-RELEASE. Thanks for any help. Jordan Breeding To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Binutils fixed in -current?
I read recently on this list that the problem with the -current binutils on Alphas had been fixed, did this also fix the problem on i386 which caused ports such as imlib, imlib2 and gnomelibs to behave weirdly as many of their binaries would segfault during configuring/linking/executing? I only ask because I would like to stop having to update my -current tree and then having to copy an old binutils over it so that things will work. Any information is appreciated. Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Support for atapi cdrw as scsi in -current?
Garrett Wollman wrote: On Sat, 02 Feb 2002 20:10:20 +, [EMAIL PROTECTED] said: I noticed a patch on freebsd-scsi a while back that added a not very complete form of atapi as scsi support to the freebsd kernel. Are there plans to complete this and add it to -current sometime before -current turns into 5.0-RELEASE? Thanks for any information. I've been using it somewhat actively in the past week or so in -current. The patch as it exists needs a few changes to fit in current -current. $ camcontrol devlist TDK CDRW241040B 57S4 at scbus0 target 0 lun 0 (cd0,pass0) LITEON CD-ROM LTN526D YSR5 at scbus0 target 1 lun 0 (cd1,pass1) I don't think that ATAPICAM works well enough to use it entirely in place of the atapi-cd driver; for example, I get the following errors: atapicam0: READ_DISK_INFO - ILLEGAL REQUEST asc=0x20 ascq=0x00 error=0x04 atapicam0: READ_TOC - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 However, it works well-enough to run cdrdao, which is what mattered to me, for both reading and writing on both of the afore-mentioned ATAPI devices. -GAWollman Is there a place where I can find this updated patch which will work for me in the current -current? Thanks. Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Support for atapi cdrw as scsi in -current?
I noticed a patch on freebsd-scsi a while back that added a not very complete form of atapi as scsi support to the freebsd kernel. Are there plans to complete this and add it to -current sometime before -current turns into 5.0-RELEASE? Thanks for any information. Jordan Breeding To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Questions about -current
Hello, I just upgraded to -current today to get a couple of features including devfs working. In the process I have run into a few questions (mainly things to do with the fact that up until a few days ago I was only using linux 2.4.x): 1) Will either the in kernel or oss sound driver for an SBLive! in FreeBSD be updated to allow multiple accesses to /dev/dsp at the same time and time in the near future? I know that the oss driver have /dev/dsp1..7 or so but they still seem to not like having multiple accesses to any of them at the same time. In linux both the oss/free and alsa drivers fully supported playing multiple (I know I had tried up to six at a time before) streams to /dev/dsp concurrently. 2) Will frame buffers for eithe VESA or more specifically radeon be added and/or documented any time soon to use a frame buffer at a reasonable resolution for the virtual consoles? 3) Will USB keyboards work as the system console keyboard any time soon, right now I can't seem to get my Sun Type 6 USB keyboard to work even though it shows up in dmesg. 4) Is there anyone actively maintaining dri for XFree86 on FreeBSD, I couldn't get my Radeon 7500 to work with dri using a fresh pull of XFree86 CVS, so I ended up making a trivial patch to allow my Radeon to be detected and set up. But this led me to notice that there have been one or two performance and lock up related changes to the linux kernel dri code and wondered whether these fixes would ever make it to FreeBSD? 5) In -current would it be possible to have a few command line switches added to certain userland utilities? I noticed -h made it into `ls` now, but `cp` still doesn't have -a or -x which I used to use all the time in Linux. I know -a isn't a big deal but - x was definitely nice from time to time. `date` having a --date option to tell you when a specified date is in Linux is also very nice. Just some thoughts. 6) I have found the pages for hardware monitoring support in the FreeBSD kernel and have a few questions about it: Will the updated code which supports newer AMD and VIA monitoring chips be rolled into -current soon? And if so what userland utility does one use in FreeBSD to pull values from the driver like lm-sensors does for Linux? Thanks if anyone can help me figure out answers to any of the above questions or provide feedback on any of my comments. So far I love FreeBSD and find it much more efficient and intuitive than Linux, keep up the good work. Please Cc: me as I am not on this list yet. Jordan Breeding To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Questions about -current
Giorgos Keramidas wrote:
On 2002-01-21 09:22:08, [EMAIL PROTECTED] wrote:
5) In -current would it be possible to have a few command line
switches added to certain userland utilities? I noticed -h made it
into `ls` now, but `cp` still doesn't have -a or -x which I used to
use all the time in Linux. I know -a isn't a big deal but - x was
definitely nice from time to time.
What does the -a or -x option do for the ls(1) command of Linux?
Perhaps equivalent options do already exist in FreeBSD ls(1).
Sorry for the confusion there :-) The -a and -x options are meant
for cp(1). The -a (--archive) option in cp(1) for linux (which I am
fairly certain is the gnu version) is essentially an easy way to safely
do -dpR automatically. So effectively -a (--archive) preserves links,
tries to preserve permissions, and also does a recursive copy. The -x
(--one-file-system) option in cp(1) for linux says that if you have
multiple file systems mounted on top of / and you do a `cp -ax /
/mnt/copy/of/root/.` it should only copy the directory stubs for the
mounts instead of the mounts themselves. I have found both of these
options to be extremely useful at times.
`date` having a --date option to tell you when a specified date is
in Linux is also very nice. Just some thoughts.
If I haven't misunderstood you on this, FreeBSD's date(1) can already
do what you want, although I have to admit that it works a bit
differently than Linux's date(1).
I've recently used date(1) -j and -f options to convert arbitrary
dates to the local timezone in a script I wrote to print the
modification date of problem reports. You might want to check the
scripts at:
http://people.FreeBSD.org/~keramida/pr/feedback/
for samples of using date(1) to convert between timezones and date
representations. A small example that will probably help you
understand how this is done (combined with the description of the -j
and -f options in the date(1) manual page) is shown below:
hades!charon:[/home/charon]% date '+%s = %T %Z'
1011645430 = 22:37:10 EET
hades!charon:[/home/charon]% TZ=UTC date -j -f '%s' 1011645328 '+%s =
%T %Z'
1011645328 = 20:35:28 GMT
Again, sorry for the misunderstanding and not providing enough
information upfront. In linux date(1) is the gnu version of date, which
means you can do the following `date --date 'Jan 22 2002'` and it would
output the following:
Tue Jan 22 00:00:00 CST 2002
Or I could do a `date --date '2 days ago'` and it would output:
Sun Jan 20 00:46:30 CST 2002
Again, this option might not be the most useful thing in the world
but I know that I have used it many times at home and at work to make
scripts less complicated.
Cheers,
--
Giorgos Keramidas . . . . . . . . .
keramida@{ceid.upatras.gr,freebsd.org}
FreeBSD Documentation Project . . . http://www.freebsd.org/docproj/
FreeBSD: The power to serve . . . . http://www.freebsd.org/
Thank you for the response and let me know if you need any further
information to be able to tell what the options I was refering to for
cp(1) and date(1) actually do.
Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
