mknod /devices/pseudo/mm@0:null c 13 2
chown root:sys /devices/pseudo/mm@0:null
chmod 666 /devices/pseudo/mm@0:null
cd /dev
ln -s ../devices/pseudo/mm@0:null null
Alexander
On 25.04.2013, at 12:51, Richard Jones openindiana-disc...@jonze.com wrote:
Hi,
I've overwritten /dev/null and
On Thu, Apr 25, 2013 at 09:57:56AM +0100, Khushil Dep wrote:
mknod /dev/null c 1 3 should work.
mknod: `/dev/null': No such file or directory
:(
--
Richard Jones +44 7843 588 599
Quod gratis asseritur, gratis negatur
Privacy
On Thu, Apr 25, 2013 at 01:00:52PM +0400, Alexander Eremin wrote:
mknod /devices/pseudo/mm@0:null c 13 2
mknod: `/devices/pseudo/mm@0:null': File exists
chown root:sys /devices/pseudo/mm@0:null
chown: changing ownership of `/devices/pseudo/mm@0:null': Not owner
chmod 666
Boot using a live cd, mount your original /dev and /devices somewhere and
then copy from the live cd using rsync.
On Thu, Apr 25, 2013 at 6:03 AM, Richard Jones
openindiana-disc...@jonze.com wrote:
On Thu, Apr 25, 2013 at 01:30:35PM +0200, Jim Klimov wrote:
How about removing both
On Thu, Apr 25, 2013 at 2:03 PM, Richard Jones
openindiana-disc...@jonze.com wrote:
On Thu, Apr 25, 2013 at 01:30:35PM +0200, Jim Klimov wrote:
How about removing both /devices/pseudo/mm@null* and /dev/null and
then trying devfsadm?
# rm /dev/null
rm: cannot remove `/dev/null': No such
Which exactly? Seemingly unimportant details can be essential here.
I have been in similar situations (during OpenSXCE debugging), I know how
ugly and hopeless it feels in such a scenario.
Fact is, that if running scripts directly from /lib/svc/method does not
even help (if you tried), then
On 04/25/13 08:03, Richard Jones wrote:
On Thu, Apr 25, 2013 at 01:30:35PM +0200, Jim Klimov wrote:
How about removing both /devices/pseudo/mm@null* and /dev/null and
then trying devfsadm?
# rm /dev/null
rm: cannot remove `/dev/null': No such file or directory
# rm
On Thu, Apr 25, 2013 at 2:53 PM, James Carlson carls...@workingcode.comwrote:
On 04/25/13 08:03, Richard Jones wrote:
On Thu, Apr 25, 2013 at 01:30:35PM +0200, Jim Klimov wrote:
How about removing both /devices/pseudo/mm@null* and /dev/null and
then trying devfsadm?
# rm /dev/null
On 25/04/13 14:53, James Carlson wrote:
snip
Unfortunately, that's where my knowledge of the system (based on my
years in PSARC) ends. I don't know how to repair damage like you're
describing. I just know that the people telling you to rm these fake
files or run mknod are misinformed. That'll
On 04/25/13 09:24, Laurent Blume wrote:
On 25/04/13 14:53, James Carlson wrote:
snip
Unfortunately, that's where my knowledge of the system (based on my
years in PSARC) ends. I don't know how to repair damage like you're
describing. I just know that the people telling you to rm these fake
On Thu, Apr 25, 2013 at 04:15:08PM +0400, Alexander Eremin wrote:
Boot from alternate BE or CD should help. Mount this BE and run
devfsadm against mountdir.
Bingo!
# beadm create newpool
# beadm activate newpool
# reboot
[...]
# beadm mount opendiana /mnt
# cd /mnt/dev
# ln -s
11 matches
Mail list logo
