I can remember that somebody already reports somewhere, but this
bug(?) is still standing there, so here's again:
I failed to install recent 5-current (5.2-BETA as of Nov/29/2003) to VMware
Workstation 4.x (tested with 4.0.5 and 4.1 beta). I've observed that:
* It seems that FreeBSD
I'd like to try to bulid FreeBSD/sparc64 on i386 box, but due to the
lack of bsdlabel(8)'s '-m' option (set machine archtecture) on
sunlabel(8), newfs(8) cannot work.
Question: Anybody working on teaching '-m' option to sunlabel(8)?
-- -
Makoto `MAR' Matsushita
Self followup...
matusita I'd like to try to bulid FreeBSD/sparc64 on i386 box, but
matusita due to the lack of bsdlabel(8)'s '-m' option (set machine
matusita archtecture) on sunlabel(8), newfs(8) cannot work.
I'm confused something. The fact that newfs(8) on i386 cannot newfs a
filesystem
brooks I don't think you can because our UFS on disk format is byte
brooks order dependent. Someone probalby needs to import the NetBSD
brooks endien-independence stuff.
My friends told me that I can do with a help of geom_sunlabel, and
it's right.
-- -
Makoto `MAR' Matsushita
toha Release build fails:
toha drivers.flp: file system if full.
Since yesterday.
toha Can somebody remove some driver from drivers.conf?
No, don't do that. Since we have only 3 floppies, simply removing
some modules may mean it cannot use it while installing FreeBSD.
Fortunately we
asmodai You cannot set the root password as passwd dumps core on a signal 12.
% pwd
/usr/src
% echo **/*(.)|xargs grep 'You cannot set the root password'
%
It should not be an message of passwd(1) or other sources, so it would
be hard to reproduce (if we can) what you've seen.
What you've
jmallett Anyone with insight into this?
Me Too with zsh 4.0.6 on 5-current as of early June/2003.
-- -
Makoto `MAR' Matsushita
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
It seems that kern.flp for FreeBSD/alpha is flooded (tested on FreeBSD/i386).
Maybe several kbytes should be removed from the kernel:
% du -s image.kern
1420image.kern
% ls -lR image.kern
total 1209
drwxr-xr-x 2 root wheel 512 Mar 28 00:57 boot
-r-xr-xr-x 1 root wheel 1223388 Mar
drosih GENERIC +VMWARE-friendly settings
It'll be unneeded for further VMware releases. At least, very recent
5-current runs quite fine on my VMware 4 beta.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the
kuku Can this be switched off with a single switch in the Makefile?
No, or you misunderstand what FreeBSD-current is.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
keramida Just in case anyone tries to build today's current and sees
keramida it fail because of boot2, you can always set BOOT2_UFS=UFS1_ONLY
keramida or BOOT2_UFS=UFS2_ONLY in your make.conf and rebuild.
It should work, but it can't be used for a release distribution:)
-- -
Makoto `MAR'
riccardo Is this stuff really needed on a boot floppy? Maybe we can leave
riccardo only I486_CPU? What about removing also device eisa and/or bpf?
riccardo (I'm just curious, don't expect to be an expert :-)
The bpf is required for DHCP client. We cannot remove it, or cannot
network install
ticso What about some uncommon ISA scsi controllers like stg and ncv?
ticso Both are available as a module.
Maybe it's ok, do you know whether stg/ncv kernel modules work as they
should be?
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
We (at least, I) don't know exactly that which options and/or drivers
can be picked out from the kernel for kern.flp... maybe it's chance to
find out all of them.
jhay What about moving the slip driver (sl) to the drivers floppy? I know its
jhay not much, but it is enough to make things fit on
Maybe it's ok, do you know whether stg/ncv kernel modules work as they
should be?
ticso No - I just can say that they got build on my system.
ticso I can't test either, because I don't have such cards.
Ah, ok, thank you. Anybody in this list knows?
-- -
Makoto `MAR' Matsushita
To
phk Not yet. I think adding a -m architecture flag to disklabel is the
phk way around this problem, but have not had time to do so.
Thanks, I'm waiting until you have enough time to do since I have
little knowledge about this issue:)
BTW, what's changes do you imagine? Make a table which
It seems that our kenrel for kern.flp does not fit again :-(
(Quote from make release logfile)
+ mdconfig -a -t vnode -f /R/stage/floppies/kern.flp
+ MDDEVICE=md1
+ [ ! -c /dev/md1 ]
+ disklabel -w -B -b /R/stage/trees/base/boot/boot md1 fd1440
+ newfs -i 8 -o space -m 0 /dev/md1c
fstab:
Ouch..
matusita % gzip loader
I've forgotten that this loader is already kgzip(8)ed, ignore me. Sorry.
Ok, we have to shrink at least 7kbytes of kernel on kern.flp.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of
Sorry for spamming again.
matusita Ok, we have to shrink at least 7kbytes of kernel on kern.flp.
If you are serious about this, attached below is a current kernel
configuration file for kern.flp kernel named BOOTMFS (attention: it is
only just for boot floppy, not GENERIC nor default installed
I've tried to do make release of FreeBSD/alpha on FreeBSD/i386 box
last night, and found that follow error while generating drivers.flp:
+ export BLOCKSIZE=512
+ [ /R/stage/floppies/drivers.flp = -s ]
+ do_size=
+ FSIMG=/R/stage/floppies/drivers.flp
+ shift
+ RD=/R/stage
+ shift
+ MNT=/mnt
+
I'd like to commit following patch to src/release/Makefile. Here's
background:
A user may want to build their own FreeBSD distribution. During the
release build, pkg_add(1) runs within chroot sandbox to install
mkisofs(8) iff MAKE_ISOS=YES. Imagine what's happen if the user is
living behind
scrappy I found the release man page this evening, after more searching, and
scrappy understand from it that a simple:
From release(7):
floppies Generate a new set of boot floppies. This will call the
release.5, release.9, and release.10 targets to re-generate
jwdThe iso(s) boot correctly and sysinstall works fine. The disks
jwd are formated and newfs'd correctly. However, when sysinstall
jwd tries to mount the cdrom, the following error is received:
jwd Error mounting /dev/acd0c on /dist: Operation not supported by device (19).
Which type of
jwd A new 5.0-20021025-CURRENT snapshot is available
jwd via anonymous ftp at usw2.freebsd.org:
Wonderful! Is it a time to switch back 'current.FreeBSD.org' name to
that machine?
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in
attila only problem with snapshot.jp at this point is that
attila release does not build: md0 problems
That should be a local problem IMO, and I believe it was fixed several
hours before (ya, sorry for being lazy.)
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL
jroberson I suspect that there is some other bug then. 1/2 of your
jroberson memory should not be consumed by kernel malloc. Do you
jroberson have an abnormally large MD or something?
MD devices are used to create installation floppies but no, it should
be 1.44MB/2.88MB size, relatively small
tlambert2 The worst case failure with my Ugly patch should be that
tlambert2 things hang, and quit running completey.
I've emailed to the list that I've tried your patch but it cannot boot
(actually it boots, but panics immediately.) Maybe I'm using
different time of source code. Which
carl I fail to see how a reduction of hours (even just one) is
carl insignificant to someone on a dial-up connection. Time is money
carl for some people; even a meager three hours.
Don't you think 30+ hours of time to fetch an ISO image is _not_
wasting of money?
carl Again, I fail to see how
After upgrading my 5-current box (as of late September 2002), the
kernel panics periodically with following message:
panic: kmem_malloc(4096): kmem_map too small: 107651072 total allocated
The number '4096' and '107651072' is always the same. What am I
missing something?
-- -
Makoto
I'm now trying Terry's patch (just rebuilding a kernel).
jroberson You are using 100mb of KVA for malloc(9)? Are you certain
jroberson that you don't have a memory leak?
Maybe there's a chance of a memory leakage by GLOBAL, but I don't sure.
jroberson How much memory is in this machine?
tlambert2 This was recently discussed on -current. I posted a dumb
tlambert2 patch that fixes the problem.
(stuff deleted)
tlambert2 See the archive of the posting, for more details:
Thank you, I'll try it right now.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
matusita Thank you, I'll try it right now.
Unfortunately, kernel panics soon after it wakes up... maybe I've
still missed something.
-- -
Makoto `MAR' Matsushita
Booting [/boot/kernel/kernel]...
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989,
tlambert2 That's 3.4 hours saved on a 28.8K modem download time,
tlambert2 overall... a 14% reduction in size.
The percentage doesn't matter. If ISO image is compressed, user who
downloads the image may de-compress that image to burn (I don't know
any about the burner softwares which support
tlambert2 fetch -o - URL | gunzip unzipped_image
You fully forgot that all users use FreeBSD.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
carl 3.4 hours is a lot of time on a dial-up connection (granted it
carl is not a one size fits all period of time).
You forget that you still compressed image with about 30 hours (at
least, full 1 day or more), and it is not helpful for ordinal users,
not you.
Again, reducing
attila If it reaches this far, both the 'livetree' and 'obj'
attila trees would be available.
Good idea, I'll try it later.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
culverk This seems a lot like personal preferance to me, I for one
culverk don't like a lot of tty's, because running getty on a bunch
culverk of ttys that I'm not going to use is a waste of ram
Seconded. Two ttys are enough for me. Many getty(8) processes usually
waste our process table
kuku So there is no more /kernel file?
Yes.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
elitetek boot -c on DP1, and the latest snapshots doesnt seem to do
elitetek anything, I have been unable to find any info regarding a
elitetek change to the command or what other switches it supports.
Userconfig was gone away in 5-current. Tweak /boot/device.hints
instead, or set appropriate
jhay md5 died on zero length files. You will have to upgrade the machine or
jhay at least do a buildworld with new source before you try a release again.
Ya, that's exactly the problem on my buildbox... Thank you for the info.
But if new md5(1) doesn't used by during a release, it's yet
mb The situation is very unpleasant.
IIRC, we have no active GCC maintainer, no matter you feel unpleasant or not...
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
ru This was broken again. I don't have any ideas of what to move
ru out.
There are some ideas to do around boot floppies in my mind:
1) More drivers to move kernel modules, including other network
drivers, pccard and friends, filesystems, etc. Apparantly it
reduces kernel size so
jhay nfsclient.ko and msdosfs.ko exists nowadays, so in theory it can
jhay reside somewhere else.
It seems that it's time to make the 3rd floppy for kernel modules...
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of
brooks It does work though.
It should work, but I wonder if 5-current kernel can mount CD-ROM as
the root filesystem. I've tried before (March/2002 or something), but
it doesn't work, kernel refused to mount CD-ROM (see email archive for
more detail). Sorry if it was already fixed.
-- -
chuckr Ohhhkay. The .jp site I found stopped making snaps on 6/21.
Mainly because kern.flp was flood. Any tiny breakages refuse to make
a distribution.
chuckr Manfred Antar told me about ftp.kddlabs.co.jp, which is the
chuckr good site.
It mirrors snapshots.jp.FreeBSD.org daily, if my log
mark /usr/sbin/sysinstall * - fix - *
What should we do about sysinstall and perl5 package? Options for the
solution may include:
1) Install perl5 package also if 'base' distribution is selected.
pros: Nobody forget to install perl5 package. /usr/bin/perl
should
gmh003532 the fix is (yet again) to rebuild sed.
Is this mean that src/usr.bin/sed should be a build-tool?
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
gshapiro One more change please. Change:
I'm very glad to hear a comment from sendmail maintainer, thank you.
Just committed.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Here is a patch to enable sysinstall to set 'sendmail_enable' value to
'YES', 'NO', and 'NONE'. Current sysinstall can't set this value to
'NONE'; users who do *not* want to use sendmail can't stop sendmail
via sysinstall.
Following patch creates submenu to change the sendmail_enable value.
bmah Comments on the text only (i.e. I haven't tested the new menus)...
Thank you.
I've (of course) tested; making floppies and do a test that sysinstall
saves sendmail_enable line to /etc/rc.conf.
-- -
Makoto `MAR' Matsushita
Index: menus.c
wizard I've got error :
wizard /bin/sh:Argument list too long,
wizard while making buildworld,
IIRC, it is already fixed; re-cvsup again.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
ken It worked fine, up until the commit to kmod.mk.
That's by chance.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
ken Sorry, it was this commit that broke building -current kernels on -stable:
How do you build -current kernel on your -stable box?
cd /usr
cvs -d /your/CVSROOT checkout src
cd src
make buildworld
make buildkernel
should work as it should be (and it's
cjc However, I have (and think I posted somewhere?) some kludgey
cjc patches that build kldxref(8) as a cross-tool so that it works
cjc for 4.5 to 5.0 upgrades. But it's not really the right fix
cjc (since it is not a true cross-tool), so I haven't committed it.
Can we add kldxref(8) to
Following are observed with 5-current kernel as of Apr/25/2002.
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x6
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01898d1
stack pointer = 0x10:0xc9476b24
frame
matusita I must provide more detailed information, but here's quick report.
Using trace command, this panic is caused by:
usbd_open_pipe_ival(c40416e0, 1, c8148858, ) at
usbd_open_pipe_ival+0x1d
usbd_open_pipe(c40416e0, 81, 1, c8148858, c40769c0, c8148880, 2, 1,
ru This is just a heads up for anyone interested that I have just
ru started working on a cross-platform make release issue so that
ru make release TARGET_ARCH=alpha on an i386 box would produce a
ru working Alpha release.
Wonderful! If there are any tasks I can help for you, feel free to
sgk Note the Error code 1(ignored).
That's right, it's not an actual *error*.
However, we have seen such a report so many, many times. We may want
to consider changing src/sys/conf/kmod.mk to shut it up.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
ru A fast -CURRENT box with root access for make release would be
ru highly appreciated. My 500MHz Celeron is too slow for this.
snapshots.jp.FreeBSD.org and associate build machines are all
P3-500Mhz, not so fast like Celeron 500Mhz...
ru There are no syscall issues in my version because I
Using 5-current code as of Apr/17/2002 15:00:00 GMT:
# pwd
/usr/src/gnu/usr.bin/groff/src/preproc/eqn
# ident Makefile
Makefile:
$FreeBSD: src/gnu/usr.bin/groff/src/preproc/eqn/Makefile,v 1.3
2002/04/11 11:06:03 ru Exp $
# make -n neqn
make: don't know how to make neqn. Stop
#
dwcjr Yeah, your make is broken, try rebuilding make by itself and
dwcjr install it then try the buildworld again
Ah, sorry. I've missed what src/usr.bin/make/str.c rev 1.19 said. I
just rebuilt make(1) and confirmed that it works again. Thanks.
-- -
Makoto `MAR' Matsushita
To Unsubscribe:
jhb Can you get a backtrace in ddb? It looks like a null pointer
jhb dereference, and knowing where it happened would help.
Backtrace told me that the panic was occured when
usbd_get_interface_descriptor() is called from aue_attach().
jhb Finding the file and line of the instruction pointer
Following are observed with 5-current kernel as of Apr/13/2002.
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x4
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0189b4a
stack pointer = 0x10:0xc03f5180
frame
'BTX halted' on floppy boot is still a problem on 5-current. Nobody
can install latest 5-current (not 5.0-DP1 :-) to a fresh PC at this time.
debolaz Well, here's a dump from me too, it's
debolaz 5.0-CURRENT-20020313-JPSNAP, the first snap from
debolaz snapshots.jp.freebsd.org which has the
matusita I doubt there is a problem around libz (which is updated
matusita between two JPSNAPs shown above), since the kernel in
matusita kern.flp is gzipped, but most users doesn't gzip their
matusita kernel on HDD.
Yeah, bingo! :-)
My friend on IRC confirms that 'gzip'-ed kernel on HDD
matusita Anybody know typical pitfalls of using new libz? I've seen some
matusita commits for adapting the new libz, but sorry I forget what they were.
I've tried to boot 5.0-CURRENT-20020404-JPSNAP and got a success @_@
Does recent change to src/lib/libz/infcodes.c rev 1.4 solve this issue?
wosch there are no up to date current snapshots available.
Yes, current 5-current's fixit.flp is flooded. I have an idea how to
fix it (see current@), but sorry I have no time to check that my idea
is good or bad...
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
jhay I'm building the fixit floppy without a populated /dev. That leaves
jhay enough space open to fit all the rest of the stuff and it shouldn't
jhay be needed on -current because of devfs. But I haven't tried it. :-)
That is all I want to check it ASAP :-)
-- -
Makoto `MAR' Matsushita
To
matusita But I don't checked that we can safely remove /dev/* files from
matusita fixit.flp (sorry, if no one try to do, I'll do it later).
I've confirmed that it makes no problem, so commit it. We get about
40kbytes of free fixit.flp space again.
-- -
Makoto `MAR' Matsushita
To Unsubscribe:
never Maybe it's better to make two different ports vmware-tools and
never vmware-tools3, first of which is for vmware2?
Ancient ports/emulators/vmware-tools (FreeBSD native vmware-tools for
VMware _1.x_) is outdated for VMware 2.x; it doesn't have time sync
feature.
If you're VMware 2.x user,
rwatson It seems to me the kernel entry point should be mi_start()
rwatson rather than main(), however.
Good point. I just did a small hack to do that:
URL:http://snapshots.jp.freebsd.org/tour/current/kernel/
4-stable kernel tour will be changed also tomorrow.
-- -
Makoto `MAR' Matsushita
rwatson Certainly we can MFC eaccess(), but that's not going to make
rwatson the problem go away. Fundamentally our model is backward
rwatson compatibility, not forward compatibility. We need to build
rwatson 5.0 packages on 5.0.
That's why I build FreeBSD 5-current snapshots on a 5-current
jstocker kldxref /boot/kernel
jstocker kldxref:No such file or directory
jstocker *** Error code 1 (ignored)
See the message (ignored). It is the intentional behavior.
If you don't like this, make NO_XREF=YES installkernel will help you.
Check src/sys/conf/kmod.mk for more details.
-- -
julian It might be an idea if the kernel were kept separate because I
julian find that the cross-reference is good but having kernel and
julian userspace mixed up is a bit confusing..
Ok, I've separated the tour into 'kernel' part and 'userland' part
(5-current kernel is now processing).
Tour
gnn They're needed for the tags: target in the kernel makefiles and
gnn since I'd like to be able to browse code...
Feel free to check URL:http://snapshots.jp.FreeBSD.org/tour/. Both
5-current and 4-stable code are HTMLed with GLOBAL daily.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send
julian It might be an idea if the kernel were kept separate because
julian I find that the cross-reference is good but having kernel and userspace
julian mixed up is a bit confusing..
Hmm, maybe it's a good idea about userland/kernel separation. I'll
try it later (maybe this evening or this
murray I'm currently looking into #2 and #3, as well as working with Ted
murray Lemon from the ISC to fix some symbol pollution that this whole mess
murray has exposed. Any other ideas?
Currently nothing, it seems that #3 (or its variant) is better IMHO.
-- -
Makoto `MAR' Matsushita
To
Current 5-current fails 'make release' when processing release.4
target (making a crunch binary). Here's sample session:
=== doc
rm -f cpio.info cpio.info.gz
rm -f .depend /usr/obj/usr/src/gnu/usr.bin/cpio/GPATH
/usr/obj/usr/src/gnu/usr.bin/cpio/GRTAGS
Ouch.
matusita src/sbin/dhclient/Makefile doesn't know 'dhclient_clean' target.
Of course that's normal, dhclient_clean target should be created by crunchgen.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the
null After the cvs checkout completes:
Ah, big sorry... I just fixed in src/release/Makefile rev 1.658.
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
will Jordan announced recently that Qwest is upgrading the hardware
will and that there would be intermittent problems with the server for
will a certain period (a few days as I recall).
It would be:
From: Jordan Hubbard [EMAIL PROTECTED]
Subject: stable.freebsd.org AKA releng4.freebsd.org
I know this is probably offtopic but is there any problem with
current.freebsd.org at the moment?
Hmm...
galtvalion % ftp current.freebsd.org
Connected to usw2.freebsd.org.
220 usw2.freebsd.org FTP server (Version 6.00LS) ready.
Name (current.freebsd.org:matusita): ftp
331 Guest login ok,
I know this is probably offtopic but is there any problem with
current.freebsd.org at the moment?
Hmm...
galtvalion % ftp current.freebsd.org
Connected to usw2.freebsd.org.
220 usw2.freebsd.org FTP server (Version 6.00LS) ready.
Name (current.freebsd.org:matusita): ftp
331 Guest login ok,
will Jordan announced recently that Qwest is upgrading the hardware
will and that there would be intermittent problems with the server for
will a certain period (a few days as I recall).
It would be:
From: Jordan Hubbard [EMAIL PROTECTED]
Subject: stable.freebsd.org AKA releng4.freebsd.org
ggombert VMware tools for FreeBSD is woefully out of date as well,
Really?
% cd /usr/ports/emulators/vmware-tools
% make -V PORTVERSION
3.0.0.1455
VMware 3.0 bundles a new VMware tools, and it is up-to-date version as
of Linux guests.
% cd /usr/ports/emulators/vmware-tools
% make -V
matusita I've just filed an incident (I have a license of VMware 3.0).
I've received a reply from VMware:
Thank you for submitting the incident and letting us know the
potential workaround.
I must apologize because we do not support FreeBSD 5.0 as a guest OS
yet in Workstation 3.0.
rwatson If someone has a commercial license, it would make sense
rwatson submitting this via a trouble ticket, as well as providing
rwatson the VMware support people with some brief directions on
rwatson installing 5.0.
I've just filed an incident (I have a license of VMware 3.0).
-- -
Makoto
I found that acd, ATAPI CD device, doesn't listed up to 'kern.disks'
kernel MIB which should list all disks in the running system.
Here is a sample:
ringo % sysctl kern.disks
kern.disks: ad0
ringo % grep acd /var/run/dmesg.boot
acd0: CDROM TOSHIBA CD-ROM XM-6202B at ata1-master PIO4
ringo %
FYI: pam_setcred() call seems used in OpenSSH, ftpd, rshd, login, and su
already included in FreeBSD source code.
URL:http://snapshots.jp.freebsd.org/tour/current/cgi-bin/global.cgi?pattern=pam_setcredid=type=reference
imp OK. This looks like a problem in 1.6.4p1 of sudo. It isn't a problem
jhay The last one that worked here was on 20020108. The one on the
jhay next day broke. The release builds are started from cron at
jhay midnight SAST which is 2 hours ahead of UTC.
FYI: 5.0-CURRENT-20020113-JPSNAP builds goes fine here. I dunno what
change fixes this :-)
-- -
Makoto `MAR'
This error is occured when make release try to roll 'bin' distribution.
jhay Make release of -current has been broken here for the past few
jhay days. I had a look on the Japanese snapshot site and theirs
jhay break with the same error. Do anybody have an idea about what
jhay is going wrong?
coolvibe What header file defines SWI_NOSWITCH?
http://snapshots.jp.freebsd.org/tour/current/cgi-bin/global.cgi?pattern=SWI_NOSWITCHid=type=symbol
SWI_NOSWITCH are used and/or defined by these files. You can easily
find that this list have only one *.h file -- sys/sys/interrupt.h.
% grep
With 5-current as of Dec/04/2001 15:00:00 GMT.
It seems that this is because 'WARNS=0' line is inside of
!defined(RELEASE_CRUNCH) clause. IMO, if an application's code
requires to set 'WARNS=0 for build, it should also be set when
building as a part of a crunched binary.
-- -
Makoto `MAR'
With the 5-current source as of Dec/02/2001 15:00 GMT.
-- -
Makoto `MAR' Matsushita
(cd /usr/src/usr.bin/telnet make -DRELEASE_CRUNCH depend make -DRELEASE_CRUNCH
commands.o main.o network.o ring.o sys_bsd.o telnet.o terminal.o utilities.o genget.o
getent.o misc.o)
rm -f .depend
mkdep
Sorry for late reply.
jkh Don't you want to try the devfs mount and only copy device files
jkh if that returns an error code?
Hmm, it seems better to me. I'll try it again... I find that more
error handling is required if mounting devfs is failed.
-- -
Makoto `MAR' Matsushita
To
jkh Don't you want to try the devfs mount and only copy device files
jkh if that returns an error code?
How 'bout this patch (attached below)? I've recreate boot floppies
with this patch, then put them to:
http://people.FreeBSD.org/~matusita/5.0-CURRENT-20011121-JPSNAP_usedevfs/
-- -
Makoto
jkh Looks good to me, I'd say commit it!
Thanks! I'll commit it in this weekend.
BTW, how dou you think my other patch (use 'devfs' while mounting
filesystems, use fsck_ffs instead of fsck) for sysinstall, which was
posted about a week before to [EMAIL PROTECTED]? You can fetch from:
matusita OK, a patch is attached below.
Sorry, forget to add the patch... try again.
If anybody test with boot floppies, available at
http://people.FreeBSD.org/~matusita/5.0-CURRENT-20011121-JPSNAP_usedevfs/,
please let me know your results.
-- -
Makoto `MAR' Matsushita
Index: install.c
In /etc/rc, there is a swapfile feature, to configure a file to use
swap device. Here is a script for that.
# Add additional swapfile, if configured.
#
case ${swapfile} in
[Nn][Oo] | '')
;;
*)
if [ -w ${swapfile} -a -c /dev/mdctl ]; then
echo Adding ${swapfile}
matusita If it seems fine for me, I'll post a patch.
OK, a patch is attached below.
I've also made boot floppies (use 5-current code as of Nov/21/2001)
for anyone who try to find out that this problem is gone away.
1 - 100 of 202 matches
Mail list logo
