You are not logged in.
@hut can you double check pkgbuild sha256sum for minirc.install
The minirc.install was edited without the checksum in the PKGBUILD being updated. I submitted a pull request to fix this, but the correct hash for the file as it is written now is as follows:
acc4346dc4a9ad7cd02b87bb206d4af205291fe532c0b2a8a585e8d7b3c7a6ee
All the best,
-HG
Offline
Thanks I made the change and have built package....
Mr Green
Offline
Thanks I made the change and have built package....
I do not have a computer on which I can test this at the moment, so I'll be interested to hear how it goes for you.
All the best,
-HG
Offline
Building an iso with it now then install and I can then test under virtualbox
Mr Green
Offline
Be aware that the package just sets up the defaults, you will still have to setup the rc script for your daemons and modify your inittab for your system.
All the best,
-HG
Offline
Thanks a lot HalosGhost for the pkgbuild. I fixed the checksum.
Give me some time, I'll test it and add the mdev-like-a-boss stuff to it so we can use systemd as optional dependency.
"hut_" or "h00th00t" in irc.freenode.net #archlinux
Ranger Mailing List: https://lists.nongnu.org/mailman/listinfo/ranger-users
Offline
Must admit I am a little rusty when it comes to inittab, got system booting but dhcpcd is not working certainly no Xorg yet!
Mr Green
Offline
Must admit I am a little rusty when it comes to inittab, got system booting but dhcpcd is not working certainly no Xorg yet!
Still though! Functional boot is not a bad achievement for the basic skeleton. That's very exciting!
All the best,
-HG
Offline
Had to add tmpfs to fstab as for some reason did not have permission to access it. I can start X now......
Mr Green
Offline
Maybe a screenshot might help
Mr Green
Offline
Victory! Congratulations!
Give me some time, I'll test it and add the mdev-like-a-boss stuff to it so we can use systemd as optional dependency.
That sounds awesome, I greatly look forward to this. Fantastic work!
All the best,
-HG
Last edited by HalosGhost (2013-05-04 18:38:58)
Offline
Still early days yet
Aha I can see the problem with dhcpcd its named eth0 a quick edit should solve the problem....
Last edited by Mr Green (2013-05-04 18:40:59)
Mr Green
Offline
Very interesting project. I'm on my girlfriend's home this weekend, going to give it a try when I come back to my house .
Offline
Very interesting project. I'm on my girlfriend's home this weekend, going to give it a try when I come back to my house .
It's already progressed a long way. I'm sorry to say that I won't have access to a computer that I can use this on for at least two more weeks, but this looks very promising so far.
All the best,
-HG
Offline
This may not of much use but rc.d.patch to add a variable for wired connection. Might make it easier to configure minirc.conf (less hidden)
--- rc 2013-05-04 17:50:26.709855225 +0100
+++ rc.d 2013-05-05 07:48:52.592738829 +0100
@@ -3,6 +3,7 @@
# define daemons
ALL_DAEMONS="syslog-ng iptables crond dbus dhcpcd sshd alsa privoxy acpid mpd vsftpd lighttpd ntpd"
DEFAULT_DAEMONS="$ALL_DAEMONS"
+WIRED_NETWORK="eth0"
# /etc/minirc.conf gives you a chance to override the daemon variables
test -f /etc/minirc.conf && source /etc/minirc.conf
@@ -65,7 +66,7 @@
privoxy)
/usr/sbin/privoxy --user privoxy.privoxy /etc/privoxy/config;;
dhcpcd)
- /usr/sbin/dhcpcd -qb eth0;;
+ /usr/sbin/dhcpcd -qb $WIRED_NETWORK;;
vsftpd)
/usr/sbin/vsftpd &;;
lighttpd)
Mr Green
Offline
Just updated minirc package and system would not boot, took me a while to figure out to switch UDEV to 'systemd' as 'busybox' did not create devices in /dev correctly.
Mr Green
Offline
The logic for `busybox mdev` to have it setup /dev correctly is in-progress. But, at the moment, using ``systemd`` is still recommended.
All the best,
-HG
P.S., I just filed a fairly heavy pull request upstream, and if it is accepted, you will certainly need to redo some of your configuration (I won't update the PKGBUILD for the new logic in the pull request unless/until it is accepted upstream). This is just a heads up.
Offline
I should have read README before updating so my fault!!! It would have far better to run with 'systemd' and give option of busybox (commented out). Testing on a virtual machine at the moment so do not mind messing it up. Also noticed rc.d is now rc which makes sense.
Mr Green
Offline
I should have read README before updating so my fault!!! It would have far better to run with 'systemd' and give option of busybox (commented out). Testing on a virtual machine at the moment so do not mind messing it up. Also noticed rc.d is now rc which makes sense.
Perhaps it's just my own force of habit, but I'm used to either using `systemctl` or `rc.d`, but hut wanted it to remain `rc` not `rc.d`so I reverted it. I wonder if he would be more amenable to `service`, as that still makes sense and was still a common way of doing things a while back. hut, thoughts?
All the best,
-HG
Offline
service files are systemd (think ubuntu uses the term too) thinking more rc scripts or even minirc scripts they have to stand out and then people will not get confused
Mr Green
Offline
service files are systemd (think ubuntu uses the term too) thinking more rc scripts or even minirc scripts they have to stand out and then people will not get confused
But `script`, though accurate, gives the wrong impression, I think. And, I mean `service` as the command, what `rc` would be renamed. Yes, .service files are a systemd thing, but using `service` as the command to {{,re}start,stop} daemons existed during the SysVinit days.
All the best,
-HG
Offline
This may not of much use but rc.d.patch to add a variable for wired connection. Might make it easier to configure minirc.conf (less hidden)
[...]
I applied the patch, thank you
Just updated minirc package and system would not boot, took me a while to figure out to switch UDEV to 'systemd' as 'busybox' did not create devices in /dev correctly.
Yeah, things will be a little volatile until we settle on the file names and default settings, sorry about that. I recommend to skim through the readme or the git diffs before each upgrade.
Mr Green wrote:service files are systemd (think ubuntu uses the term too) thinking more rc scripts or even minirc scripts they have to stand out and then people will not get confused
But `script`, though accurate, gives the wrong impression, I think. And, I mean `service` as the command, what `rc` would be renamed. Yes, .service files are a systemd thing, but using `service` as the command to {{,re}start,stop} daemons existed during the SysVinit days.
All the best,
-HG
I renamed it to "rc" because it's very short. "rc.d" would be confused with the old rc.d from sysvinit. The most sane option looks to me like renaming /sbin/rc to /sbin/minirc to remove all ambiguity. Is that okay with everyone?
"hut_" or "h00th00t" in irc.freenode.net #archlinux
Ranger Mailing List: https://lists.nongnu.org/mailman/listinfo/ranger-users
Offline
Renaming 'rc' tp 'minirc' makes perfect sense to me.
EDIT: syslog did not work for me until I changed path in syslog-ng.conf
Last edited by Mr Green (2013-05-06 00:08:16)
Mr Green
Offline
Renaming 'rc' tp 'minirc' makes perfect sense to me.
EDIT: syslog did not work for me until I changed path in syslog-ng.conf
I'll add it to the FAQ.
"hut_" or "h00th00t" in irc.freenode.net #archlinux
Ranger Mailing List: https://lists.nongnu.org/mailman/listinfo/ranger-users
Offline
Renaming 'rc' tp 'minirc' makes perfect sense to me.
If you want it short, what about mrc?
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline