Hi there,
I've made a patch to use our beloved blue penguin as framebuffer logo:
http://jw.smts.ch/files/crux/fblogo.png
sorry for the shaky picture :-)
The patch is here:
http://jw.smts.ch/files/crux/linux-2.6.24.3-crux-logo.diff
Applies cleanly to 2.6.25.7 too, and probably most other recent
versions. Adds a new option "224-color CRUX logo" to "Device Drivers >
Graphics support > Bootup logo".
Enjoy, Johannes
--
Johannes Winkelmann mailto:jw@smts.ch
Zurich, Switzerland http://jw.smts.ch
I've written a small utility to facilitate backups of live packages
git://die.net.au/crux/tools/pkg-backup.git
I also put together a wiki page on how to use it.
http://crux.nu/Public/PackageBackups
--
Lucas Hazel <lucas(a)die.net.au>
Hi Danny !
I changed lilo.conf boot line to boot=/dev/sda and ran lilo again.
Still the problem persists.
Completely erased the CD-RW (full erase) and burnt the iso image with 4x speed and installed on sda6 but the problem is persistent.
I am perplexed.
Boovarahan S
Please visit http://www.bajajinsurance.110mb.com
For your web hosting needs (both free and paid) visit http://www.110mb.com/aff.php?un=bajajinsurance
Hi there,
Lately, I've been going through the TODO list of prt-get, and started to
implement some of them; cause they're changing the user experience quite
drastically, I'd like to hear what people think about them. Since both
the old and the new variant rely on the same core, it should be fairly
easy to keep around both if we want to. So if you don't like what you
read, don't worry :-).
There are two major chances:
1. User interface: less commands
--------------------------------
Many of its current features weren't there from the start, and I've
usually chosen to add a separate 'command' (think: prt-get <command>
...), for example depends/deptree/dependent. In addition, there's a
major overlap between some of the commands in query (printf is just a
more specific form of either list or info, depending on the filter
argument). For a long time, I wanted to change this, and finally got
around it. That might look like this:
[old] [new]
prt-get depends <port> pgt depends <port>
prt-get deptree <port> pgt depends -T <port>
prt-get quickdep <port> pgt depends -Q <port>
prt-get dependent <port> pgt depends -R <port> (reverse)
prt-get diff [<port>] pgt diff [<port>]
prt-get quickdiff [<port>] pgt diff -Q [<port>]
Note how -Q has the same meaning. There a list of mapping here:
http://jw.smts.ch/pg-ng
7 commands in pgt replace 18 in prt-get. The 'find' generalizations
might be a bit too much, I may go for a find/list combo.
2. Dependency handling
----------------------
When prt-get was introduced, the "Depends on:" header was optional (and
somtimes even frowned upon). As a consequence of this, the default
'install' command did not install dependencies. As a side effect,
'update' and 'sysup' never got --with-deps options, since it's
impossible to tell whether a user omitted a dependency by calling
'install' instead of 'depinst' or whether it was introduced in the last
update (think: pkgutils and libarchive).
Nowadays, things are different: we expect people to install
dependencies, and if errors get reported we typically ask first whether
all dependencies are met. Therefore, I'd suggest the following:
- pgt install <port> would install <port> and its dependencies (like
depinst)
- pgt update <port> would install <port>'s missing dependencies, and
update <port>
- pgt sysup would install all missing dependencies, and update outdated
ports in the system
All commands will get a -N/--no-deps switch to really only handle a
single port, however the next update or sysup will of course bring them
back.
In other words prt-get no more silently assumes that the user didn't
want a particular dependency.
Now, if you don't want a package (and believe it's only an optional
dependency for your usage pattern although the maintainer listed it),
you can still do it, but explicitely by calling 'pgt lock' on an
uninstalled package. Locked packages won't be touched by any pgt
command (but there will be a warning printed in the end of install if a
locked dependency was requested in that transaction).
As mentioned, I'd like to hear your comments on those two changes. I'm
sure both will take some time to get used to (heck, even the new name; I
keep typing 'prt-get' on the machine where I installed pgt to test it
;-)), but are worth it in the long run.
Best regards, Johannes
--
Johannes Winkelmann mailto:jw@smts.ch
Zurich, Switzerland http://jw.smts.ch
Did you configure properly your /etc/fstab file?
Well, /etc/fstab has not yet available when the panic happens since it's
on the very filesystem the kernel tries to mount and fails at it.
Boovarahan: typically, this error occurs if one of the the following
isn't true:
- you compiled support for your SATA, IDE or SCSI controller into the
kernel (not as module)
- you compiled support for the filesystem of the root partition into the
kernel (not as module)
- the root= option in lilo.conf is correct
Please verify these, along with the lilo settings as mentioned in Dannys
mail.
HTH, Johannes
1. lilo.conf file is as follows:
# /etc/lilo.conf: lilo(8) configuration, see lilo.conf(5)
#
lba32
install=text
boot=/dev/sda6
image=/boot/vmlinuz
label=CRUX
root=/dev/sda6
read-only
append="quiet"
# End of file
2.fstab file is this:
/dev/sda6 / ext3 defaults,noatime 0 1
/dev/sda1 swap swap defaults 0 0
/dev/cdrom /cdrom iso9660 ro,user,noauto,unhide 0 0
devpts /dev/pts devpts defaults 0 0
none /sys sysfs defaults 0 0
none /proc proc defaults 0 0
#tmp /tmp tmpfs defaults 0 0
#shm /dev/shm tmpfs defaults 0 0
usb /proc/bus/usb usbfs defaults 0 0
# End of file
3. The SATA / ext3 fs support were not compiled as modules.
4. I have used sda6 only and no other separate partitons are used.
Let me once again chroot and do the compiling.
Thanks.
Boovarahan S
Please visit http://www.bajajinsurance.110mb.com
For your web hosting needs (both free and paid) visit http://www.110mb.com/aff.php?un=bajajinsurance
I have two discs - one ide and another SATA.
The ide disc has windows.
The SATA drive is divided into 8 partitions and one swap.
I installed CRUX on sda6 and tried to boot but got yhe following msg:
"kernel panic - not syncing, VFS :unable to mount root fs on unknown block (8,6) "
The /etc/lilo.conf is as follows:
"
lba32
install=text
boot=/dev/sda6
image=/boot/vmlinuz
label=CRUX
root=/dev/sda6
read-only
append="quiet" "
How to boot CRUX ?
Boovarahan S
Please visit http://www.bajajinsurance.110mb.com
For your web hosting needs (both free and paid) visit http://www.110mb.com/aff.php?un=bajajinsurance
