When it is done flashing, it should display the OK message as stated in the above article and you can connect to your router openwrt using 192.168.1.1
Note: Make sure no other device (i.e some other router in the network) is using this IP or change this IP after logging in to avoid IP conflicts. If you are unable to access the GUI due to conflict, try setting a static IP then log in again.
You are right, but the method is too complicated and not everyone wants to open their device and connect it using serial, besides, the firmware link given is also broken and I was unable to find an option to edit anything on the wiki.
NOTE: This guide only installs openwrt on one partition, as Linksys whw01 is a dual partition device firmware, if you wish to install it on both partitions you can reflash the image when openwrt boots up from the luci web interface. This will install openwrt on both partitions but you will have to configure both partitions individually and the settings of one partition will stay the same unless you change them explicitly. In simple words, changes done to one partition stay on only one partition and do not reflect on the second partition.
NOTE (2): If you wish to see which boot partition is currently active or want to switch to another partition for some reason, you can use the command below using ssh.
Shows currently active boot partition:
/usr/sbin/fw_printenv -n boot_part
The below command switches the partition to the given number, In this case, I used 1 to switch boot to partition 1, you can do the same with others by replacing 1 with 2. Do note that you will have to reboot either manually or using the reboot command for the actual switching to happen after executing the command.
Switch the boot partition to the given number after reboot:
A few days ago, only the snapshot was available and so we had no choice but to use snapshots which are very early stage (latest / in development) build and can change many times in a day.
Now, it seems that rc (release candidate) has also become available, Release candidate builds are as the name implies candidates for the stable release, they will soon be made available as stable releases for the production/ family environment if no major bugs are found.
Coming to your question, I have not tested the release candidate version myself but it should work fine, you can try if you wish or wait more until it becomes a stable release, but if you are thinking of installing a snapshot then you can go with release candidate as it is more mature compared to snapshot. In a way, you could say that the release candidate is similar to the beta version and the snapshot is similar to the alpha version.