Re: PATCH: sysinstall to remove userconfig code
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 Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
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 `MAR' Matsushita
Index: install.c
===
RCS file: /pub/snapshots/cvsup/FreeBSD.cvs/src/usr.sbin/sysinstall/install.c,v
retrieving revision 1.309
diff -c -r1.309 install.c
*** install.c 20 Oct 2001 09:28:53 - 1.309
--- install.c 1 Dec 2001 13:49:27 -
***
*** 857,863
int
installFilesystems(dialogMenuItem *self)
{
! int i;
Disk *disk;
Chunk *c1, *c2, *rootdev, *swapdev, *usrdev, *vardev;
Device **devs;
--- 857,863
int
installFilesystems(dialogMenuItem *self)
{
! int i, mountfailed;
Disk *disk;
Chunk *c1, *c2, *rootdev, *swapdev, *usrdev, *vardev;
Device **devs;
***
*** 932,938
}
dialog_clear_norefresh();
msgNotify(Checking integrity of existing %s filesystem., dname);
! i = vsystem(fsck -y %s, dname);
if (i)
msgConfirm(Warning: fsck returned status of %d for %s.\n
This partition may be unsafe to use., i, dname);
--- 932,938
}
dialog_clear_norefresh();
msgNotify(Checking integrity of existing %s filesystem., dname);
! i = vsystem(fsck_ffs -y %s, dname);
if (i)
msgConfirm(Warning: fsck returned status of %d for %s.\n
This partition may be unsafe to use., i, dname);
***
*** 949,954
--- 949,969
msgConfirm(Unable to mount the root file system on %s! Giving up.,
dname);
return DITEM_FAILURE | DITEM_RESTORE;
}
+
+ /* Mount devfs for other partitions to mount */
+ Mkdir(/mnt/dev);
+ if (!Fake)
+ mountfailed = mount(devfs, /mnt/dev, 0, NULL);
+
+ if (mountfailed) {
+ dialog_clear_norefresh();
+ msgNotify(Copying initial device files..);
+ /* Copy the boot floppy's dev files */
+ if ((root-newfs || upgrade) vsystem(find -x /dev | cpio %s -pdum
+/mnt, cpioVerbosity())) {
+ msgConfirm(Couldn't clone the /dev files!);
+ return DITEM_FAILURE | DITEM_RESTORE;
+ }
+ }
}
/* Now buzz through the rest of the partitions and mount them too */
***
*** 962,974
msgConfirm(No chunk list found for %s!, disk-name);
return DITEM_FAILURE | DITEM_RESTORE;
}
! if (RunningAsInit root (root-newfs || upgrade)) {
! Mkdir(/mnt/dev);
! if (!Fake)
! MakeDevDisk(disk, /mnt/dev);
}
- else if (!RunningAsInit !Fake)
- MakeDevDisk(disk, /dev);
for (c1 = disk-chunks-part; c1; c1 = c1-next) {
if (c1-type == freebsd) {
--- 977,991
msgConfirm(No chunk list found for %s!, disk-name);
return DITEM_FAILURE | DITEM_RESTORE;
}
! if (mountfailed) {
! if (RunningAsInit root (root-newfs || upgrade)) {
! Mkdir(/mnt/dev);
! if (!Fake)
! MakeDevDisk(disk, /mnt/dev);
! }
! else if (!RunningAsInit !Fake)
! MakeDevDisk(disk, /dev);
}
for (c1 = disk-chunks-part; c1; c1 = c1-next) {
if (c1-type == freebsd) {
***
*** 983,989
if (tmp-newfs (!upgrade || !msgNoYes(You are upgrading -
are you SURE you want to newfs /dev/%s?, c2-name)))
command_shell_add(tmp-mountpoint, %s %s/dev/%s,
tmp-newfs_cmd, RunningAsInit ? /mnt : , c2-name);
else
! command_shell_add(tmp-mountpoint, fsck -y %s/dev/%s,
RunningAsInit ? /mnt : , c2-name);
if (tmp-soft)
command_shell_add(tmp-mountpoint, tunefs -n enable
%s/dev/%s, RunningAsInit ? /mnt : , c2-name);
command_func_add(tmp-mountpoint, Mount, c2-name);
--- 1000,1006
if (tmp-newfs (!upgrade || !msgNoYes(You are upgrading -
are you SURE you want to newfs /dev/%s?, c2-name)))
command_shell_add(tmp-mountpoint, %s %s/dev/%s,
tmp-newfs_cmd, RunningAsInit ? /mnt : , c2-name);
else
! command_shell_add(tmp-mountpoint, fsck_ffs -y
%s/dev/%s, RunningAsInit ? /mnt : , c2-name);
if (tmp-soft)
command_shell_add(tmp-mountpoint, tunefs -n enable
%s/dev/%s, RunningAsInit ? /mnt : , c2-name);
command_func_add(tmp-mountpoint,
Re: PATCH: sysinstall to remove userconfig code
Looks good to me, I'd say commit it!
- Jordan
dsyphers DEBUG: kget: error buffer sizing
matusita This is because sysinstall still want to get userconfig data
matusita and put the result to /boot/kernel.conf.
Userconfig was gone in 5-current, so we can safely remove kget() from
sysinstall. Attached below is a patch to do (kget.c should be remove
also).
Jordan (and others who may concern), would you please review my patch?
-- -
Makoto `MAR' Matsushita
Index: Makefile
===
RCS file: /home/ncvs/src/usr.sbin/sysinstall/Makefile,v
retrieving revision 1.117
diff -u -r1.117 Makefile
--- Makefile 2001/09/05 07:12:19 1.117
+++ Makefile 2001/11/13 18:12:37
@@ -2,7 +2,7 @@
PROG=sysinstall
MAN= sysinstall.8
-SRCS=anonFTP.c cdrom.c command.c config.c devices.c dhcp.c kget.c \
+SRCS=anonFTP.c cdrom.c command.c config.c devices.c dhcp.c \
disks.c dispatch.c dist.c dmenu.c doc.c dos.c floppy.c \
ftp.c globals.c http.c index.c install.c installUpgrade.c keymap.c \
label.c main.c makedevs.c media.c menus.c misc.c modules.c \
Index: install.c
===
RCS file: /home/ncvs/src/usr.sbin/sysinstall/install.c,v
retrieving revision 1.309
diff -u -r1.309 install.c
--- install.c 2001/10/20 09:28:53 1.309
+++ install.c 2001/11/13 18:12:37
@@ -755,14 +755,6 @@
/* All of this is done only as init, just to be safe */
if (RunningAsInit) {
#ifdef __i386__
-/* Snapshot any boot -c changes back to the new kernel */
- cp = variable_get(VAR_KGET);
- if (cp (*cp == 'Y' || *cp == 'y')) {
- if ((kstat = kget(/boot/kernel.conf)) != NULL) {
- msgConfirm(Unable to save boot -c changes to new kernel,\n
-please see the debug screen (ALT-F2) for details.)
;
- }
- }
if ((fp = fopen(/boot/loader.conf, a)) != NULL) {
if (!kstat || !OnVTY)
fprintf(fp, # -- sysinstall generated deltas -- #\n);
@@ -1054,7 +1046,6 @@
/* Set default startup options */
variable_set2(VAR_RELNAME, getRelname(), 0);
variable_set2(VAR_CPIO_VERBOSITY,high, 0);
-variable_set2(VAR_KGET, YES, 0);
variable_set2(VAR_TAPE_BLOCKSIZE,DEFAULT_TAPE_BLOCKSIZE,
0);
variable_set2(VAR_INSTALL_ROOT, /, 0);
variable_set2(VAR_INSTALL_CFG, install.cfg, 0);
Index: options.c
===
RCS file: /home/ncvs/src/usr.sbin/sysinstall/options.c,v
retrieving revision 1.76
diff -u -r1.76 options.c
--- options.c 2001/09/25 00:28:26 1.76
+++ options.c 2001/11/13 18:12:37
@@ -148,8 +148,6 @@
OPT_IS_VAR,NEWFS_PROMPT, VAR_NEWFS_ARGS, varChec
k },
{ Fixit Console, Which tty to use for the Fixit action.,
OPT_IS_FUNC, fixitTtyWhich, VAR_FIXIT_TTY, varChec
k },
-{ Config save, Whether or not to save installation kernel config chan
ges,
- OPT_IS_VAR,NULL, VAR_KGET, varChec
k },
{ Re-scan Devices, Re-run sysinstall's initial device probe,
OPT_IS_FUNC, deviceRescan },
{ Use Defaults,Reset all values to startup defaults,
Index: sysinstall.h
===
RCS file: /home/ncvs/src/usr.sbin/sysinstall/sysinstall.h,v
retrieving revision 1.218
diff -u -r1.218 sysinstall.h
--- sysinstall.h 2001/10/12 22:39:02 1.218
+++ sysinstall.h 2001/11/13 18:12:38
@@ -126,7 +126,6 @@
#define VAR_IPV6_ENABLE ipv6_enable
#define VAR_IPV6ADDR ipv6addr
#define VAR_KEYMAP keymap
-#define VAR_KGET kget
#define VAR_LABELlabel
#define VAR_LABEL_COUNT labelCount
#define VAR_LINUX_ENABLE linux_enable
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
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: URL:http://people.freebsd.org/~matusita/5.0-CURRENT-20011121-JPSNAP_usedevfs/patch -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
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:
URL:http://people.freebsd.org/~matusita/5.0-CURRENT-20011121-JPSNAP_usedevfs
/patch
Hmmm. To be honest, at least one part doesn't make too much sense to
me.
In the quoted section, where you move up the code for copying the
initial /dev files from the mfsroot to the new on-disk root, you then
proceed to mount a devfs instance right over it. Don't you want to
try the devfs mount and only copy device files if that returns an
error code? You're just going to do extra work and then cover it up
otherwise. :-)
+
+ dialog_clear_norefresh();
+ msgNotify(Copying initial device files..);
+ /* Copy the boot floppy's dev files */
+ if ((root-newfs || upgrade) vsystem(find -x /dev | cpio %s -pdum /mnt,
+cpioVerbosity())) {
+ msgConfirm(Couldn't clone the /dev files!);
+ return DITEM_FAILURE | DITEM_RESTORE;
+ }
+
+ /* Mount devfs for other partitions to mount */
+ Mkdir(/mnt/dev);
+ if (!Fake)
+ mount(devfs, /mnt/dev, 0, NULL);
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
imp Right. There is a forth tool available (authored I think by imp matsushita-san), I never do that :-) Maybe the one you mentioned is by yokota-san, URL:http://people.freebsd.org/~yokota/vuserconfig.tar.gz. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
In message [EMAIL PROTECTED] Makoto Matsushita writes: : : imp Right. There is a forth tool available (authored I think by : imp matsushita-san), : : I never do that :-) Maybe the one you mentioned is by yokota-san, : URL:http://people.freebsd.org/~yokota/vuserconfig.tar.gz. Yes. I was confusing you with yokota-san for some reason. Please accept my appologies. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
In message [EMAIL PROTECTED] Cyrille Lefevre writes: : I don't know -current. what is the feature which replace kget ? : does boot -c (or whatever) still exists ? is it possible to : edit KERNEL.hints at boot time ? set/unset works. I've removed ISA devices at boot time by unsetting the 'at' hint. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
Warner Losh wrote: In message [EMAIL PROTECTED] Cyrille Lefevre writes: : I don't know -current. what is the feature which replace kget ? : does boot -c (or whatever) still exists ? is it possible to : edit KERNEL.hints at boot time ? set/unset works. I've removed ISA devices at boot time by unsetting the 'at' hint. thanks for the trick. but show/set/unset are really less intuitive than boot -c, specifically to novice users. unfortunately, I'm not forth aware at all, so, don't ask me about writting such tool using forth :P Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
In message [EMAIL PROTECTED] Cyrille Lefevre writes: : Warner Losh wrote: : In message [EMAIL PROTECTED] Cyrille Lefevre writes: : : I don't know -current. what is the feature which replace kget ? : : does boot -c (or whatever) still exists ? is it possible to : : edit KERNEL.hints at boot time ? : : set/unset works. : : I've removed ISA devices at boot time by unsetting the 'at' hint. : : thanks for the trick. but show/set/unset are really less intuitive : than boot -c, specifically to novice users. unfortunately, I'm not : forth aware at all, so, don't ask me about writting such tool using : forth :P Right. There is a forth tool available (authored I think by matsushita-san), and now that matsushita-san is a committer, maybe it will be done in time for 5.0. :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
Warner Losh wrote: In message [EMAIL PROTECTED] Cyrille Lefevre writes : : Warner Losh wrote: : In message [EMAIL PROTECTED] Cyrille Lefevre wr ites: : : I don't know -current. what is the feature which replace kget ? : : does boot -c (or whatever) still exists ? is it possible to : : edit KERNEL.hints at boot time ? : : set/unset works. : : I've removed ISA devices at boot time by unsetting the 'at' hint. : : thanks for the trick. but show/set/unset are really less intuitive : than boot -c, specifically to novice users. unfortunately, I'm not : forth aware at all, so, don't ask me about writting such tool using : forth :P Right. There is a forth tool available (authored I think by matsushita-san), and now that matsushita-san is a committer, maybe it will be done in time for 5.0. :-) As a fallback, I've been threatening to do a simple userconfig-style thing in loader itself as a fallback if necessary.. I'd rather not since that would just make loader bigger still, but it's always there as a quick/dirty fallback option. If my memory serves me correctly, we dont enable bootforth on the 5.0 boot floppies. This is probably more a symptom of having an identical config for floppies and cd boot. Now that we have cdboot for i386 all but there, we should be able to finally do a complete boot for the CD case and a smaller stripped kernel with esoteric drivers on a seperate disk for the floppy-only case. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
In message [EMAIL PROTECTED] Peter Wemm writes: : Warner Losh wrote: : In message [EMAIL PROTECTED] Cyrille Lefevre writes : : : : Warner Losh wrote: : : In message [EMAIL PROTECTED] Cyrille Lefevre wr : ites: : : : I don't know -current. what is the feature which replace kget ? : : : does boot -c (or whatever) still exists ? is it possible to : : : edit KERNEL.hints at boot time ? : : : : set/unset works. : : : : I've removed ISA devices at boot time by unsetting the 'at' hint. : : : : thanks for the trick. but show/set/unset are really less intuitive : : than boot -c, specifically to novice users. unfortunately, I'm not : : forth aware at all, so, don't ask me about writting such tool using : : forth :P : : Right. There is a forth tool available (authored I think by : matsushita-san), and now that matsushita-san is a committer, maybe it : will be done in time for 5.0. :-) : : As a fallback, I've been threatening to do a simple userconfig-style : thing in loader itself as a fallback if necessary.. I'd rather not since : that would just make loader bigger still, but it's always there as : a quick/dirty fallback option. : : If my memory serves me correctly, we dont enable bootforth on the 5.0 boot : floppies. This is probably more a symptom of having an identical config : for floppies and cd boot. Now that we have cdboot for i386 all but there, : we should be able to finally do a complete boot for the CD case and a : smaller stripped kernel with esoteric drivers on a seperate disk for the : floppy-only case. Actually, now that I think about it, the module I saw was in 'C'. So someone needs to learn forth to do this. :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
Warner Losh wrote: [snip] Actually, now that I think about it, the module I saw was in 'C'. So someone needs to learn forth to do this. :-) what are you waiting for ? :P it's still possible to install gforth (don't know if it's compatible w/ loader ?) and to begin to read the gforth info files (don't know if they are really accurate ?). well, I'm the maintainer, but that's all :-)) I still know nothing to forth ! Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
I don't know -current. what is the feature which replace kget ? There is none. does boot -c (or whatever) still exists ? is it possible to edit KERNEL.hints at boot time ? No. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
On 15-Nov-01 Jordan Hubbard wrote: I don't know -current. what is the feature which replace kget ? There is none. kenv | grep '^hint' kernel.conf does boot -c (or whatever) still exists ? is it possible to edit KERNEL.hints at boot time ? No. Well, you can use set and unset in the loader to do it manually, but that's hardly intuitive. :( We need a Forth hacker to write up a nice interface for manipulating the hints. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
PATCH: sysinstall to remove userconfig code
dsyphers DEBUG: kget: error buffer sizing
matusita This is because sysinstall still want to get userconfig data
matusita and put the result to /boot/kernel.conf.
Userconfig was gone in 5-current, so we can safely remove kget() from
sysinstall. Attached below is a patch to do (kget.c should be remove
also).
Jordan (and others who may concern), would you please review my patch?
-- -
Makoto `MAR' Matsushita
Index: Makefile
===
RCS file: /home/ncvs/src/usr.sbin/sysinstall/Makefile,v
retrieving revision 1.117
diff -u -r1.117 Makefile
--- Makefile2001/09/05 07:12:19 1.117
+++ Makefile2001/11/13 18:12:37
@@ -2,7 +2,7 @@
PROG= sysinstall
MAN= sysinstall.8
-SRCS= anonFTP.c cdrom.c command.c config.c devices.c dhcp.c kget.c \
+SRCS= anonFTP.c cdrom.c command.c config.c devices.c dhcp.c \
disks.c dispatch.c dist.c dmenu.c doc.c dos.c floppy.c \
ftp.c globals.c http.c index.c install.c installUpgrade.c keymap.c \
label.c main.c makedevs.c media.c menus.c misc.c modules.c \
Index: install.c
===
RCS file: /home/ncvs/src/usr.sbin/sysinstall/install.c,v
retrieving revision 1.309
diff -u -r1.309 install.c
--- install.c 2001/10/20 09:28:53 1.309
+++ install.c 2001/11/13 18:12:37
@@ -755,14 +755,6 @@
/* All of this is done only as init, just to be safe */
if (RunningAsInit) {
#ifdef __i386__
-/* Snapshot any boot -c changes back to the new kernel */
- cp = variable_get(VAR_KGET);
- if (cp (*cp == 'Y' || *cp == 'y')) {
- if ((kstat = kget(/boot/kernel.conf)) != NULL) {
- msgConfirm(Unable to save boot -c changes to new kernel,\n
- please see the debug screen (ALT-F2) for details.);
- }
- }
if ((fp = fopen(/boot/loader.conf, a)) != NULL) {
if (!kstat || !OnVTY)
fprintf(fp, # -- sysinstall generated deltas -- #\n);
@@ -1054,7 +1046,6 @@
/* Set default startup options */
variable_set2(VAR_RELNAME, getRelname(), 0);
variable_set2(VAR_CPIO_VERBOSITY, high, 0);
-variable_set2(VAR_KGET,YES, 0);
variable_set2(VAR_TAPE_BLOCKSIZE, DEFAULT_TAPE_BLOCKSIZE, 0);
variable_set2(VAR_INSTALL_ROOT,/, 0);
variable_set2(VAR_INSTALL_CFG, install.cfg, 0);
Index: options.c
===
RCS file: /home/ncvs/src/usr.sbin/sysinstall/options.c,v
retrieving revision 1.76
diff -u -r1.76 options.c
--- options.c 2001/09/25 00:28:26 1.76
+++ options.c 2001/11/13 18:12:37
@@ -148,8 +148,6 @@
OPT_IS_VAR, NEWFS_PROMPT, VAR_NEWFS_ARGS, varCheck
},
{ Fixit Console, Which tty to use for the Fixit action.,
OPT_IS_FUNC, fixitTtyWhich, VAR_FIXIT_TTY, varCheck
},
-{ Config save, Whether or not to save installation kernel config changes,
- OPT_IS_VAR, NULL, VAR_KGET, varCheck
},
{ Re-scan Devices, Re-run sysinstall's initial device probe,
OPT_IS_FUNC, deviceRescan },
{ Use Defaults, Reset all values to startup defaults,
Index: sysinstall.h
===
RCS file: /home/ncvs/src/usr.sbin/sysinstall/sysinstall.h,v
retrieving revision 1.218
diff -u -r1.218 sysinstall.h
--- sysinstall.h2001/10/12 22:39:02 1.218
+++ sysinstall.h2001/11/13 18:12:38
@@ -126,7 +126,6 @@
#define VAR_IPV6_ENABLEipv6_enable
#define VAR_IPV6ADDR ipv6addr
#define VAR_KEYMAP keymap
-#define VAR_KGET kget
#define VAR_LABEL label
#define VAR_LABEL_COUNTlabelCount
#define VAR_LINUX_ENABLE linux_enable
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
Makoto Matsushita wrote: Userconfig was gone in 5-current, so we can safely remove kget() from sysinstall. Attached below is a patch to do (kget.c should be remove also). I don't know -current. what is the feature which replace kget ? does boot -c (or whatever) still exists ? is it possible to edit KERNEL.hints at boot time ? Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
On 13-Nov-01 Cyrille Lefevre wrote: Makoto Matsushita wrote: Userconfig was gone in 5-current, so we can safely remove kget() from sysinstall. Attached below is a patch to do (kget.c should be remove also). I don't know -current. what is the feature which replace kget ? does boot -c (or whatever) still exists ? is it possible to edit KERNEL.hints at boot time ? You can use kenv and just save the ones starting with 'hint' to kernel.conf. kenv dumps the entire kernel environment. We still need a utility written in Forth that the loader can run for the user to modify the hints in the environment. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PATCH: sysinstall to remove userconfig code
John Baldwin wrote: On 13-Nov-01 Cyrille Lefevre wrote: Makoto Matsushita wrote: Userconfig was gone in 5-current, so we can safely remove kget() from sysinstall. Attached below is a patch to do (kget.c should be remove also). I don't know -current. what is the feature which replace kget ? does boot -c (or whatever) still exists ? is it possible to edit KERNEL.hints at boot time ? You can use kenv and just save the ones starting with 'hint' to kernel.conf. kenv dumps the entire kernel environment. We still need a utility written in well, kenv is a userland program (which also exists under -stable... forgot about it) but it is really not comparable to boot -c ! I don't remember if I already use sysinstall to change any kernel value ? Forth that the loader can run for the user to modify the hints in the environment. not for me ;^) thanks anyway for the answer. Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
userconfig()
options USERCONFIG, options VISUAL_USERCONFIG, and options INTRO_USERCONFIG were removed from /sys/conf/options.i386 and options.pc98 on 12 June. Does this mean we are going to ditch userconfig()? (Or, did I miss announcement on this issue?) Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: userconfig()
On Fri, Jul 13, 2001 at 08:32:18PM +0900, Kazutaka YOKOTA wrote: options USERCONFIG, options VISUAL_USERCONFIG, and options INTRO_USERCONFIG were removed from /sys/conf/options.i386 and options.pc98 on 12 June. Does this mean we are going to ditch userconfig()? I think they were disabeled 'cos they interfered with some other changes. I'm not sure if Peter has fixes in the pipeline... David. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
syscons panic in userconfig mode (with patch)
[ cc'd to -stable since that's affected, too ] Attempting to switch VTYs in userconfig mode will lead to a null dereference in syscons. I saw some messages about this on -current, -stable, or -bugs recently, but I can't find them now. This is pretty easy to reproduce: simply boot the kernel with the -c flag (userconfig), and press ALT+F2 (i386). As far as I can tell, this isn't a new bug. The patch is also pretty trivial. It just changes the VIRTUAL_TTY macro not to blindly assume sc-dev[x] is a valid pointer. It is safe to have it "return" NULL because any code that uses it must (and does) already check for that condition since si_tty may also be NULL in some cases (or at least that's the way I understand it). Could someone please look it over and, if it's okay, commit it? Thanks, Dima Dorfman [EMAIL PROTECTED] Index: syscons.c === RCS file: /st/src/FreeBSD/src/sys/dev/syscons/syscons.c,v retrieving revision 1.355 diff -u -r1.355 syscons.c --- syscons.c 2001/03/26 12:40:39 1.355 +++ syscons.c 2001/04/07 21:02:31 @@ -122,7 +122,8 @@ #define SC_CONSOLECTL 255 -#define VIRTUAL_TTY(sc, x) (SC_DEV((sc), (x))-si_tty) +#define VIRTUAL_TTY(sc, x) (SC_DEV((sc), (x)) != NULL ?\ + SC_DEV((sc), (x))-si_tty : NULL) static int debugger; To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Info needed re: new userconfig scripting and PnP
On Tue, Oct 26, 1999 at 06:50:11AM -0500, Conrad Sabatier wrote: I would be most honored, kind sir. :-) Just let me update it first, based on this recently acquired information re: -current. Then, to whom should I submit it? send-pr, including a URL to the DocBook source is the best way. N To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Nevermind! (Re: Info needed re: new userconfig scripting and PnP)
OK, I've gotten a few private replies (thanks!), and have also read through several threads in the -current archives. I think I've got the picture now. Can't say I'm all that happy about what I've read (I mean, having to add to my web pages something to the effect of "you can disregard all of this information if you're running -current"), but who am I to stand in the way of progress, eh? :-) BTW, speaking of device IDs, if anyone needs the info for the AWE 64 "value" card, I'll be happy to provide whatever I can. -- Conrad Sabatier http://members.home.net/conrads/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Info needed re: new userconfig scripting and PnP
Someone just mailed me this heads up about my AWE soundcard setup tutorial at http://members.home.net/conrads/awepnp-freebsd.html. As this is the first I've heard about this, I'd greatly appreciate it if someone could fill me in on the details, so I can update the info on my web site. Thanks! BTW, I'm subscribed to -current now, so you can reply to the list. -FW: [EMAIL PROTECTED]- Date: Sun, 24 Oct 1999 14:50:46 -0400 (EDT) From: Matt Dibb [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: http://members.home.net/conrads/awepnp-freebsd.html Your SB AWE-card how-to is quite helpful, but slightly flawed. You indicate that the procedures listed apply to FreeBSD 3.x and -CURRENT, but this is not so. While the kernel config lines compile fine under 3.x and 4.0, the userconfig script employs the "pnp" keyword to explicitly define which slots/irqs/dmas to probe, but, much to my dismay, this command was eliminated when the userconfig program was reworked for FreeBSD-Current this summer. I am writing to you to inquire as to whether another method (even if less conventional) exists for instructing the kernel to probe all these slots. The kernel syntax doesn't accomodate multiple ports for devices [that I know of], so I've had no luck getting AWE64 support with VoxWare drvs. If you could advise me on a way to get the slots probed right without the "pnp" keyword in userconfig, I'd be most grateful. --End of forwarded message- -- Conrad Sabatier http://members.home.net/conrads/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
new PnP code and pcm and kernel userconfig
The sound card is: ... unknown0: 4232 on isa0 pcm0: CS4232 at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 unknown1: GAME PORT at port 0x200-0x207 on isa0 unknown2: MPU-401 at port 0x330-0x331 irq 9 on isa0 ... Everything looks fine but in my case the CS4232 is a buggy and it can't work in duplex mode and I have to change drq0=drq1=1 Now I can't do this from the kernel userconfig (boot -c ) - pnp configuration is missing. Any ideas? Thanks, Val __ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pnp in userconfig
Hi ... I've got a -current of about a week ago .. when I boot in user config, pnp is no longer listed as a command. when executing pnp .. it says "Invalid command or syntax. Type `?' for help." Is pnp command no longer in user config in -current ??? Thanx Reinier To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
