Multiuser (or at least dual user :) ) puppy linux
Hey Pizzasgood, someone found out about multiuser puppy reading my blog and he/she has problem with grub, can you take a look @ comments, don't know if this is puppy issue or he/she didn't pick right options when installing grub:
http://dejan555.freehostia.com/?p=31&cpage=1#comment-10
http://dejan555.freehostia.com/?p=31&cpage=1#comment-10
puppy.b0x.me stuff mirrored [url=https://drive.google.com/open?id=0B_Mb589v0iCXNnhSZWRwd3R2UWs]HERE[/url] or [url=http://archive.org/details/Puppy_Linux_puppy.b0x.me_mirror]HERE[/url]
MultiUser Puppy--Grub trouble
Hi, Dejan & Pizzasgood--
Some but not extensive experience with Linux...but I really like Puppy and have installed it before without problems. I did a full install of MultiUser Puppy on an old compaq deskpro with 6 GB hdd and 192 MB Ram. I chose install grub on MBR. When finished, I rebooted without cd, and got a (terminal-like screen) with a short paragraph about tab giving some possible completions after the first word, and then below:
grub>
When I pressed tab, I got a list of words like boot, ioprobe, etc. Tried typing boot after grub> but then got a message that the kernel has to be loaded first. Don't know how to do that.
Does this give you any idea of where I might have gone wrong?
many thanks,
srdorothy
Some but not extensive experience with Linux...but I really like Puppy and have installed it before without problems. I did a full install of MultiUser Puppy on an old compaq deskpro with 6 GB hdd and 192 MB Ram. I chose install grub on MBR. When finished, I rebooted without cd, and got a (terminal-like screen) with a short paragraph about tab giving some possible completions after the first word, and then below:
grub>
When I pressed tab, I got a list of words like boot, ioprobe, etc. Tried typing boot after grub> but then got a message that the kernel has to be loaded first. Don't know how to do that.
Does this give you any idea of where I might have gone wrong?
many thanks,
srdorothy
MultiUser Puppy--Grub trouble
I tried once more installing M.U. Puppy to hdd, and this time got a message that the hdd could not be unmounted (I had saved a pup_save file). So I put in my Mepis live cd, found the file and as root deleted it. Rebooted Puppy cd, and didn't get the 'can't unmount hdd' message...continued with install, etc, and couldn't boot Puppy on the hdd.
So with the live cd I mounted the hdd, and found and edited menu.lst per the installation instructions, but still no joy.
I think there is something important that I am missing...8^)
So with the live cd I mounted the hdd, and found and edited menu.lst per the installation instructions, but still no joy.
I think there is something important that I am missing...8^)
Try to do grubconfig from one of your other puppy cd's that work
(Menu -> System -> Grub Bootloader config ) then edit menu.lst to boot multiuser puppy
(Menu -> System -> Grub Bootloader config ) then edit menu.lst to boot multiuser puppy
puppy.b0x.me stuff mirrored [url=https://drive.google.com/open?id=0B_Mb589v0iCXNnhSZWRwd3R2UWs]HERE[/url] or [url=http://archive.org/details/Puppy_Linux_puppy.b0x.me_mirror]HERE[/url]
MultiUser Puppy--Grub trouble
Thank you, Dejan--I'll try that!
- Max Headroom
- Posts: 421
- Joined: Wed 28 Jun 2006, 07:17
- Location: GodZone Kiwi
- Contact:
G'day Pizzasgood & dejan555
Wundered 'bout recent Progress, & Developments w/ a view to Applying this to Dingo 4.3, otherwise is there a time frame 4 an 1d10T Proof howto documentation? ... Thanx
Um, just a thought Pizzasgood. Could it be made a pet with useradd and your wizards for managing users/login and other needed content, then make pinstall.sh set all neded things, I guess this could be done with one script to change all instances of root into $HOME in scripts and set permissions and stuff, that way, instead remastering iso specifically for puppy versions users could just download pet and run it to enable multiuser on any puppy version. What you think, could it be done with one well writen script suplied in package?.
puppy.b0x.me stuff mirrored [url=https://drive.google.com/open?id=0B_Mb589v0iCXNnhSZWRwd3R2UWs]HERE[/url] or [url=http://archive.org/details/Puppy_Linux_puppy.b0x.me_mirror]HERE[/url]
- Max Headroom
- Posts: 421
- Joined: Wed 28 Jun 2006, 07:17
- Location: GodZone Kiwi
- Contact:
Woof
Or SFS Package?
- Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
Forget the docs? I spent a long time last weekend writing those, no way I'd forget them at this stage... I have them nearly done, and the actual work of finishing off the puplet nearly done. As in, I ought to have it complete by Sunday at the latest unless I realize I made some horribly bad oversight. I'd have had it done already but this last week was busier than normal (I had three exams plus the weekly thermodynamics quiz). And my uncle has been working on his website again, so I needed to help fix it a couple times.
Anyway, I realized over the weekend that users could not shutdown or reboot. Well, they normally shouldn't be able to in a server environment, but in a desktop environment you might want at least some users to be able to. I had just written the daemon I mentioned for unmounting partitions, so I was able to reuse that to set up another for rebooting/powering down. Users in the "power" group can do that now.
WRT the mounting/unmounting, it turns out limited users can't do NTFS. For NTFS root needs to mount it. This is because Puppy uses ntfs-3g to handle NTFS partitions, and that doesn't want to let me allow limited users to use it properly. I suppose I could do the same thing I did for unmounting and powering off, but I don't like the idea of having so many daemons (even though they aren't really impacting anything - they just sit there waiting until the directory they monitor changes). But if anyone feels especially strongly about NTFS I'll do it.
I don't know how well all of this could be done by a .pet. I guess I'll look into it. I am making the extra scripts I've written into a .pet, and another for the shadow utilities, and probably a third .pet (or at least .tar.gz archive) for the modifications I had to do to get X running, since it involved some extra stuff like support for /etc/X11/$USER/xorg.conf.
Anyway, I realized over the weekend that users could not shutdown or reboot. Well, they normally shouldn't be able to in a server environment, but in a desktop environment you might want at least some users to be able to. I had just written the daemon I mentioned for unmounting partitions, so I was able to reuse that to set up another for rebooting/powering down. Users in the "power" group can do that now.
WRT the mounting/unmounting, it turns out limited users can't do NTFS. For NTFS root needs to mount it. This is because Puppy uses ntfs-3g to handle NTFS partitions, and that doesn't want to let me allow limited users to use it properly. I suppose I could do the same thing I did for unmounting and powering off, but I don't like the idea of having so many daemons (even though they aren't really impacting anything - they just sit there waiting until the directory they monitor changes). But if anyone feels especially strongly about NTFS I'll do it.
I don't know how well all of this could be done by a .pet. I guess I'll look into it. I am making the extra scripts I've written into a .pet, and another for the shadow utilities, and probably a third .pet (or at least .tar.gz archive) for the modifications I had to do to get X running, since it involved some extra stuff like support for /etc/X11/$USER/xorg.conf.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
Glad to hear that, pizzasgood.
I can't wait for the documentation so I can finish my work on my Account Control Center for K-9. The GUI is (almost) done and my scripts for user creation, group assignment and deletion seem to work flawlessly. However, I still have probs with removing users from a specific group, as the BB-variant of delgroup seems to be pretty crappy (my tcl/tk-based frontend frequently pops up a message that it couldn't find a certain group entry in /etc/gshadow, which I need to iron out in some way now).
And looking at the reports about the troubles you had with mounting and unmounting, I guess that issue will probably give me some sleepless nights as well.
I can't wait for the documentation so I can finish my work on my Account Control Center for K-9. The GUI is (almost) done and my scripts for user creation, group assignment and deletion seem to work flawlessly. However, I still have probs with removing users from a specific group, as the BB-variant of delgroup seems to be pretty crappy (my tcl/tk-based frontend frequently pops up a message that it couldn't find a certain group entry in /etc/gshadow, which I need to iron out in some way now).
And looking at the reports about the troubles you had with mounting and unmounting, I guess that issue will probably give me some sleepless nights as well.
- Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
It lives.
http://www.murga-linux.com/puppy/viewtopic.php?t=47409
I felt guilty so I went ahead and took care of the ntfs issue. I also noticed that somewhere along the way the inittab-AUTO and inittab-NOAUTO files wound up in /usr/etc/ rather than /etc/. I don't know if that happened before or after the last beta. Anyway, it's fixed in the final.
I also set the adduser-wizard to make the user's home directory 750 rather than 755.
The documentation is linked to from the announcement.
Sorry about how I kept releasing it with the exact same filename. I normally don't do that, but I forgot this time around (it's been over a year since I've released a puplet).
http://www.murga-linux.com/puppy/viewtopic.php?t=47409
I felt guilty so I went ahead and took care of the ntfs issue. I also noticed that somewhere along the way the inittab-AUTO and inittab-NOAUTO files wound up in /usr/etc/ rather than /etc/. I don't know if that happened before or after the last beta. Anyway, it's fixed in the final.
I also set the adduser-wizard to make the user's home directory 750 rather than 755.
The documentation is linked to from the announcement.
Sorry about how I kept releasing it with the exact same filename. I normally don't do that, but I forgot this time around (it's been over a year since I've released a puplet).
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
Thank you for your efforts, pizzasgood.
I'll have a look at your multiuser-iso as soon as I finished ironing out some serious probs with my own system. Erm, did you ever encounter the following problem by chance?
When you try to start X as a limited user you see the output
"Startup X, specs in /home/user/.etc/X11/xorg.conf, startup apps /home/user/.xinitrc ..."
but then, nothing happens until the connection to X timed out and you get bumped back to the prompt. Any idea what might cause it? It didn't happen with NOP 4.13, it just happens in Puppy 4.21.
I'll have a look at your multiuser-iso as soon as I finished ironing out some serious probs with my own system. Erm, did you ever encounter the following problem by chance?
When you try to start X as a limited user you see the output
"Startup X, specs in /home/user/.etc/X11/xorg.conf, startup apps /home/user/.xinitrc ..."
but then, nothing happens until the connection to X timed out and you get bumped back to the prompt. Any idea what might cause it? It didn't happen with NOP 4.13, it just happens in Puppy 4.21.
- Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
I think I had a problem like that with Xvesa. I was trying to let the user use his choice of X server, but I didn't realize that xwin was calling xinit, not X, to start it. So to make that work I'd probably have needed to give users a local symlink to their X of choice and then add that to their path so that it overrides /usr/X11R7/bin/X. Once I realized what was wrong I decided it wasn't worth the effort.
I think it did that when xwin was configuring it for xorg but X still pointed at Xvesa. But it might have been the other way around. Not sure.
I think it did that when xwin was configuring it for xorg but X still pointed at Xvesa. But it might have been the other way around. Not sure.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
PG
Long-running arguement, I know, but someone's not heard of your Multi-user pup
Would you care to comment to JeffM on googlegroups?
Aitch
Long-running arguement, I know, but someone's not heard of your Multi-user pup
Would you care to comment to JeffM on googlegroups?
http://groups.google.com/group/comp.os. ... 3d75d399aeJeffM wrote:Roy Schestowitz wrote:
>http://distrolove.blogspot.com/2009/09/ ... ux-2u.html
>|[...]sure it is best[sic] than windows 98.
>|Now I can say it is a perfect windows killer.
Well, it has the same lousy security model as Win98 (none at all).
When folks' Puppy boxes get pwned, Linux gets a black eye. 8-(
The same 99.999 percent of Win98 users
who never installed/configured M$'s System Policy Editor
will also never Google up the directions needed
to reconfigure Puppy to add less-privileged users
--instead of the always-run-as-root default.
With the number of folks running Puppy,
I'm surprized there isn't a Puppy-specific botnet.
Aitch